From: "debashis mahata" <debashis.mahata@wipro.com>
To: "gdb" <gdb@sourceware.cygnus.com>
Subject: need of SOFTWARE_SINGLE_STEP
Date: Mon, 18 Jun 2001 06:16:00 -0000 [thread overview]
Message-ID: <001e01c0f7f8$b6406f00$5dcda8c0@8420044-mahatad.wipro.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hi,
I am
just a new comer in GDB internals. I have a doubt regarding the necessity of
SOFTWARE_SINGLE_STEP in the function resume() (file: infrun.c). My working
platform is Sparc- Solaris 5.8 and going through the code of GDB 4.18. The
question is :
Â
The
file procfs.c have the support for single step using the PRSTEP flag (function:
proc_run_process() ). Then, is there any specific reason behind doing
SOFTWARE_SINGLE_STEP rather than using the proc system support? Will there be
any hidden side effect if I disabled SOFTWARE_SINGLE_STEP_P and use PRSTEP for
single stepping?
Â
Looking forward to an early response.Â
Thanks
in advance.
mahata.
next reply other threads:[~2001-06-18 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 6:16 debashis mahata [this message]
2001-06-18 7:39 ` Daniel Berlin
2001-06-18 8:54 ` J.T. Conklin
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='001e01c0f7f8$b6406f00$5dcda8c0@8420044-mahatad.wipro.com' \
--to=debashis.mahata@wipro.com \
--cc=gdb@sourceware.cygnus.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