From: Eli Zaretskii <eliz@gnu.org>
To: matze999@gmx.net
Cc: gdb@sourceware.org
Subject: Re: basic gdb usage question
Date: Tue, 26 Jun 2007 03:12:00 -0000 [thread overview]
Message-ID: <uabuno1dc.fsf@gnu.org> (raw)
In-Reply-To: <200706251708.34817.matze999@gmx.net> (message from Matt Funk on Mon, 25 Jun 2007 17:08:34 -0600)
> From: Matt Funk <matze999@gmx.net>
> Date: Mon, 25 Jun 2007 17:08:34 -0600
>
> I am just starting to use gdb and so have a lot to learn.
Welcome!
> So i want to set the breakpoint in file A at line M under condition X.
> However, another condition that needs to be met before breaking is in file B
> with condition Y.
>
> condition X: the value of a local variable is (say) 2.
> condition Y: the value of a variable is (say) 3.
>
> Is this possible to set multiple conditions for one breakpoint?
A condition could be complex: var1 == 2 && var2 == 3. Would that do
the job?
> I thought
> about setting two breakpoints but that would not do what i need it to do.
Why not? You could set the second breakpoint from the commands
defined for the first breakpoint. Would this do what you want?
> Along the same lines, is it then possible to create a condition that
> references a variable outside the local scope?
AFAIK, only if it has global scope in its file. You can use the
FILE:VARIABLE syntax.
Btw, I'd be eager to know which ones of the answers above cannot be
found in the user's manual. That will help us improve the docs.
next prev parent reply other threads:[~2007-06-26 3:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 16:31 Non-uniform address spaces Michael Eager
2007-06-23 21:25 ` Daniel Jacobowitz
2007-06-23 21:47 ` Michael Eager
2007-06-23 23:09 ` Daniel Jacobowitz
2007-06-25 17:46 ` Jim Blandy
2007-06-25 18:08 ` Michael Eager
2007-06-25 19:05 ` Jim Blandy
2007-06-25 19:09 ` Daniel Jacobowitz
2007-06-25 20:04 ` Michael Eager
2007-06-25 22:23 ` Jim Blandy
2007-06-25 22:55 ` Michael Eager
2007-06-25 23:08 ` basic gdb usage question Matt Funk
[not found] ` <655C3D4066B7954481633935A40BB36F041415@ussunex02.svl.access-company.com>
2007-06-25 23:36 ` Matt Funk
2007-06-26 1:25 ` Michael Eager
2007-06-26 3:12 ` Eli Zaretskii [this message]
2007-06-26 16:13 ` Matt Funk
2007-06-27 3:29 ` Eli Zaretskii
2007-06-26 16:56 ` Non-uniform address spaces Jim Blandy
2007-06-26 17:22 ` Michael Eager
2007-06-26 17:55 ` Jim Blandy
2007-06-26 18:08 ` Jim Blandy
2007-06-26 23:08 ` Michael Eager
2007-06-26 23:39 ` Jim Blandy
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=uabuno1dc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=matze999@gmx.net \
/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