← Back to team overview

igotu2gpx team mailing list archive

[Bug 508372] Re: "Response too short" and segfault

 

Hi Thomas,

thanks for the bugreport. As it works for you now, I will mark the bug
as invalid. If it happens again, just reopen the bug or file a new one.

Michael

** Changed in: igotu2gpx
       Status: New => Invalid

-- 
"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: Invalid

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?





References