© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
> Where does it say error? :) It's just the backtrace at the time gdb attaches to
> the process, which implicitly stops its execution.
Ok, sorry about that :*), I'm not that used to gdb yet. After the handle and continuing, when I change to a VT I get the following gdb log:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1477245248 (LWP 13740)]
0x48eed2d0 in main_arena () from /lib/libc.so.6
(gdb) bt f
#0 0x48eed2d0 in main_arena () from /lib/libc.so.6
No symbol table info available.
#1 0x00000000 in ?? ()
No symbol table info available.
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x48eed2d0 in main_arena () from /lib/libc.so.6
(gdb) bt
#0 0x48eed2d0 in main_arena () from /lib/libc.so.6
#1 0xa7de8aff in RADEONRestore (pScrn=0x82186b8) at radeon_
#2 0xa7de8ea5 in RADEONLeaveVT (scrnIndex=0, flags=0) at radeon_
#3 0xa7c2fbe5 in XAALeaveVT (index=0, flags=0) at xaaInit.c:694
#4 0x080bb91a in xf86XVLeaveVT (index=0, flags=0) at xf86xv.c:1278
#5 0xa7eb510f in ?? () from /usr/lib/
#6 0x00000000 in ?? ()
The first sigsegv seems inside glibc, as I have to continue to get the xorg one. Unfortunately I don't have glibc with USE=debug; if necesary I will recompile it but I foresee major breakage, even not changing versions if I do that. Just in case, glibc is 2.6.1 with useflags (glibc-omitfp nls -debug -glibc-compat20 -hardened -multilib -profile -selinux).
As I saw something about XAA I tried with EXA instead, but the backtrace is pretty much the same, just without the XAALeaveVT line:
(gdb) bt
#0 0x48eed2d0 in main_arena () from /lib/libc.so.6
#1 0xa7dadaff in RADEONRestore (pScrn=0x82186b8) at radeon_
#2 0xa7dadea5 in RADEONLeaveVT (scrnIndex=0, flags=0) at radeon_
#3 0x080bb91a in xf86XVLeaveVT (index=0, flags=0) at xf86xv.c:1278
#4 0xa7e7a10f in ?? () from /usr/lib/
#5 0x00000000 in ?? ()