From: Grazia Russo-Lassner <glassner@umiacs.umd.edu>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sources.redhat.com
Subject: Re: how to debug functions called from other classes
Date: Mon, 12 Dec 2005 11:26:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.61.0512120625240.15423@trifle.umiacs.umd.edu> (raw)
In-Reply-To: <8f2776cb0512111209t7d4ba313x3bf9b19553175399@mail.gmail.com>
thank you, Jim.
i am able to step into the function now.
Grazia
On Sun, 11 Dec 2005, Jim Blandy wrote:
> On 12/11/05, Grazia Russo-Lassner <glassner@umiacs.umd.edu> wrote:
>> my question is how tobe able to step into BuildVcb.
>> So far when I "step" the entire output of BuildVcb gets printed out.
>
> So, when the program reaches the line containing the call of the
> BuildVcb method, and you type "step", GDB acts as if you had typed
> "next" or "continue"?
>
> If you ask GDB to "step" into a function or method that has no
> debugging information, GDB will do a "next" instead. Did you compile
> the file that contains the definition of the BuildVcb method with -g?
>
prev parent reply other threads:[~2005-12-12 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 21:48 No symbol table is loaded. Use the "file" command. --- new to gdb: please help ! Grazia Russo-Lassner
2005-12-09 21:49 ` Daniel Jacobowitz
2005-12-10 11:42 ` Grazia Russo-Lassner
2005-12-10 11:48 ` how to debug functions called from other classes Grazia Russo-Lassner
2005-12-10 18:44 ` Jim Blandy
2005-12-11 15:34 ` Grazia Russo-Lassner
2005-12-11 15:43 ` Grazia Russo-Lassner
2005-12-11 20:09 ` Jim Blandy
2005-12-12 11:26 ` Grazia Russo-Lassner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.61.0512120625240.15423@trifle.umiacs.umd.edu \
--to=glassner@umiacs.umd.edu \
--cc=gdb@sources.redhat.com \
--cc=jimb@red-bean.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox