This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: break of close loop
- From: 'Daniel Jacobowitz' <drow at false dot org>
- To: Simon Richter <Simon dot Richter at hogyros dot de>
- Cc: Dave Korn <dave dot korn at artimi dot com>, 'Efim Monjak' <ymonyak at lipowsky dot de>,gdb at sources dot redhat dot com
- Date: Fri, 4 Nov 2005 10:39:45 -0500
- Subject: Re: break of close loop
- References: <SERRANObieLYCT4aJ6p00000174@SERRANO.CAM.ARTIMI.COM> <436B7BE1.5040702@hogyros.de>
On Fri, Nov 04, 2005 at 04:18:57PM +0100, Simon Richter wrote:
> Hi,
>
> Dave Korn wrote:
>
> > The stub is probably implemented by placing a temp breakpoint immediately
> >after the instruction to be tested, but has negelected the fact that to
> >handle
> >jumps you may need to place the temp breakpoint somewhere _other_ than
> >immediately after the instruction,
>
> The question at hand appears to be breakpoints placed on top of the
> instruction being stepped, as the instruction steps back to itself. This
> is especially common on architectures with a dedicated "decrement and
> jump if not zero" instruction.
If you have such instructions, and you don't have hardware single step,
then you need to be prepared to either wait for the instruction to
finish or else interrupt it. I don't see the problem.
--
Daniel Jacobowitz
CodeSourcery, LLC