From: David Williams <davidwilliams@ozemail.com.au>
To: "kevinb@cygnus.com" <kevinb@cygnus.com>,
"'Mark Salter'" <msalter@cygnus.com>
Cc: "gdb@sourceware.cygnus.com" <gdb@sourceware.cygnus.com>
Subject: RE: Breakpoints
Date: Wed, 22 Dec 1999 13:06:00 -0000 [thread overview]
Message-ID: <01BF4D1C.4AD8ABC0.davidwilliams@ozemail.com.au> (raw)
My question is still does GDB need to set more than one breakpoint when
stepping through source? Thinking about it a little more GDB should have
all of the information available to decide whether a branch will occur. It
has the current value of all the registers (esp CCR) so it can work it out
- the real question is does it use this information?
Dave.
----------
From: Mark Salter[SMTP:msalter@cygnus.com]
Sent: Thursday, December 23, 1999 2:09 AM
To: kevinb@cygnus.com
Cc: davidwilliams@ozemail.com.au; gdb@sourceware.cygnus.com
Subject: Re: Breakpoints
>>>>> Kevin Buettner writes:
> On Dec 22, 2:29pm, David Williams wrote:
>> Does GDB ever need to set more than one breakpoint when stepping through
>> source code? I have not (as yet) seen this type of behaviour.
> Can the target do a singlestep in hardware or do you have to do
> software emulation? If the latter, when you're stepping by machine
> instruction, you'd need two breakpoints on a conditional branch;
> one for the branch target, the other for the instruction after the
> branch.
Even in the latter case, the stub can evaluate the condition of the
branch to see which way its going to go.
--Mark
next reply other threads:[~1999-12-22 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-22 13:06 David Williams [this message]
[not found] <01BF4C88.F6D54B20.davidwilliams@ozemail.com.au>
[not found] ` <991222035342.ZM17881@ocotillo.lan>
1999-12-22 7:09 ` Breakpoints Mark Salter
1999-12-22 15:49 ` Breakpoints J.T. Conklin
2002-12-16 19:57 Breakpoints Satyavathi Malladi
2003-01-27 3:10 gdb_indent vs. dwarf2read Daniel Jacobowitz
2003-01-27 17:30 ` Andrew Cagney
2003-01-27 17:43 ` Daniel Jacobowitz
2003-01-27 20:02 ` breakpoints jacques
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=01BF4D1C.4AD8ABC0.davidwilliams@ozemail.com.au \
--to=davidwilliams@ozemail.com.au \
--cc=gdb@sourceware.cygnus.com \
--cc=kevinb@cygnus.com \
--cc=msalter@cygnus.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