为什么gdb不能附加到用inetd调用的服务器应用程序？ [英] Why can't gdb attach to server application summoned with inetd?

问题描述

我有一个可以使用inetd为客户端调用的服务器应用程序。但是，如果我尝试附加到使用inetd启动的服务器进程，我得到以下响应：ptrace：不允许操作。

I have a server application that can be summoned for the client using inetd. However, if I try to attach to the server process that was launched with inetd, I get the following response: ptrace: Operation not permitted.

gdb --annotate=3 /my/app/here <processId>

Current directory is /usr/local/bin/
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
Reading symbols from /usr/local/bin/flumed...done.
Using host libthread_db library "/lib/tls/libthread_db.so.1".
Attaching to program: /my/app/here, process <processId>
ptrace: Operation not permitted.
/usr/local/bin/<processId>: No such file or directory.
(gdb)

推荐答案

显然， funky with inetd where userid不是root。你最终得到一个具有奇怪权限的进程。例如，即使权限为777，您也无法读取/ proc / self / exe。我怀疑这个问题更相同。即使我是进程的userid，我没有权限。使用root用于gdb是一个工作。

Apparently, things get funky with inetd where the userid is not root. You end up with a process with weird permissions. For example, you are unable to read /proc/self/exe even though the permissions are 777. I suspect this issue is more of the same. Even though I'm the userid of the process, I don't have permissions. Using root for gdb is a work around.

这篇关于为什么gdb不能附加到用inetd调用的服务器应用程序？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！