From: Pedro Alves <palves@redhat.com>
To: "Maucci, Cyrille" <cyrille.maucci@hp.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: working around batch mode command errors
Date: Tue, 30 Oct 2012 17:39:00 -0000 [thread overview]
Message-ID: <509010B5.6050309@redhat.com> (raw)
In-Reply-To: <7D0928B9A8397D4B9E2F9E5FFFB8D860027BED37@G6W2492.americas.hpqcorp.net>
On 10/28/2012 10:28 PM, Maucci, Cyrille wrote:
> One of the problem I have is that when frame 0 is not C++ code, "print *this" fails and the script aborts with the following error
>
> Error in sourced command file:
> No symbol "this" in current context.
>
> And therefore all subsequent commands are not executed.
> I wanted to know if there would be any possiblity to avoid halting on such errors.
There's no try/catch mechanism in the CLI unfortunately, but I think you could
come up with one in python gdb. ISTR Tromey had a python command wrapper that
swallows CLI errors?
> An aside question would be is there any built-in commands allowing to do something like
>
> for each frame do
> info source
> info args
> info locals
> info frame
> info all-registers
> print *this
> done
Nope. But could construct something like that using gdb's builtin python support.
--
Pedro Alves
next prev parent reply other threads:[~2012-10-30 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 22:28 Maucci, Cyrille
2012-10-30 17:27 ` Jan Kratochvil
2012-10-30 17:39 ` Pedro Alves [this message]
2012-10-30 17:43 ` Tom Tromey
2012-11-01 20:30 ` Doug Evans
2012-11-01 20:38 ` Tom Tromey
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=509010B5.6050309@redhat.com \
--to=palves@redhat.com \
--cc=cyrille.maucci@hp.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).