View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000775 | Xdebug | Uncategorized | public | 2012-02-03 22:24 | 2012-04-24 16:31 |
| Reporter | otto | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| OS | OSX | OS Version | 10.6.8 | ||
| Product Version | 2.2dev | ||||
| Target Version | 2.2.0 | Fixed in Version | 2.2.0RC2 | ||
| Summary | 0000775: eaa74b501c75dcd9c9912d5ef407625b782fcd26 broke resume | ||||
| Description | I have been using xdebug 2.1.2 to debug my drupal 7 installation with intellij idea. When I upgraded to 2.1.3 the "resume program execution" (ie I want to continue after a breakpoint has been hit) feature stopped working. | ||||
| Steps To Reproduce | Unfortunately I cannot reproduct this with a simple script. But it happens every time in my drupal project. | ||||
| Additional Information | I git bisected and it seem to be eaa74b501c75dcd9c9912d5ef407625b782fcd26 that broke this. Logfile for a working 2.1.2 session: http://pastebin.com/5HDpc4uv | ||||
| Tags | No tags attached. | ||||
| Operating System | OSX | ||||
| PHP Version | 5.3.8 | ||||
|
|
Hi, I think I've already fixed this in https://github.com/derickr/xdebug/commit/52eb81b20eca0655da7ec01a830ce591a8f5d0cd Could you please try Xdebug from github's xdebug_2_1 branch (or master)? cheers, |
|
|
Nope, seems to be the same problem. Log: http://pastebin.com/bztTq5te |
|
|
Could you either make a backtrace (https://bugs.php.net/bugs-generating-backtrace.php) or give me access to the machine so I can try this in case you can't duplicate this in a small script? |
|
|
Hi, sorry for the delay. I tried to get a backtrace but when I ran httpd under gdb I only got this after I tried to resume after the breakpoint:Program exited with code 0377.
|
|
|
I'm GMT. Send me a mail at derick xdebug org and we can schedule something for Monday. |
|
|
Just for reference: I've tried with macgdbp and can not reproduce the error there. So it must be something in the way intellij is setting up the debug session. Edit: log from macgdbp session: http://pastebin.com/tr69NtBQ |
|
|
Still the same with 2.2.0rc1 |
|
|
The log output for 2.1.4dev doesn't seem to show any problems, just like the one for 2.1.2. The one in 2.1.3 shows a bailout and/or segfault though. 2.1.2: http://pastebin.com/5HDpc4uv |
|
|
Testing now witch 2.2.0rc2 (and also new version of intellij) and it seems like everything is working again. Fantastic! |
|
|
Woo, awesome :-) |