From: Efim Monjak <ymonyak@lipowsky.de>
To: gdb@sources.redhat.com
Subject: Re: break of close loop
Date: Fri, 04 Nov 2005 09:15:00 -0000 [thread overview]
Message-ID: <436B2677.4020802@lipowsky.de> (raw)
Hi,
as I see the step for debugger is not the same as stepi.
After step command debugger try to go to the next source line.
I think it checks for number of source line.
I mean many single steps can be done before an another source
line is recognised. Recognising of an other source line is need
to complete the step command.
After single step command only one single step is done. I don't know
if for an other address is checked or single step responce is enougth
to complete the single step.
The stub recognise the single step complete if the address is changed.
In this case it is not occurs because jump to the same address.
Yes it is possible break a wait by timeout, but it is not really need.
For user is OK if it can stop execution of such loop by ctrl+c
I fixed this by responce Interrupt Signal if Ctrl+c is received.
It seems the debugger don't recognise if it sends ctrl+c and check
only for responce signal. The SIGTRAP after ctrl+c is recognised
as single step is complete but step exeqution will not be stopped.
next reply other threads:[~2005-11-04 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 9:15 Efim Monjak [this message]
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'
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 16:41 Efim Monjak
2005-11-03 21:25 ` 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=436B2677.4020802@lipowsky.de \
--to=ymonyak@lipowsky.de \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).