igotu2gpx team mailing list archive
-
igotu2gpx team
-
Mailing list archive
-
Message #00588
[Bug 508372] [NEW] "Response too short" and segfault
Public bug reported:
I have a new GT-120, and always get the following crash:
> igotu2gpx -v info
Downloading configuration...
Command: 930101030000000000000000000000
Protocol violated : Response too short: expected 3, got 0 bytes
Command: 930101030000000000000000000000
Protocol violated : Response too short: expected 3, got 0 bytes
After a couple more of these messages it either hangs indefinitely, or
crashes with
Failed: Response too short: expected 3, got 0 bytes
QThread: Destroyed while thread is still running
Segmentation fault
This happens whenever I try to connect, whether using the gui or igotu2gpx.
So maybe a threading issue?
** Affects: igotu2gpx
Importance: Undecided
Status: New
--
"Response too short" and segfault
https://bugs.launchpad.net/bugs/508372
You received this bug notification because you are a member of
MobileAction i-gotU USB GPS travel logger Mac/Linux developers, which is
subscribed to igotu2gpx.
Status in MobileAction i-gotU USB GPS travel logger Mac/Linux support: New
Bug description:
I have a new GT-120, and always get the following crash:
> igotu2gpx -v info
Downloading configuration...
Command: 930101030000000000000000000000
Protocol violated : Response too short: expected 3, got 0 bytes
Command: 930101030000000000000000000000
Protocol violated : Response too short: expected 3, got 0 bytes
After a couple more of these messages it either hangs indefinitely, or crashes with
Failed: Response too short: expected 3, got 0 bytes
QThread: Destroyed while thread is still running
Segmentation fault
This happens whenever I try to connect, whether using the gui or igotu2gpx.
So maybe a threading issue?
Follow ups
References