Bug#353494: gdb output Re: Bug#353494:
Walter wrote:
>>>>> I can report that is problem is exists. I have this problem with my
>>>>> 6x86 processor / Mystique and Debian Etch.
>>>>>
>>>>> I can confirm that in XFree86 3.3.6 it worked fine. Problems started
>>>>> when I tried XFree86 4.0 and apparently they are still there now that
>>>>> I've tried a new installation with a debian-40r0-i386 CD.
>>>>
>>>> Could you try with xserver-xorg-core 1.3 currently in
>>>> testing/Lenny? The
>>>> Xserver in Etch is already pretty old unfortunately.
>>>
>>> This gives a different result. I get a signal 11 and the backtrace
>>> doesn't show much:
>>>
>>> 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591]
>>> 1: [0xb7f08420]
>>
>> Could you try with xserver-xorg-core-dbg and start X from gdb?
>
> So far no real luck. GDB from testing has a problem with loading
> symbols ("Failed to read a valid object file image from memory."). A
> newer kernel then etch seems to solve this. However the kernel in
> testing gives a panic during start-up.
> (http://www.uwsg.iu.edu/hypermail/linux/kernel/0706.3/0272.html,
> apply_paravirt)
>
> So below you can see what I have.
>
> Best regards,
>
> Walter
>
> linux:~# gdb Xorg
> GNU gdb 6.4.90-debian
> Copyright (C) 2006 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 "i486-linux-gnu"...Using host libthread_db
> library "/lib/libthread_db.so.1".
>
> (gdb) run
> Starting program: /usr/bin/Xorg
> Failed to read a valid object file image from memory.
>
> X Window System Version 1.3.0
> Release Date: 19 April 2007
> X Protocol Version 11, Revision 0, Release 1.3
> Build Operating System: Linux Debian
> Current Operating System: Linux linux 2.6.18-4-486 #1 Mon Mar 26
> 16:39:10 UTC 2007 i486
> Build Date: 01 June 2007
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 14 02:29:48 2007
> (==) Using config file: "/etc/X11/xorg.conf"
> [tcsetpgrp failed in terminal_inferior: Operation not permitted]
> (II) Module already built-in
> (II) Module already built-in
> (II) Module already built-in
> (II) Module already built-in
> (EE) MGA(0): [drm] Direct rendering only supported with
> G200/G400/G450/G550.
> (EE) AIGLX: Screen 0 is not DRI capable
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb7ae8004 in ?? ()
> (gdb) where
> #0 0xb7ae8004 in ?? ()
> #1 0x2ab0c800 in ?? ()
> #2 0x00000108 in ?? ()
> #3 0xcdf86800 in ?? ()
> #4 0xf09cd0bf in ?? ()
> #5 0x000000b7 in ?? ()
> #6 0xb203e400 in ?? ()
> #7 0x2ab0c8b7 in ?? ()
> #8 0x00000108 in ?? ()
> #9 0xcdf86800 in ?? ()
> #10 0xb06497bf in ?? ()
> #11 0xe2fff4b7 in ?? ()
> #12 0xe31120b7 in ?? ()
> #13 0x2ab0c8b7 in ?? ()
> #14 0xcdf80808 in ?? ()
> #15 0xd5af7ebf in ?? ()
> #16 0xe31120b7 in ?? ()
> #17 0xaea274b7 in ?? ()
> #18 0x23d150b7 in ?? ()
> #19 0x2ab68808 in ?? ()
> #20 0xc6d02c08 in ?? ()
> #21 0xf11ff406 in ?? ()
> #22 0x23d150b7 in ?? ()
> ---Type <return> to continue, or q <return> to quit---
> #23 0xaea27408 in ?? ()
> #24 0xcdf850b7 in ?? ()
> #25 0xf04102bf in ?? ()
> #26 0x23d308b7 in ?? ()
> #27 0x00000008 in ?? ()
> #28 0x00000100 in ?? ()
> #29 0x00000100 in ?? ()
> #30 0x2ab6e000 in ?? ()
> #31 0x00000108 in ?? ()
> #32 0x00000000 in ?? ()
> (gdb)
> (gdb) c
> Continuing.
>
> Backtrace:
> 0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80c8591]
> 1: [0xb7ef5420]
>
> Fatal server error:
> Caught signal 11. Server aborting
>
>
> Program received signal SIGABRT, Aborted.
> 0xb7d1ad86 in raise () from /lib/libc.so.6
Even if there is few information in the above, I think i am going to
report this upstream anyway since you never got it to work and my
reading of code does not show anything that could make Xorg work on your
processor.
Brice
Reply to: