From: Daniel Jacobowitz <drow@false.org>
To: David Lamy-Charrier <david.lamy@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: How to access files (open/read/close) from gdb script ?
Date: Mon, 26 Sep 2005 17:36:00 -0000 [thread overview]
Message-ID: <20050926173638.GC8277@nevyn.them.org> (raw)
In-Reply-To: <6541ed4c05092610342d7d63c1@mail.gmail.com>
On Mon, Sep 26, 2005 at 07:34:10PM +0200, David Lamy-Charrier wrote:
> > > You can launch any command from GDB using the "shell" command.
> > >
> > > Just as a comment regarding TCL, I would personally use anything but
> > > TCL. It's your choice: You can use bourne scripts, or even write a
> > > program in C or Ada...
>
> Thanks a lot for your help,
> but with an external script or program, I can not retrieve results of
> the external program from my gdb script (except maybe the exit_code) ?
>
> Is there anywhere a list of allowed functions from gdb script (I know
> that printf, strcmp... are allowed) ?
They aren't "allowed" per se. You're calling functions in the program
you're debugging when you do this.
You have two options: use "shell" and its limitations, or wrap GDB in
something that processes its input and output, like Expect.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-26 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6541ed4c050926074274c08518@mail.gmail.com>
2005-09-26 14:45 ` David Lamy-Charrier
2005-09-26 14:51 ` Ramana Radhakrishnan
2005-09-26 15:53 ` David Lamy-Charrier
2005-09-26 17:03 ` Joel Brobecker
2005-09-26 17:22 ` Jim Ingham
2005-09-26 17:34 ` David Lamy-Charrier
2005-09-26 17:36 ` Daniel Jacobowitz [this message]
2005-09-27 13:57 ` David Lamy-Charrier
2005-09-27 13:59 ` Daniel Jacobowitz
2005-09-26 17:35 ` Daniel Jacobowitz
2005-09-26 17:42 ` Jim Ingham
2005-09-26 21:48 ` Joel Brobecker
2005-09-26 17:27 ` Jim Ingham
2005-09-26 17:33 ` Daniel Jacobowitz
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=20050926173638.GC8277@nevyn.them.org \
--to=drow@false.org \
--cc=david.lamy@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).