gdb basic questions

gdb basic questions

[nagaraju.m]

Hi Ranjith,


    You can use -x option and link a command file which will take 
commands from the input file


     open a new file:
 
     Then type the commands you want to give input to gdb
   
    tar simulator
    load
    b main
    r
    info reg
    c
    q
   
then call gdb  -x option

 [nagaraju@nagaraju nagaraju]$ gdb a.out -x gdb.cmd



Good luck,
Nagaraju M
   

gdb basic questions

[ranjith kumar]

hi,
I am new to gdb. I have 3 questions.

Suppose that we want to keep a breakpoint at a function say
'myfunction', we will a gdb command
(gdb) b myfunction
at  gdb command prompt.

What I want is keep breakpoints at, say, 1000 functions.
 But I cant type 1000 times '(gdb)  b functionname'.
1) Is there any way to keep breakpoints at 1000 functions,  without
typing ?( Assume I have saved all 1000 funcion names in a file)

2) Generally, is it possible to ask gdb to go and read 'gdb commands'
from a file?

3) Another question. Sometimes gdb diplays a message like below and
waits for user to type 'y or n'.
"Make breakpoint pending on future shared library load? (y or [n]) "
How to tell gdb to not to wait for input from user and assume that
user has typed 'y' always ?

Thanks in advance.

Re: gdb basic questions

[Jan Kratochvil]

On Sun, 15 Nov 2009 12:41:18 +0100, ranjith kumar wrote:
> 1) Is there any way to keep breakpoints at 1000 functions,  without
> typing ?( Assume I have saved all 1000 funcion names in a file)
+
> 2) Generally, is it possible to ask gdb to go and read 'gdb commands'
> from a file?

(gdb) help source
Read commands from a file named FILE.
Optional -v switch (before the filename) causes each command in
FILE to be echoed as it is executed.
Note that the file ".gdbinit" is read automatically in this way
when GDB is started.
Optional -p switch (before the filename) causes FILE to be evaluated
as Python code.


> 3) Another question. Sometimes gdb diplays a message like below and
> waits for user to type 'y or n'.
> "Make breakpoint pending on future shared library load? (y or [n]) "
> How to tell gdb to not to wait for input from user and assume that
> user has typed 'y' always ?

(gdb) set breakpoint pending on
(gdb) help set breakpoint pending 
Set debugger's behavior regarding pending breakpoints.
If on, an unrecognized breakpoint location will cause gdb to create a
pending breakpoint.  If off, an unrecognized breakpoint location results in
an error.  If auto, an unrecognized breakpoint location results in a
user-query to see if a pending breakpoint should be created.

In some other cases one needs:

(gdb) set confirm off 
(gdb) help set confirm 
Set whether to confirm potentially dangerous operations.


Regards,
Jan