Skip to contentSkip to conversation

The purpose of PT_TRACESYSGOOD

DISCUSSION Alex LIU 3 participants 5 messages Jan 10, 2005 – Jan 11, 2005

lore
Share & tools
lore

Alex LIU

author
#0 lore raw

Hi:

What's the effect of PT_TRACESYSGOOD flag? I found it's used only set in ptrace_setoptions,which is called in the function ptrace_request. And the PT_TRACESYSGOOD flag will be requested in do_syscall_trace. What's the purpose of that flag? Thanks!

Alex

#1 lore raw

Hi!

Quoted 2 lines

What's the effect of PT_TRACESYSGOOD flag? I found it's used only set in ptrace_setoptions,which is called in the function ptrace_request. And the PT_TRACESYSGOOD flag will be requested in do_syscall_trace. What's the purpose of that flag? Thanks!

Search archives, it was needed for subterfugue.
Pavel

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
#2 lore raw
Quoted 5 lines
Quoted 5 lines

What's the effect of PT_TRACESYSGOOD flag? I found it's used only set in ptrace_setoptions, which is called in the function ptrace_request. And the PT_TRACESYSGOOD flag will be requested in do_syscall_trace. What's the purpose of that flag?

/*
* A child stopped at a syscall has status as if it received SIGTRAP.
* In order to distinguish between SIGTRAP and syscall, some kernel
* versions have the PTRACE_O_TRACESYSGOOD option, that sets an extra
* bit 0x80 in the syscall case.
*/

author
#3 lore raw

Then I think the tracing thread should call the ptrace_request to set PTRACE_O_TRACESYSGOOD flag of the traced thread first before ptrace(PTRACE_SYSCALL...) ,right?
Thanks a lot!

Alex

Quoted 11 lines · Andries Brouwer
Quoted 4 lines

What's the effect of PT_TRACESYSGOOD flag? I found it's used only set in ptrace_setoptions, which is called in the function ptrace_request. And the PT_TRACESYSGOOD flag will be requested in do_syscall_trace. What's the purpose of that flag?

/*
* A child stopped at a syscall has status as if it received SIGTRAP.
* In order to distinguish between SIGTRAP and syscall, some kernel
* versions have the PTRACE_O_TRACESYSGOOD option, that sets an extra
* bit 0x80 in the syscall case.
*/

#4 lore raw
Quoted 10 lines
Quoted 6 lines

/*
* A child stopped at a syscall has status as if it received SIGTRAP.
* In order to distinguish between SIGTRAP and syscall, some kernel
* versions have the PTRACE_O_TRACESYSGOOD option, that sets an extra
* bit 0x80 in the syscall case.
*/

Then I think the tracing thread should call the ptrace_request to set PTRACE_O_TRACESYSGOOD flag of the traced thread first before ptrace(PTRACE_SYSCALL...) ,right?

Yes.

Quoted 1 line

From a baby ptrace demo:

#define SIGSYSTRAP (SIGTRAP | sysgood_bit)

int sysgood_bit = 0;

void set_sysgood(pid_t p) {

#ifdef PTRACE_O_TRACESYSGOOD
        int i = ptrace(PTRACE_SETOPTIONS, p, 0, (void*) PTRACE_O_TRACESYSGOOD);
        if (i == 0)
                sysgood_bit = 0x80;
        else
                perror("PTRACE_O_TRACESYSGOOD");

#endif
}

and now the signal SIGSYSTRAP signifies a system call when the sysgood bit was implemented, anything different from SIGSYSTRAP is guaranteed to be a signal.