wuhailinjerry / edb-debugger

Automatically exported from code.google.com/p/edb-debugger
GNU General Public License v2.0
0 stars 0 forks source link

make error: unix/linux/DebuggerCore.cpp:86: error: 'PTRACE_EVENT_CLONE' was not declared in this scope #121

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. make
2.
3.

What is the expected output? What do you see instead?
unix/linux/DebuggerCore.cpp:86: error: 'PTRACE_EVENT_CLONE' was not declared in 
this scope

What version of the product are you using? On what operating system?
product: edb-debugger 0.9.17 and 0.9.18
OS: RHEL5

Please provide any additional information below.

qt: 4.8.4
boost: 1.51

Original issue reported on code.google.com by bridg...@gmail.com on 8 May 2013 at 4:39

Attachments:

GoogleCodeExporter commented 9 years ago
I think the issue is that the kernel you are compiling against is too old. I am 
not sure what version PTRACE_EVENT_CLONE was introduced, but it is necessary 
for debugging threads :-(.

Original comment by evan.teran on 2 Jun 2013 at 5:05

GoogleCodeExporter commented 9 years ago
Please try the latest SVN version, I believe I made it possible to compile the 
code without kernel support for PTRACE_EVENT_CLONE.

Original comment by evan.teran on 3 Jun 2013 at 2:33

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Thanks, Evan, the issue has been solved with the latest SVN version.

Seems there is another issue with this svn version. 

When exit edb, suppose the terminal of "edb output" should be closed 
automatically at the same time, but with this version, the "edb output" termail 
won't close when exit edb, and the debugging program will go on running in the 
"edb output" window.

Original comment by bridg...@gmail.com on 6 Jun 2013 at 2:00

GoogleCodeExporter commented 9 years ago
It should close when edb exits cleanly. Is there any messages on the output of 
edb which seem noteworthy? Also which terminal is being launched? I've 
experienced difficulties in the past with terminals besides xterm.

Original comment by evan.teran on 6 Jun 2013 at 1:33

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
> Is there any messages on the output of edb which seem noteworthy?
The edb output show message of the running process, just like that run at 
terminal directly.
I'm sorry it's not convenient to past the output message of this case here. 
I'll try to find another case and share the output message if needed.

> Also which terminal is being launched?
I try terminals on both Linux and Solaris.
Linux: shell - Konsole
Solaris: Terminal

Original comment by bridg...@gmail.com on 7 Jun 2013 at 7:43

GoogleCodeExporter commented 9 years ago
The primary issue being discussed has long been fixed

Original comment by evan.teran on 8 Jan 2014 at 3:49