[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libunwind] remote unwinding and ptrace()

From: Umut Aymakoglu
Subject: Re: [libunwind] remote unwinding and ptrace()
Date: Thu, 11 Dec 2003 15:39:59 -0800

Hi David -
You are right it is not completely libunwind issue. It is a ptrace() problem; a non-root process can not attach to a setuid/setgid process.This is mentioned in the man page of ptrace.
In this case is there an alternative to ptrace()?

Inactive hide details for David Mosberger <address@hidden>David Mosberger <address@hidden>

          David Mosberger <address@hidden>
          Sent by: address@hidden

          12/11/2003 02:50 PM
          Please respond to davidm

To: Umut Aymakoglu/Menlo Park/address@hidden
cc: address@hidden
Subject: Re: [libunwind] remote unwinding and ptrace()

Hi Umut,

>>>>> On Thu, 11 Dec 2003 13:54:15 -0800, Umut Aymakoglu <address@hidden> said:

Umut> Hi - I have the following problem: The owner of the target
Umut> process is root and the permissions are 6755 (-rwsr-sr-x). The
Umut> program that will attach and unwind the target process does
Umut> not have the root ownership and the permissions are
Umut> 2755(-rwxr-sr-x). The group ids are same on both of the
Umut> programs. The program does a ptrace(PTRACE_ATTACH) call to
Umut> attach the target process and receives EPERM error. The 2nd
Umut> program can not have the root ownership. Is there a way to
Umut> make this work?

I don't see why this is a libunwind-specific question. If process A
cannot access process B, then how could A have any hope to unwind B,
whether or not libunwind is involved. Am I missing something?

libunwind mailing list

GIF image

reply via email to

[Prev in Thread] Current Thread [Next in Thread]