Message-ID: <87BC54A997CCD01198930020AFF6011C270EDF@mail.rkk.cz>
From: "Holejsovsky, Pavel" <PHolejs AT rkk DOT cz>
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
Cc: djgpp AT delorie DOT com
Subject: RE: RHIDE misfeature ?
Date: Fri, 11 Jul 1997 11:54:58 +0200
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

On Thursday, July 10, 1997 5:45 PM, Salvador Eduardo Tropea (SET)
[SMTP:salvador AT inti DOT edu DOT ar] wrote:
> Pierre Muller wrote:
> 
> >    When my program makes a SEGMENT violation
> > 
> >   I would like to see the stack where the program crashed
> > 
> > but it seems that RHIDE sends a kill to GDB before giving the hand
back to 
> > the user.
> > 
> >   So I have no stack information only the line where it crashed ?
> > 
> >   Could that be changed are is there a good reason why it is so ?
> 
> Run the exe without breakpoints, in this way gdb is not used and
you'll see the 
> stack trace.
> 

Umm, this is more hack-workaround, it still does not explain why rhide
kills SIGSEGVing process.
No offence to Robert, of course, but I'd like RHIDE to behave as GDB,
which stops process (but does not kill it) in such situation and you are
able to examine not only stack backtrace, but also all variables etc..
I think that this would be very helpfull when debugging SIGSEGving
program.

Pavel