On Tuesday 30 August 2005 02:55, Belgabor wrote:
> > On Tuesday 30 August 2005 00:30, Belgabor wrote:
> > > > Another method to get a closer idea, what the problem is would be to
> > > > start gpsdrive in debug mode
> > > > gpsdrive -D
> > >
> > > Good tip, but I have to interfere at this point since the cvs version
> >
> > has
> >
> > > been segfaulting for me for a while with -d...
> >
> > Can you tell me more about your segfault with gpsdrive-cvs
> > If you could try the current cvs Version and send me the debug output
> > from gdb
> > would be nice.
>
> Unfortunately I don't know much about gdb. If you tell me which command's
> output you're interested in after the segfault, I'll get it for you. So far
> gdb tells me after the segfault:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 15848)]
> 0xb77c5253 in strlen () from /lib/libc.so.6
>
> Here is the backtrace up to the point that I deemed interestig =)
>
> #0 0xb7834253 in strlen () from /lib/libc.so.6
> #1 0xb781fe87 in fputs () from /lib/libc.so.6
> #2 0xb7a5b074 in g_print () from /usr/lib/libglib-2.0.so.0
> #3 0x00000000 in ?? ()
> #4 0xb78e27a0 in _IO_2_1_stderr_ () from /lib/libc.so.6
> #5 0xb7813b94 in _IO_vfscanf () from /lib/libc.so.6
> #6 0x08075c4e in expose_display_battery () at battery.c:854
>
> As I said, if you need more, just say so.
Could you try this version?
http://www.ostertag.name/tweety/Projekte/gpsdrive/gpsdrive-2.10pre3-segfault-in-expose_display_battery.tar.gz
with
gpsdrive -D
and send me the last ~ 30 Lines.
-
Joerg
--
This message was part of the gpsdrive mailinglist
unsubscribing can be done by sending a mail containing a body of:
-quote--
unsubscribe gpsdrive
-unquote--
to majordomo-ahljRfkWE0EwtzFM8z8+AfP6llvjuJOh@xxxxxxxxxxxxxxxx
|
