Re: how to include subdirectories too, for the source directory

Re: how to include subdirectories too, for the source directory

[Michael Elizabeth Chastain]

How about:

  gdb $(find /home -type d -print | sed -e 's/.*/--directory=&')

Michael C

Pending breakpoints and scripts

[Andrew Cagney]

Anyone noticed this?

(top-gdb) run testsuite/gdb.base/advance
Starting program: ...
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Breakpoint 1 (internal_error) pending.
Function "info_command" not defined.
Breakpoint 2 (info_command) pending.
(top-gdb)

It's caused by this:

           if (!query ("Make breakpoint pending on future shared library 
load? ")
)
             return rc;

The old behavior was: when in batch mode, throw an error (and hence 
abandon the script) if the breakpoint insert fails.

The new behavior is: when in batch mode, always insert the breakpoint. 
when not in batch mode never throw an error.

For the existing behavior to be restored the query's logic would need to 
be reversed (ask the oposite question) and then re-throw the error.  A 
/pending qualifier could then be added.

Thoughts?
Andrew

Re: Pending breakpoints and scripts

[Daniel Jacobowitz]

On Mon, Feb 09, 2004 at 03:02:19PM -0500, Andrew Cagney wrote:
> Anyone noticed this?
> 
> (top-gdb) run testsuite/gdb.base/advance
> Starting program: ...
> Setting up the environment for debugging gdb.
> Function "internal_error" not defined.
> Breakpoint 1 (internal_error) pending.
> Function "info_command" not defined.
> Breakpoint 2 (info_command) pending.
> (top-gdb)
> 
> It's caused by this:
> 
>           if (!query ("Make breakpoint pending on future shared library 
> load? ")
> )
>             return rc;
> 
> The old behavior was: when in batch mode, throw an error (and hence 
> abandon the script) if the breakpoint insert fails.
> 
> The new behavior is: when in batch mode, always insert the breakpoint. 
> when not in batch mode never throw an error.
> 
> For the existing behavior to be restored the query's logic would need to 
> be reversed (ask the oposite question) and then re-throw the error.  A 
> /pending qualifier could then be added.
> 
> Thoughts?

I'd rather not reverse the question.  We could check from_tty at the
call site, and not set pending breakpoints if no tty...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: Pending breakpoints and scripts

[Andrew Cagney]

> On Mon, Feb 09, 2004 at 03:02:19PM -0500, Andrew Cagney wrote:
> 
>> Anyone noticed this?
>> 
>> (top-gdb) run testsuite/gdb.base/advance
>> Starting program: ...
>> Setting up the environment for debugging gdb.
>> Function "internal_error" not defined.
>> Breakpoint 1 (internal_error) pending.
>> Function "info_command" not defined.
>> Breakpoint 2 (info_command) pending.
>> (top-gdb)
>> 
>> It's caused by this:
>> 
>>           if (!query ("Make breakpoint pending on future shared library 
>> load? ")
>> )
>>             return rc;
>> 
>> The old behavior was: when in batch mode, throw an error (and hence 
>> abandon the script) if the breakpoint insert fails.
>> 
>> The new behavior is: when in batch mode, always insert the breakpoint. 
>> when not in batch mode never throw an error.
>> 
>> For the existing behavior to be restored the query's logic would need to 
>> be reversed (ask the oposite question) and then re-throw the error.  A 
>> /pending qualifier could then be added.
>> 
>> Thoughts?
> 
> 
> I'd rather not reverse the question.  We could check from_tty at the
> call site, and not set pending breakpoints if no tty...

Why?

Re: Pending breakpoints and scripts

[Daniel Jacobowitz]

On Tue, Feb 10, 2004 at 04:22:41PM -0500, Andrew Cagney wrote:
> >On Mon, Feb 09, 2004 at 03:02:19PM -0500, Andrew Cagney wrote:
> >
> >>Anyone noticed this?
> >>
> >>(top-gdb) run testsuite/gdb.base/advance
> >>Starting program: ...
> >>Setting up the environment for debugging gdb.
> >>Function "internal_error" not defined.
> >>Breakpoint 1 (internal_error) pending.
> >>Function "info_command" not defined.
> >>Breakpoint 2 (info_command) pending.
> >>(top-gdb)
> >>
> >>It's caused by this:
> >>
> >>          if (!query ("Make breakpoint pending on future shared library 
> >>load? ")
> >>)
> >>            return rc;
> >>
> >>The old behavior was: when in batch mode, throw an error (and hence 
> >>abandon the script) if the breakpoint insert fails.
> >>
> >>The new behavior is: when in batch mode, always insert the breakpoint. 
> >>when not in batch mode never throw an error.
> >>
> >>For the existing behavior to be restored the query's logic would need to 
> >>be reversed (ask the oposite question) and then re-throw the error.  A 
> >>/pending qualifier could then be added.
> >>
> >>Thoughts?
> >
> >
> >I'd rather not reverse the question.  We could check from_tty at the
> >call site, and not set pending breakpoints if no tty...
> 
> Why?

Well, how would you word it?  It makes more intuitive sense to me to
answer 'y' to create something special and 'n' to do nothing, than the
other way around.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

System calls debugging

[MuthuKumar-Hotpop]

Hello deBUGies,

        Is there any way to debug what are all the "system calls" usage and process happening over on the program.

        I have written a simple program which gets the a string.I have made it to wait for the input and using that process-id,
        I have attached the process with gdb.Now the "where" command gives the stackframes about the system calls information.
        To find the processings of other system calls what is the way.  
             
Regards,
Muthu.

how to include subdirectories too, for the source directory

[murugesan]

Hello all,
    I need to include a directory (including it's subdirectories ). I did
that with
gdb --directory=home --directory=/home/sub1 --directory=/home/sub2
............

Is there a way to get out from this riddle to include recursively the
subdirectories.

Thanks
Murugesan

Re: how to include subdirectories too, for the source directory

[Bob Rossi]

On Thu, Feb 12, 2004 at 03:27:40PM +0530, murugesan wrote:
> Hello all,
>     I need to include a directory (including it's subdirectories ). I did
> that with
> gdb --directory=home --directory=/home/sub1 --directory=/home/sub2
> ............
> 
> Is there a way to get out from this riddle to include recursively the
> subdirectories.

Generate the names given a directory with a command. For example,
(find directoryName -type d | perl -pi -e 's/(.*)/--directory=$1/')
That will generate a '--directory=dir' for every directory in
directoryName. 

What you need looks like it can easily be accomplished outside of GDB.

Bob Rossi

Re: how to include subdirectories too, for the source directory

[murugesan]

Thanks BOB &Michael.
I am off way in my attempt.

Regards,
Murugesan
----- Original Message ----- 
From: Bob Rossi 
To: murugesan 
Cc: gdb@sources.redhat.com 
Sent: Thursday, February 12, 2004 6:37 PM
Subject: Re: how to include subdirectories too, for the source directory


On Thu, Feb 12, 2004 at 03:27:40PM +0530, murugesan wrote:
> Hello all,
>     I need to include a directory (including it's subdirectories ). I did
> that with
> gdb --directory=home --directory=/home/sub1 --directory=/home/sub2
> ............
> 
> Is there a way to get out from this riddle to include recursively the
> subdirectories.

Generate the names given a directory with a command. For example,
(find directoryName -type d | perl -pi -e 's/(.*)/--directory=$1/')
That will generate a '--directory=dir' for every directory in
directoryName. 

What you need looks like it can easily be accomplished outside of GDB.

Bob Rossi