* need of SOFTWARE_SINGLE_STEP
@ 2001-06-18 6:16 debashis mahata
2001-06-18 7:39 ` Daniel Berlin
2001-06-18 8:54 ` J.T. Conklin
0 siblings, 2 replies; 3+ messages in thread
From: debashis mahata @ 2001-06-18 6:16 UTC (permalink / raw)
To: gdb
[-- 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: need of SOFTWARE_SINGLE_STEP
2001-06-18 6:16 need of SOFTWARE_SINGLE_STEP debashis mahata
@ 2001-06-18 7:39 ` Daniel Berlin
2001-06-18 8:54 ` J.T. Conklin
1 sibling, 0 replies; 3+ messages in thread
From: Daniel Berlin @ 2001-06-18 7:39 UTC (permalink / raw)
To: debashis mahata; +Cc: gdb
[-- 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: need of SOFTWARE_SINGLE_STEP
2001-06-18 6:16 need of SOFTWARE_SINGLE_STEP debashis mahata
2001-06-18 7:39 ` Daniel Berlin
@ 2001-06-18 8:54 ` J.T. Conklin
1 sibling, 0 replies; 3+ messages in thread
From: J.T. Conklin @ 2001-06-18 8:54 UTC (permalink / raw)
To: debashis mahata; +Cc: gdb
>>>>> "debashis" == debashis mahata <debashis.mahata@wipro.com> writes:
debashis> I am just a new comer in GDB internals. I have a doubt
debashis> regarding the necessity of SOFTWARE_SINGLE_STEP in the
debashis> function resume() (file: infrun.c). My working platform is
debashis> Sparc- Solaris 5.8 and going through the code of GDB
debashis> 4.18. The question is :
If I recall correctly, kernel single-step support is a relatively new
feature in Solaris. If you know that you'll only run GDB on versions
that support it, you probably can get away with disabling SOFTWARE_-
SINGLE_STEP_P locally. I'm not sure what would be required to get it
into the mainline GDB. It would either have to be a new config, or
be able to determine whether or not kernel single-step is available
at run-time.
--jtc
--
J.T. Conklin
RedBack Networks
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-06-18 8:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-06-18 6:16 need of SOFTWARE_SINGLE_STEP debashis mahata
2001-06-18 7:39 ` Daniel Berlin
2001-06-18 8:54 ` J.T. Conklin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox