search

lncg / edb-debugger

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

detach is not a real detach #111

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
After detaching the disassembly/things of the debugged program are not shown 
anymore, but it still is not possible to attach to it with gdb, unless edb is 
closed (or perhaps attached to some other program).

Original issue reported on code.google.com by evan.teran on 3 Oct 2012 at 3:22

GoogleCodeExporter commented 9 years ago 
I am unable to reproduce this behavior. Here is what I tested:

I opened a random program (in this case thunderbird).

I attached with edb
I detached with edb
I ran gdb
I attached with gdb

No issues were encountered. Can you possibly provide I a simple set of steps to 
reproduce this?

Thank you for the report, I hope to get this resolved for you ASAP.

Original comment by evan.teran on 3 Oct 2012 at 5:27

GoogleCodeExporter commented 9 years ago 
I was a little bit wrong, it has nothing to do with gdb, it just doesn't detach.

1. Attach to program
2. Run program
3. Detach (without pausing)
4. Nothing can attach anymore (not even the current edb instance)

Original comment by evan.teran on 3 Oct 2012 at 5:27

GoogleCodeExporter commented 9 years ago 
Ah, ok now I've been able to reproduce it. It must not be properly detaching 
when the target isn't stopped yet. I'll look into a fix.

Thanks!

Original comment by evan.teran on 3 Oct 2012 at 5:27

GoogleCodeExporter commented 9 years ago 
I've applied a patch to the SVN (svn checkout 
http://edb-debugger.googlecode.com/svn/trunk/ edb-debugger-read-only).

Basically, I just added code to stop the running threads before attempting the 
detach, and it appears to work. Please let me know if it proves to not work or 
has undesired side effects.

Closing for now. Re-Open as needed.

Original comment by evan.teran on 3 Oct 2012 at 5:27