[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nil became bound to (#<save_value ptr=0x085526f0 int=0> 96536 96288)

From: Eli Zaretskii
Subject: Re: nil became bound to (#<save_value ptr=0x085526f0 int=0> 96536 96288)
Date: Sat, 25 Feb 2006 13:56:02 +0200

> From: Joe Wells <address@hidden>
> Date: Fri, 24 Feb 2006 00:26:15 +0000
> Cc: address@hidden, address@hidden
> I attached gdb to the crippled-but-not-dead-yet process.
> Cross-checking with the source code, I wasn't able to figure out how
> to make any sense of the data at 0x08554f28.  I somehow doubt this
> will help, but in case this is somehow easy here is what gdb reported
> as the contents of the 8 words (32 bytes) starting at that location:
> (gdb) x/8xw 0x08554f28
> 0x8554f28:    0x084bf340      0x085544c0      0x00000004      0x00000003
> 0x8554f38:    0x0000000b      0x00000000      0x085544e8      0x00a00000

Does the GDB command "info symbol 0x08554f28" display something
useful?  Also try "print/a 0x08554f28".

I agree with Andreas that putting a watchpoint on Qnil's address and
on its obarray entry (and on any other places thru which Qnil can be
modified) is the best strategy, given the data you've gather so far.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]