* PTRACE_SYSCALL on Intel Linux
@ 2002-08-22 7:13 Datoda
2002-08-22 7:19 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Datoda @ 2002-08-22 7:13 UTC (permalink / raw)
To: gdb
Hi,
This ptrace request sigtraps at the entry and at
the exit of a system call. It is not clear to me how
to tell whether it's at the entry or at the exit. Does
anyone have an idea? Thanks.
__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: PTRACE_SYSCALL on Intel Linux
2002-08-22 7:13 PTRACE_SYSCALL on Intel Linux Datoda
@ 2002-08-22 7:19 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2002-08-22 7:19 UTC (permalink / raw)
To: Datoda; +Cc: gdb
On Thu, Aug 22, 2002 at 07:13:32AM -0700, Datoda wrote:
> Hi,
>
> This ptrace request sigtraps at the entry and at
> the exit of a system call. It is not clear to me how
> to tell whether it's at the entry or at the exit. Does
> anyone have an idea? Thanks.
There is no way to tell.
If you use the TRACESYSGOOD option, you can at least distinguish it
from normal breakpoints. Then you count how many you've had. I have
some additional kernel patches to make TRACESYSGOOD work on all
architectures, but it should already work on Intel.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-08-22 14:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-08-22 7:13 PTRACE_SYSCALL on Intel Linux Datoda
2002-08-22 7:19 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox