[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DDD 3.3 crashes
From: |
Andreas Zeller |
Subject: |
Re: DDD 3.3 crashes |
Date: |
05 Feb 2001 07:50:25 +0100 |
User-agent: |
Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) |
Hi!
Martin Bickel <bickel@student.uni-kl.de> writes:
> I've just installed the new DDD. It crashed four times this afternoon
> with a segmentation fault. Unfortunately, I can't reproduce any crashes.
> They seem to be quite random and caused by memory corruption. I've taken
> a look at the backtrace on several occasions but couln't find any
> trivial errors like NULL-pointer accesses. [...]
> The previous versions of DDD which I've used over the time were just as
> unstable, but I didn't report it until now because those versions where
> not up to date then.
Sorry - why do you think these versions are out there? To give you
the opportunity to *report* errors, of course. Otherwise, DDD 3.3 may
now have a serious bug nobody knew about so far...
> And I've attached a log file. When this particular log file was created,
> glibc heap consistency checking had been enabled by setting
> MALLOC_CHECK_=2
Hmm... The particular error was caused by a memory corruption in the
LessTif XmText widget (see traceback below). It may be that DDD
itself has caused this corruption, but with MALLOC_CHECK_=2, the
chances are quite small. Do you see any particular message on the
console (such as `freed memory that was already freed' or likewise?)
Also, you may simply try upgrading to LessTif 0.92 or later and see
whether the problem persists; please tell me the results.
Best wishes,
Andreas
#0 0x403f3ab1 in __kill () from /lib/libc.so.6
#0 0x403f3ab1 in __kill () from /lib/libc.so.6
#1 0x403f3785 in raise () at ../sysdeps/posix/raise.c:28
#2 0x403f4e4f in abort () at ../sysdeps/generic/abort.c:139
#3 0x40429096 in free_check (mem=0x86d0ec8, caller=0x401bf473) at malloc.c:4520
#4 0x4042715f in free () at malloc.c:2952
#5 0x401bf473 in XtFree () from /usr/X11R6/lib/libXt.so.6
#6 0x400d574a in RefigureLines (w=0x84c6f20) at Text.c:1052
#7 0x400d5522 in Redisplay (w=0x84c6f20) at Text.c:919
#8 0x400d6280 in _XmTextEnableRedisplay () at Text.c:1644
#9 0x400e8bf3 in Replace (w=0x84c6f20, ev=0x0, startret=0xbffdef30,
endret=0xbffdef34, block=0xbffdef10, call_callback=1 '\001') at TextStrSo.c:475
#10 0x400e968b in _XmStringSourceSetValue () at TextStrSo.c:865
#11 0x400d83ba in XmTextSetString () at Text.c:1644
#12 0x8216c1c in SourceView::read_file (file_name=0xbffdf034,
initial_line=2301, force_reload=false, silent=false) at SourceView.C:2668
#13 0x821bfcf in SourceView::show_execution_position (position=0xbffdf08c,
stopped=false, signaled=false, silent=false) at SourceView.C:3764
#14 0x80db3c8 in command_completed (data=0x8658128) at comm-manag.C:2195
#15 0x81e5bad in GDBAgent::handle_input (this=0x83b7208, answer=@0xbffdf1a8) at
GDBAgent.C:1533
#16 0x81e469c in GDBAgent::InputHP (agent=0x83b7208, call_data=0xbffdf210) at
GDBAgent.C:1212
#17 0x807c3c9 in HandlerList::call (this=0x83b722c, type=10, source=0x83b7208,
call_data=0xbffdf210) at HandlerL.C:152
#18 0x807da7a in LiterateAgent::dispatch (this=0x83b7208, type=10,
data=0x404f7008 "(gdb) ", length=6) at Agent.h:175
#19 0x807db71 in LiterateAgent::inputReady (c=0x83b7208) at LiterateA.C:372
#20 0x807bc4e in AsyncAgent::dispatch (this=0x83b7208, inputId=0xbffff2d8) at
AsyncAgent.C:218
#21 0x807ba0a in AsyncAgent::somethingHappened (client_data=0x83b7208,
fid=0x856841c, inputId=0xbffff2d8) at AsyncAgent.C:106
#22 0x401d7615 in DoOtherSources () from /usr/X11R6/lib/libXt.so.6
#23 0x401d7946 in XtAppNextEvent () from /usr/X11R6/lib/libXt.so.6
#24 0x805660b in process_next_event () at ddd.C:2963
#25 0x81235e5 in ddd_main_loop () at mainloop.C:106
#26 0x8055a73 in main (argc=2, argv=0xbffff754) at ddd.C:2917
--
Andreas Zeller Universitaet Passau
http://www.fmi.uni-passau.de/st/staff/zeller/
- DDD 3.3 crashes, Martin Bickel, 2001/02/04
- Re: DDD 3.3 crashes,
Andreas Zeller <=