If I set a watchpoint for a variable local to the current scope, it will be auto deleted when going out of the scope. Is there any way to set it once and keep it auto alive whenever entering the same scope?
Is there anyway to set conditional watchpoint, like
watch var1 if var1==0
? In my case, the condition does't work. gdb stops whenevervar1
's value is changed, instead of untillvar1 == 0
is true. My gdb is GNU gdb 6.8-debian.
相关问题
- How to compile C++ code in GDB?
- Invoke and control GDB from c++
- Don't want netbeans debugger to go to disassem
- Setting application affinity in gdb
- pretty print not working for c++ stl list
相关文章
- How to handle all signals in GDB
- Embedding a program's source code into its bin
- Why are there no debug symbols in my vmlinux when
- can't debug small program on eclipse helios cd
- gdb - list source of current function without typi
- ndk-gdb on windows
- Debug a linux kernel module using gdb
- modify values of elements of an array in gdb for C
You can set a watchpoint that does not go out of scope by setting it to the memory address.
This also works for other data types and pointers.
I'm not sure which language us are using, so the exact answer will vary, but could you change the variable to either be static, global, or dynamically allocated (and don't free it when the function returns?). This way it's raw address won't change, and gdb will be able breakpoint on it.
Instead of watching the value whe it equals a specific value; you should set a conditional break point on the line where you want to check the value of
var1
. This should effectively have the same effecte.g.
I agree with Dave that a conditional breakpoint is the way to go.
However, to do what you asked, you can use GDB's
commands
command to set a list of GDB commands to execute whenever a breakpoint is hit. I find this incredibly useful.I suggest writing your GDB commands into a file so that they are easy to edit and easy to reload with the
source
command. Or you can specify command files to load on the GDB command line or use .gdbinit to make them load automatically.An example of a good use of
commands
:Suppose that I have a function
format
that is called by a lot of other functions. I want to break on it, but only after functiondo_step_3
has been called.You could use this for your problem with something like:
You can set conditions on watchpoints in the same way that you do with breakpoints. This is in the documentation but admittedly it hardly calls attention to itself.
So
watch my_var if my_var > 3
works just fine, as does thecondition
command.To recreate the watchpoint if the variable it is watching goes out of scope, have gdb do this automatically using a breakpoint at the start of the function as Zan has described.