From: Daniel Jacobowitz <drow@false.org>
To: Efim Monjak <ymonyak@lipowsky.de>
Cc: gdb@sources.redhat.com
Subject: Re: break of close loop
Date: Thu, 03 Nov 2005 21:25:00 -0000 [thread overview]
Message-ID: <20051103212546.GC11828@nevyn.them.org> (raw)
In-Reply-To: <4368EC1E.3000300@lipowsky.de>
On Wed, Nov 02, 2005 at 05:41:02PM +0100, Efim Monjak wrote:
> Hi all,
>
> if it is need to stop in the small loop i.e.:
> for(;;)
> ;
> which is compiled as one opcode:
> lable:
> jmp lable:
>
> GDB works fine by "continue" and "stepi" commands: it sends ctrl+c
> receive the break address and doing no more, but by "step" command
> it try to do a one step after break address is received. The break address
> is the "lable" address and this step starts the loop another time.
>
> Hier is the part of protocol
> (gdb) c
> Continuing.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> main () at ../src/main.c:95
> 95 ;
> (gdb) c
> Continuing.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> main () at ../src/main.c:95
> 95 ;
> (gdb) set debug remote 1
> (gdb) stepi
> Sending packet: $s#73...Ack
> remote_interrupt called
> remote_stop called
Why is the step packet not single-stepping the target? Why do you need
to use C-c to stop the target? This is a problem with your stub.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-03 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 16:41 Efim Monjak
2005-11-03 21:25 ` Daniel Jacobowitz [this message]
2005-11-04 9:15 Efim Monjak
2005-11-04 14:27 ` Daniel Jacobowitz
2005-11-04 15:13 ` Dave Korn
2005-11-04 15:19 ` Simon Richter
2005-11-04 15:35 ` Dave Korn
2005-11-04 15:39 ` 'Daniel Jacobowitz'
2005-11-04 15:46 ` Dave Korn
2005-11-04 16:00 ` 'Daniel Jacobowitz'
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=20051103212546.GC11828@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ymonyak@lipowsky.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).