Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: "debashis mahata" <debashis.mahata@wipro.com>
Cc: "gdb" <gdb@sourceware.cygnus.com>
Subject: Re: need of SOFTWARE_SINGLE_STEP
Date: Mon, 18 Jun 2001 07:39:00 -0000	[thread overview]
Message-ID: <87g0cxetss.fsf@cgsoftware.com> (raw)
In-Reply-To: <001e01c0f7f8$b6406f00$5dcda8c0@8420044-mahatad.wipro.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

"debashis  mahata" <debashis.mahata@wipro.com> writes:

> 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?
The fact that many host OSes of GDB have no procfs support?
>  Will
> there be any hidden side effect if I disabled SOFTWARE_SINGLE_STEP_P and use
> PRSTEP for single stepping?
Yes, you'll break GDB on a lot of platforms.
:)

> 
>  
> 
> Looking forward to an early response. 
> 
> Thanks in advance.
> 
> mahata.

-- 
"There was a power outage at a department store yesterday.
Twenty people were trapped on the escalators.
"-Steven Wright


  reply	other threads:[~2001-06-18  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-18  6:16 debashis  mahata
2001-06-18  7:39 ` Daniel Berlin [this message]
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=87g0cxetss.fsf@cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=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