Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PTRACE_GETSIGINFO failed #660

Open
certxbmc opened this Issue Jun 25, 2018 · 9 comments

Comments

Projects
None yet
3 participants
@certxbmc
Copy link

certxbmc commented Jun 25, 2018

I updated from 0.9.xxx to 1.0.0

open file, running application -> edb error "unable to get signal info for thread xxx : PTRACE_GETSIGINFO failed"

i tried to set "kernel.yama.ptrace_scope = 0" /etc/sysctl.d/10-ptrace.conf but it doesn't help.

@eteran

This comment has been minimized.

Copy link
Owner

eteran commented Jun 26, 2018

Can you please provide information about your distribution? Also, I assume 0.9.xx worked? Which is a bit odd since 1.0.0 didn't make any large changes since the last 0.9.x release to the debugging core code.

@certxbmc

This comment has been minimized.

Copy link
Author

certxbmc commented Jun 26, 2018

Ubuntu 18.04 LTS, edb 0.9.21-3 is in this distibution, i deleted the edb config file after updating because plugins didn't load, edb 0.9.21-3 sometimes stopped working when i used the "step over" function.

@10110111

This comment has been minimized.

Copy link
Contributor

10110111 commented Jun 26, 2018

Latest git works for me on Ubuntu 18.04 x86_64.

@certxbmc

This comment has been minimized.

Copy link
Author

certxbmc commented Jun 26, 2018

I compiled edb yesterday from git. Fresh Ubuntu 18.04 LTS installation with updates. When i use the "attach" function edb 1.0.0 works fine but i want to pause at application start.

@10110111

This comment has been minimized.

Copy link
Contributor

10110111 commented Jun 26, 2018

Please provide detailed step-by-step instructions on how to reproduce your exact problem, including how you built EDB, which application you launch/attach to, what errors/misbehavior you get as a result. Otherwise we'll be unable to help you.

@certxbmc

This comment has been minimized.

Copy link
Author

certxbmc commented Jun 29, 2018

I tried Ubuntu 16.04 and there's the same problem. Fresh install and compiling 1.0.0. I have to correct me and the problem is in 0.9.21 too. I think the application i 'm trying to debug is starting a thread and gdb can't follow.

@certxbmc

This comment has been minimized.

Copy link
Author

certxbmc commented Jun 30, 2018

EDB stops debugging at this location "call qword [rel 0x6xxxxx]" and it points to __libc_start_main.

@eteran

This comment has been minimized.

Copy link
Owner

eteran commented Jul 1, 2018

@certxbmc is the issue debugging a specific binary, or do you encounter this with any other binaries?

If we are to work on this, we'll need to reproduce it locally, so as much information (the program, steps to reproduce, etc...) would be very helpful.

Thanks

@certxbmc

This comment has been minimized.

Copy link
Author

certxbmc commented Jul 1, 2018

Maybe the problem is similar to this issue:

#571

I will check other binaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.