bug#11395: 24.0.96; Sporadic crashing

[Lars Ingebrigtsen]

Richard Stanton <stanton@haas.berkeley.edu> writes:

> On 5/17/12 5:00 AM, "Chong Yidong" <cyd@gnu.org> wrote:
>
>>Richard Stanton <stanton@haas.berkeley.edu> writes:
>>
>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>> Reason: 13 at address: 0x0000000000000000
>>> 0x00000001001cf0a4 in mem_insert (start=0x10fa29010, end=0x10fa29088,
>>> type=MEM_TYPE_VECTORLIKE) at alloc.c:3585
>>> 3585              c = start < c->start ? c->left : c->right;
>>> (gdb) bt
>>> #0  0x00000001001cf0a4 in mem_insert (start=0x10fa29010,
>>>end=0x10fa29088,
>>> type=MEM_TYPE_VECTORLIKE) at alloc.c:3585
>>> #1  0x00000001001cb45e in lisp_malloc (nbytes=120,
>>> type=MEM_TYPE_VECTORLIKE) at alloc.c:918
>>
>>Please keep the gdb session alive, thanks.
>>
>>Could you do
>>
>>f 0
>>p *c
>>
>>and show the results?
>
> (gdb) f 0
> #0  0x00000001001cf0a4 in mem_insert (start=0x10fa29010, end=0x10fa29088,
> type=MEM_TYPE_VECTORLIKE) at alloc.c:3585
> 3585        c = start < c->start ? c->left : c->right;
> (gdb) p *c
> Cannot access memory at address 0x1cc1000000000000
> (gdb) 

Is this issue still a problem?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no