On Sun, Aug 18, 2024 at 11:58:33AM +0100, Stuart Henderson wrote:
> On 2024/08/18 09:09, Walter Alejandro Iglesias wrote:
> > I still don't understand how gdb(1) works.  Today I ran the same command
> > against the same Xorg.core file but I got different messages.  The whole
> > egdb output:
> > 
> > $ egdb -q $(which X) Xorg.core
> > Reading symbols from /usr/X11R6/bin/X...
> [...]
> > warning: .dynamic section for "/usr/lib/libc.so.100.3" is not at the 
> > expected address (wrong library or version mismatch?)
> 
> You presumably rebooted between generating the core and trying to use
> gdb and triggered the "library_aslr" mechanism, so the libc.so that you
> now have is useless for debugging with that core.
> 

Oh, I see, because the "reordering libraries"!  Then those messages I
got were not related to the bug.  The bad news is now I compiled
xenocara with debug symbols and egdb still shows nothing (this time I
didn't reboot):

$ egdb $(which X) Xorg.core
Reading symbols from /usr/X11R6/bin/X...
BFD: warning: /home/morlock/Xorg.core is truncated: expected core file size >= 
22428072, found: 1710504
[New process 138511]
[New process 289405]
[New process 532913]
[New process 443937]
Cannot access memory at address 0x255deaa5048
Cannot access memory at address 0x255deaa5040
Core was generated by `Xorg'.
Program terminated with signal SIGABRT, Aborted.
#0  0x000002564bc0643b in ?? ()
[Current thread is 1 (process 138511)]
(gdb) bt
#0  0x000002564bc0643b in ?? ()
Backtrace stopped: Cannot access memory at address 0x7739cdf761e0
(gdb) thread 2
[Switching to thread 2 (process 289405)]
#0  0x000002564bc10f7b in ?? ()
(gdb) bt
#0  0x000002564bc10f7b in ?? ()
Backtrace stopped: Cannot access memory at address 0x2569976dcc0
(gdb) thread 3
[Switching to thread 3 (process 532913)]
#0  0x000002564bc10f7b in ?? ()
(gdb) bt
#0  0x000002564bc10f7b in ?? ()
Backtrace stopped: Cannot access memory at address 0x25679aae6a0
(gdb) thread 4
[Switching to thread 4 (process 443937)]
#0  0x000002564bc10f7b in ?? ()
(gdb) bt
#0  0x000002564bc10f7b in ?? ()
Backtrace stopped: Cannot access memory at address 0x256444dbe10
(gdb)

-- 
Walter

Reply via email to