How to access files (open/read/close) from gdb script ?

How to access files (open/read/close) from gdb script ?

[David Lamy-Charrier]

Hello,

Does anyone of you know how to perform file operations
(open/read/close) from a GDB script ?

Each time GDB stops on a breakpoint I read a value from memory and then
I want to open a file on the host and search for the value in this
file ? any hints ?

Thanks,
David

Re: How to access files (open/read/close) from gdb script ?

[Ramana Radhakrishnan]

On Mon, 2005-09-26 at 16:44 +0200, David Lamy-Charrier wrote:
> Hello,
> 
> Does anyone of you know how to perform file operations
> (open/read/close) from a GDB script ?


Maybe you can integrate this with an expect / tcl script  ? AFAIK gdb
scripting 
does not allow such stuff. 

cheers
Ramana

Re: How to access files (open/read/close) from gdb script ?

[David Lamy-Charrier]

> Maybe you can integrate this with an expect / tcl script  ? AFAIK gdb
> scripting
> does not allow such stuff.

I am not sure to understand correclty:
you mean that I can write a tcl script to do that, but how can I then
launch the tcl script ?

Thanks,
David

Re: How to access files (open/read/close) from gdb script ?

[Joel Brobecker]

> I am not sure to understand correclty:
> you mean that I can write a tcl script to do that, but how can I then
> launch the tcl script ?

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...

-- 
Joel

Re: How to access files (open/read/close) from gdb script ?

[Jim Ingham]

Since ALL the gdb testsuites are written in Tcl (that's what Expect  
uses, and that is consequently what dejagnu uses) this seems a  
particularly unfortunate place to be airing your prejudices.

Jim

On Sep 26, 2005, at 10:03 AM, Joel Brobecker wrote:

>> I am not sure to understand correclty:
>> you mean that I can write a tcl script to do that, but how can I then
>> launch the tcl script ?
>>
>
> 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...
>
> -- 
> Joel
>

Re: How to access files (open/read/close) from gdb script ?

[David Lamy-Charrier]

> > 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) ?

Thanks,
David

Re: How to access files (open/read/close) from gdb script ?

[Daniel Jacobowitz]

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

Re: How to access files (open/read/close) from gdb script ?

[David Lamy-Charrier]

> > 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.

Thanks for your hints,
but I am using a GUI front-end (Elicpse) for GDB, so I can't process
GDB's input and ouput.
That's why I was trying to do it from a GDB script...


By the way, in a "debugguee" program, is there any way to know if the
program is currently running "in" GDB or if it is freely running
(without debuuger connected) ??


Thanks again,
David

Re: How to access files (open/read/close) from gdb script ?

[Daniel Jacobowitz]

On Tue, Sep 27, 2005 at 03:57:12PM +0200, David Lamy-Charrier wrote:
> By the way, in a "debugguee" program, is there any way to know if the
> program is currently running "in" GDB or if it is freely running
> (without debuuger connected) ??

In general there shouldn't be.  It's supposed to be transparent.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: How to access files (open/read/close) from gdb script ?

[Daniel Jacobowitz]

On Mon, Sep 26, 2005 at 10:23:10AM -0700, Jim Ingham wrote:
> Since ALL the gdb testsuites are written in Tcl (that's what Expect  
> uses, and that is consequently what dejagnu uses) this seems a  
> particularly unfortunate place to be airing your prejudices.

In fact I find it excessively appropriate; they are some of the worst
testsuite codes I've ever had the misfortune to work with and TCL is a
big part of the reason why.  As the currently most active TCL
programmer in the GDB project, I think I've earned the right to agree
with Joel.

If I had the luxury to redo it I'd do it in Anything But TCL, probably
by improving QMTest's support for interactive testing.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: How to access files (open/read/close) from gdb script ?

[Jim Ingham]

I totally disagree with this.  The reason why so much of the gdb  
testsuite is horrible is that it was written by people who never  
bothered to learn Tcl, and instead programmed it wishing it was "sh"  
- which is a pretty perverse thing to wish anyway.

If you take the trouble to actually learn how it works, rather than  
just cutting & pasting examples you don't fully understand, it is a  
perfectly fine language.  Any language will work poorly for you if  
you have decided up front that it's going to do so.

Jim


On Sep 26, 2005, at 10:35 AM, Daniel Jacobowitz wrote:

> On Mon, Sep 26, 2005 at 10:23:10AM -0700, Jim Ingham wrote:
>
>> Since ALL the gdb testsuites are written in Tcl (that's what Expect
>> uses, and that is consequently what dejagnu uses) this seems a
>> particularly unfortunate place to be airing your prejudices.
>>
>
> In fact I find it excessively appropriate; they are some of the worst
> testsuite codes I've ever had the misfortune to work with and TCL is a
> big part of the reason why.  As the currently most active TCL
> programmer in the GDB project, I think I've earned the right to agree
> with Joel.
>
> If I had the luxury to redo it I'd do it in Anything But TCL, probably
> by improving QMTest's support for interactive testing.
>
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
>

Re: How to access files (open/read/close) from gdb script ?

[Joel Brobecker]

> If you take the trouble to actually learn how it works, rather than  
> just cutting & pasting examples you don't fully understand, it is a  
> perfectly fine language.  Any language will work poorly for you if  
> you have decided up front that it's going to do so.

Sorry guys, my intention wasn't really to bash on TCL at all,
just to let him know that TCL was not the only option for writing
his external tool. The point was for him to use whatever language
he's most familiar with, even if it is TCL.

I'm sorry that my personal opinion of the language seeped through,
again, that was not my intention.

-- 
Joel

Re: How to access files (open/read/close) from gdb script ?

[Jim Ingham]

The gdb testsuites are an example of how to do this.  They use  
"expect" to drive gdb and parse it's output.  There are also a lot of  
Tcl helper libraries in the testsuite/lib directory that manage  
stepping, etc.  So one pretty easy option is to use the dejagnu harness.

In any case, you can run the gdb testsuite (using "make check") to  
get an example of how to use Tcl & Expect to script gdb.

Also, if you can get the Insight debugger, that has a Tcl Interpreter  
build into gdb, and you can write scripts and just "source" them in  
Insight.  At that point, you can do anything you could do in plain  
Tcl...

I think DanielJ also has mentioned working on scripting bindings  
using the MI in the past, but I don't know the state of this.  That  
is a little bit more work, but would allow you to run gdb under  
another scripting language if you wanted.

Jim


On Sep 26, 2005, at 8:53 AM, David Lamy-Charrier wrote:

>> Maybe you can integrate this with an expect / tcl script  ? AFAIK gdb
>> scripting
>> does not allow such stuff.
>>
>
> I am not sure to understand correclty:
> you mean that I can write a tcl script to do that, but how can I then
> launch the tcl script ?
>
> Thanks,
> David
>

Re: How to access files (open/read/close) from gdb script ?

[Daniel Jacobowitz]

On Mon, Sep 26, 2005 at 10:28:46AM -0700, Jim Ingham wrote:
> I think DanielJ also has mentioned working on scripting bindings  
> using the MI in the past, but I don't know the state of this.  That  
> is a little bit more work, but would allow you to run gdb under  
> another scripting language if you wanted.

The current state is I'm hoping to piggyback on Nick's current
interpreter work but haven't tried lately.

-- 
Daniel Jacobowitz
CodeSourcery, LLC