From: Daniel Jacobowitz <drow@false.org>
To: Alex Bennee <alexjb@transitive.com>
Cc: gdb@sources.redhat.com
Subject: Re: Fully automating GDB (aka how to make canned command strings see the exit status)
Date: Thu, 16 Mar 2006 17:25:00 -0000 [thread overview]
Message-ID: <20060316171829.GA15821@nevyn.them.org> (raw)
In-Reply-To: <1142529081.5372.14.camel@okra.transitives.com>
On Thu, Mar 16, 2006 at 05:11:21PM +0000, Alex Bennee wrote:
> Hi,
>
> I've got a program I'm trying to debug that crashes on a very
> intermittent basis. I suspect the core dumps I'm getting are incomplete
> so I would like to try and catch the the crash live in gdb.
>
> I figure a canned script to run the program is the answer. However how
> do I tell if the program has exited successfully (in which case I can
> run again) to hitting the SEG and staying put for when I come back in
> the morning?
There's lots of ways you can do this. There's nothing in the GDB
command line scripting language that will work, but you can drive
GDB using something like "expect" instead; have the expect script stop
when it sees a SIGSEGV in the output.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-16 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 17:18 Alex Bennee
2006-03-16 17:25 ` Daniel Jacobowitz [this message]
2006-03-16 23:09 ` Andrew STUBBS
2006-03-16 17:31 ` Larry Martell
2006-03-16 18:54 ` Ramana Radhakrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060316171829.GA15821@nevyn.them.org \
--to=drow@false.org \
--cc=alexjb@transitive.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox