This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Breakpoints

To: David Williams <davidwilliams at ozemail dot com dot au>
Subject: Re: Breakpoints
From: Andrew Cagney <ac131313 at cygnus dot com>
Date: Tue, 04 Jan 2000 22:45:03 +1100
CC: gdb mail list <gdb at sourceware dot cygnus dot com>
Organization: Cygnus Solutions
References: <01BF4D1C.4AD8ABC0.davidwilliams@ozemail.com.au> <3870B8E0.B4BB4034@haulpak.com> <38711A49.C239221D@ozemail.com.au> <38715252.4AFCF918@cygnus.com> <3871C994.17394AF5@ozemail.com.au>

David Williams wrote:
> 
> Thanks,
> 
> So some targets may set multiple breakpoints. What I want to know is does 68K support
> in gdb ever need to set multiple breakpoints? Which part of source code should I check
> to see? I have had a quick look but got hopelessly lost I have not looked at the source
> for gdb before.

It happens when the instruction being stepped over is a branch.  GDB
figures out all possible branch destinations (which can get complex) and
sets a breakpoint at each one.

Look for the macro SOFTWARE_SINGLE_STEP / *_single_step().

As for the 68k - I don't think so.  It doesn't define
SOFTWARE_SINGLE_STEP_P.

	Andrew

References:
- Re: Breakpoints
  - From: William Gatliff
- Re: Breakpoints
  - From: David Williams
- Re: Breakpoints
  - From: Andrew Cagney
- Re: Breakpoints
  - From: David Williams

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]