GNU bug report logs -
#11395
24.0.96; Sporadic crashing
Previous Next
Reported by: Richard Stanton <stanton <at> haas.berkeley.edu>
Date: Wed, 2 May 2012 20:40:02 UTC
Severity: normal
Tags: moreinfo
Found in version 24.0.96
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #68 received at 11395 <at> debbugs.gnu.org (full text, mbox):
On 5/17/12 5:00 AM, "Chong Yidong" <cyd <at> gnu.org> wrote:
>Richard Stanton <stanton <at> 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)
This bug report was last modified 9 years and 150 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.