[Gllug] gpilotd on SUSE LINUX 9.1

[Richard Turner]

On Tue, 2004-05-18 at 23:32, Richard Turner wrote:
> How can I generate a back-trace so that I can either investigate further
> myself or submit a half-decent bug report if it comes to that?
> 

Sorry, I was being a bit dumb -- having Googled so long looking for
solutions to the gpilotd problem I didn't think about how easy it'd be
to discover how to generate a back-trace.

GDB reports the segv occurring during a fgets() call in libc.so.6.  I've
tried using glibc 2.3.3-97 and then 2.3.3-98, both supplied by SUSE, but
that's not made a blind bit of difference.  Any insight would be much
appreciated!  Below is the output from gdb.  It says that there are no
pilots configured because I've not managed to configure any yet -- it
keeps crashing!

Starting program: /opt/gnome/lib/gnome-pilot/gpilotd
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 16384 (LWP 17473)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...gpilotd-Message: gnome-pilot
2.0.10 starting...
gpilotd-Message: compiled for pilot-link version 0.11.8
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
 
(gpilotd:17473): gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching Cradle (/dev/pilot)
 
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 17473)]
0x40cd9434 in fgets () from /lib/libc.so.6

Cheers,

Richard.
-- 
"Racing turtles, the grapefruit is winning..."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20040519/27614acc/attachment.pgp>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug