Re: Kudzu seg fault

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Eric \"Shubes\"
Date:  
To: Main PLUG discussion list
Subject: Re: Kudzu seg fault
Eric "Shubes" wrote:
> Edward Norton wrote:
>> On 3/30/06, *Eric Shubes* < <mailto:plug@shubes.net>>
>> wrote:
>>
>>     Anyone else getting a segmentation fault with kudzu on FC5?
>>     I've googled a bit and haven't found a definitive answer.
>>     I've removed kudzu (and dependents) and reinstalled, still no go.
>>     kernel-2.6.16-1.2080_FC5
>>     kudzu-1.2.34.3-1
>>     Ideas?
>>     --
>>     -Eric 'shubes'
>>     ****************************************************
>>     This message has been scanned using Contraxx
>>     Technology Group mail server v8.0.3 and is virus free.
>>     Message sent from Mail Server 3
>>     ****************************************************
>>     ---------------------------------------------------
>>     PLUG-discuss mailing list - 
>>     <mailto:PLUG-discuss@lists.plug.phoenix.az.us>
>>     To subscribe, unsubscribe, or to change  you mail settings:
>>     http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

>>
>>
>>
>> gdb -q /path/to/kudzu
>> in gdb:
>> run
>> backtrace
>> quit
>>
>> reply with results.
>>
>>
> [root@helen ~]# gdb -q /sbin/kudzu
> (no debugging symbols found)
> Using host libthread_db library "/lib/libthread_db.so.1".
> (gdb) run
> Starting program: /sbin/kudzu
> Reading symbols from shared object read from target memory...(no
> debugging symbols found)...done.
> Loaded system supplied DSO at 0x144000
> (no debugging symbols found)
> (no debugging symbols found)
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00a3bd63 in strdup () from /lib/libc.so.6
> (gdb) backtrace
> #0 0x00a3bd63 in strdup () from /lib/libc.so.6
> #1 0x0805db7b in xenNewDevice ()
> #2 0x0805acf5 in ddcNewDevice ()
> #3 0x080509df in newDevice ()
> #4 0x0804d5a6 in ?? ()
> #5 0x009e77e4 in __libc_start_main () from /lib/libc.so.6
> #6 0x0804a8e1 in ?? ()
> (gdb) quit
> The program is running. Exit anyway? (y or n) y
> [root@helen ~]#


That doesn't say too much, so I installed kudzu-debuginfo and tried again:

[root@helen ~]# gdb /sbin/kudzu
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /sbin/kudzu
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x144000

Program received signal SIGSEGV, Segmentation fault.
0x00a3bd63 in strdup () from /lib/libc.so.6
(gdb) backtrace
#0  0x00a3bd63 in strdup () from /lib/libc.so.6
#1  0x0805db7b in vbe_get_vbe_info () at vbe.c:198
#2  0x0805acf5 in ddcProbe (probeClass=Variable "probeClass" is not 
available.
) at ddc.c:395
#3  0x080509df in probeDevices (probeClass=CLASS_UNSPEC, probeBus=-9,
     probeFlags=1) at kudzu.c:806
#4  0x0804d5a6 in main (argc=Cannot access memory at address 0xffffffff
) at hwconf.c:938
#5  0x009e77e4 in __libc_start_main () from /lib/libc.so.6
#6  0x0804a8e1 in _start ()
(gdb) quit
The program is running.  Exit anyway? (y or n) y
You have new mail in /var/spool/mail/root
[root@helen ~]#


That's better, but it's still a bit g(r)eek to me. :)

--
-Eric 'shubes'
****************************************************
This message has been scanned using Contraxx
Technology Group mail server v8.0.3 and is virus free.
Message sent from Mail Server 3
****************************************************
---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss