Hello,

I've been using gpsbabel for several years without problem, also with
the "Navin MiniHomer". Just now I'm trying to download something from
the MiniHomer, and this is what happens:

dh@dotcom:~/gps/new$ gpsbabel -D 10 -i miniHomer -f /dev/ttyUSB0 -o gpx
-F t.gpx
GPSBabel Version: 1.5.0
options: module/option=value: miniHomer/baud="115200" (=default)
options: module/option=value: miniHomer/erase="0" (=default)
options: module/option=value: miniHomer/first-sector="0" (=default)
options: module/option=value: miniHomer/initbaud="38400" (=default)
options: module/option=value: miniHomer/last-sector="-1" (=default)
options: module/option=value: miniHomer/no-output="0" (=default)
options: module/option=value: miniHomer/read-at-once="255" (=default)
gbser_init("/dev/ttyUSB0")
skytraq: Probing SkyTraq Venus at 38400baud...
Sending: a0 '.'
Sending: a1 '.'
Sending: 00 '.'
Sending: 02 '.'
Sending: 02 '.'
Sending: 01 '.'
Sending: 03 '.'
Sending: 0d '.'
Sending: 0a '.'
rd_char(): Got char: a0 '.'
rd_char(): Got char: a1 '.'
rd_char(): Got char: 00 '.'
rd_char(): Got char: 02 '.'
Receiving message with 2 bytes of payload (expected >=2)
rd_buf():  dump follows:
83 00                                            ..
rd_char(): Got char: 83 '.'
rd_char(): Got char: 0d '.'
rd_char(): Got char: 0a '.'
rd_char(): Got char: a0 '.'
rd_char(): Got char: a1 '.'
rd_char(): Got char: 00 '.'
rd_char(): Got char: 02 '.'
Receiving message with 2 bytes of payload (expected >=2)
rd_buf():  dump follows:
83 02                                            ..
rd_char(): Got char: 81 '.'
rd_char(): Got char: 0d '.'
rd_char(): Got char: 0a '.'
Got ACK (id=0x02)
rd_char(): Got char: a0 '.'
rd_char(): Got char: a1 '.'
rd_char(): Got char: 00 '.'
rd_char(): Got char: 0e '.'
Receiving message with 14 bytes of payload (expected >=14)
rd_buf():  dump follows:
80 01 00 01 04 2a 00 01 04 39 00 0d 0a 18        .....*...9....
rd_char(): Got char: 8d '.'
rd_char(): Got char: 0d '.'
rd_char(): Got char: 0a '.'
skytraq: Venus device found: Kernel version = 1.4.42, ODM version =
1.4.57, revision (Y/M/D) = 13/10/24
Segmentation fault
dh@dotcom:~/gps/new$

hi,

thanks for your bug report.

Do you know how to create a backtrace using gdb?

https://wiki.debian.org/HowToGetABacktrace

You'll need a debug build of gpsbabel to be able to get a proper backtrace, I
could guide you to build one or build a .deb for you, but that would take some time.

cheers,

bernd

GPSBabel never really had widespread issues of this, but there have been
changes to improve SkyTraq code in subsequent years.

If you DO have an affected device that still shows this problem with
development head (or a released version) and you wish to submit it for
analysis, please contact me (upstream) directly for shipping addresses.


As this appears to have been a one-off from seven years ago with no further
action, please consider closing it.