This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
RE: Breakpoints
- To: "'Kevin Buettner'" <kevinb at cygnus dot com>
- Subject: RE: Breakpoints
- From: David Williams <davidwilliams at ozemail dot com dot au>
- Date: Wed, 22 Dec 1999 14:57:43 +1100
- Cc: "'gdb mail list'" <gdb at sourceware dot cygnus dot com>
- Organization: DLC software P/L
- Reply-To: "davidwilliams at ozemail dot com dot au" <davidwilliams at ozemail dot com dot au>
Being a 68K core it can single step (at assembly level) using trace
interrupt facility of the core. Ie the CPU hardware does the single
stepping. I was more concerned in the case when stepping at the source
code level (c source in my case) that GDB may have to set more than one
breakpoint.
Dave.
----------
From: Kevin Buettner[SMTP:kevinb@cygnus.com]
Sent: Wednesday, December 22, 1999 2:53 PM
To: davidwilliams@ozemail.com.au; 'gdb mail list'
Subject: Re: Breakpoints
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.
Kevin