wdb debugger Post: 11351

Sponsored Content

Top Forums Programming wdb debugger Post 11351 by PxT on Monday 3rd of December 2001 03:34:31 PM

12-03-2001

Registered User

As I understand it, wdb is just a front-end to gdb. If so, you can "jump" past any function easily. For example, if you are debugging the following code:

Code:

printf("hello, world\n");
this_is_my_function();
printf("goodbye, world\n");

as you are stepping through the code -- lets say you are at line 1 -- you can enter "jump 3" to jump immediately to line 3 thereby skipping line 2 and the function call entirely. If you want to automatically skip a function as the program runs (with no input needed), you might give the following commands to the debugger:

Code:

break this_is_my_function
commands
return
continue
end

That would tell gdb to stop at the specified function, and automatically execute the commands "return" and "continue" which would have the same effect as skipping the function entirely.

PxT

View Public Profile for PxT

Find all posts by PxT

2 More Discussions You Might Find Interesting

1. Programming

How to debug with wdb debugger a cobol program?

Hi Forum, i have such a question. I have a cobol program which is calling a C program and in that C program i get a core dump:(. I want to investigate what is the issue using WDB debuger, but a dont see the code from COBOL program in the debuger, when i run the debugger with the exe!!! ...

2. Programming

Alternative debugger to GNU insight debugger

GNU insight debugger is not available now a days and it is required to debug/inspect assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same...

LEARN ABOUT REDHAT

nana

NANA(1) 						      General Commands Manual							   NANA(1)

NAME
       nana - generates debugger commands from C and C++ source code

SYNOPSIS
       nana [cpp-flags] files...

DESCRIPTION
       Generates  gdb(1)  commands  from  the arguments which implement the assertion and logging operations specified by macros such as DI(3) and
       DL(3).  The output of nana(1) can then be sourced into gdb(1) to perform these operations.

       Note that you must provide any C preprocessor flags you are using to nana since these can change the code that is  generated  by  the  com-
       piler.

SEE ALSO
       nana-clg(1), nana(3), I(3), DI(3), L(3), DL(3), Q(3) and nana.info.

       The nana.info file is the primary documentation.

AUTHOR
       Phil Maker <pjm@gnu.org>

																	   NANA(1)