bug-ddd
[Top][All Lists]
Advanced

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

Re: DDD 3.3.1 (i686-pc-linux-gnu) gets `Segmentation fault' signal (fwd)


From: Arnaud Desitter
Subject: Re: DDD 3.3.1 (i686-pc-linux-gnu) gets `Segmentation fault' signal (fwd)
Date: Thu, 5 Jul 2001 10:03:08 +0100 (BST)

Date: Thu, 05 Jul 2001 12:39:55 +1000 (EST)
From: Jens Troeger <savage@light-speed.de>
Subject: Re: DDD 3.3.1 (i686-pc-linux-gnu) gets `Segmentation fault' signal
To: arnaud.desitter@nag.co.uk
Reply-to: savage@light-speed.de

> > > i use RH7.1, 128 memory and was about to debug a big application. the 
> > > system
> > > is usually busy swapping... anyway, i modified the application, 'run'ed it
> > > again and that was too much :-)
> > > 
> > > attached please find the log and the core!
> > 
> > well actually i TAB'ed to list all the method names which start with
> > 'interpret' for a given class to add a breakpoint at one of those methods:
> > 
> > gdb> break SSInterpreter::interpret[TAB]
> > 
> > here it started to be busy till the crash!
> > 
> > sorry,
> > jens
> > 
> 
> Maybe a pie in the sky: can you apply the patch available at
> http://mail.gnu.org/pipermail/ddd/2001-May/000874.html
> and tell us if the memory problem gets better ?

and sth else happens. when i 'graph display' some valye explicitely as, say,
hex, the graph header is then '/x *v' or so. then clicking to a member of v
delivers an error

  (gdb) graph display *((/x *v)._type) dependent on 43
  A parse error in expression, near *v)._type)'.

because of the '/x'
if i retype the stuff without that it works

  (gdb) graph display *((*v)._type) dependent on 43

just a remark
jens

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.



reply via email to

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