Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Sun, 11 Dec 2005 15:34:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.61.0512111028360.12642@trifle.umiacs.umd.edu> (raw)
In-Reply-To: <8f2776cb0512101044h7e870480i74b03b9058e54574@mail.gmail.com>


Hello Jim,


On Sat, 10 Dec 2005, Jim Blandy wrote:

> On 12/10/05, Grazia Russo-Lassner <glassner@umiacs.umd.edu> wrote:
>> the function BuildVcb is where the error message of my code comes from:
>>
>> line50 : parser->BuildVcb(arg1, arg2);
>
> So, 'BuildVcb' is a method of whatever class 'parser' points to; and
> when you call 'parser->BuildVcb', that code prints an error message;
> is that right?

 	the code exits  and  prints out the error message that was
 	coded 	in that function.
 	I know it has to do with the input file to that function,
 	BuildVcb.
 	I cannot pinpoint the input line that is breaking the code.

 	grazia
>
> What does GDB do when you reach line 50 and type 'step' to step into
> the method call?  Can you show us a transcript?
>


  reply	other threads:[~2005-12-11 15:34 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 [this message]
2005-12-11 15:43       ` Grazia Russo-Lassner
2005-12-11 20:09         ` Jim Blandy
2005-12-12 11:26           ` Grazia Russo-Lassner

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.0512111028360.12642@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