From mboxrd@z Thu Jan  1 00:00:00 1970
From: Elena Zannoni <ezannoni@cygnus.com>
To: Dmitry Sivachenko <dima@Chg.RU>
Cc: gdb@sources.redhat.com
Subject: Re: please explain some terms!
Date: Sun, 20 Aug 2000 11:18:00 -0000
Message-id: <200008201817.LAA03017@critters.cygnus.com>
References: <2818304729.20000819234724@Chg.RU>
X-SW-Source: 2000-08/msg00085.html

Dmitry Sivachenko writes:
 > Hello all!
 > 
 > 1) Could someone please explain the meaning of the word 'flathead',
 > found in gdbmi.texinfo?

Hmm...., er,.... Flathead is a fish. This was the internal name we
gave to the GDB MI project. :-)


 > 
 > 2) What are 'mode', 'member mode', 'varying mode' and 'instance mode'
 > (these are Chill terms, found in gdb.texinfo).
 > 

I don't know about these, sorry.

 > Any help will be greatly appreciated.
 > 
 > Thank you in advance,
 > Dmitry.
 > 
 > 
 > 

Elena
>From kistler@cs.utexas.edu Sun Aug 20 18:27:00 2000
From: Mike Kistler <kistler@cs.utexas.edu>
To: gdb@sources.redhat.com
Subject: Just-In-Time debugging with GDB
Date: Sun, 20 Aug 2000 18:27:00 -0000
Message-id: <39A08630.7E36E60@cs.utexas.edu>
X-SW-Source: 2000-08/msg00086.html
Content-length: 1265

Hello,

I am interested in doing "just-in-time" debugging with gdb.  The basic
idea is to launch the program normally (not under the debugger), but
if an error occurs (e.g. memory protection exception), the debugger
magically launches and attaches to the program at the point of error.
The program could also cause the debugger to launch using a call to
some special procedure. This is available on other platforms and I
have used it quite a bit.  Perhaps it is also available in gdb ... if
so,
I would really appreciate a pointer to some information on it.

I have been trying to engineer a crude version of this on my own,
and it kinda works.  However, I would like to disable it if I decide
to launch the program under gdb (I don't need 2 debug sessions
for the same program!).  I thought I could determine if gdb was
already active by checking the signal handler for SIGINT.  I
figured that gdb would have installed a signal handler for this, and
thus if gdb was already running, the handler for SIGINT would
not be SIG_DFL.  Unfortunately, this is apparently not so.  Is
there some technique I can use to determine if my program is
running under the control of gdb?

Many thanks in advance to anyone that can provide guidance on
these issues.

Mike Kistler