View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000790Xdebugpublic2012-03-06 15:332012-03-12 16:15
Reporteralexhofbauer Assigned Toderick  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
PlatformDebian/unstableOSLinuxOS Version3.2
Product Version2.2dev 
Summary0000790: Debugging broken with PHP 5.4: Unexpected termination of script, debugging ended
Description

Xdebug doesn't work anymore since Debian/unstable migrated to PHP 5.4.

I tried the recent master branch in git, Eclipse errors with a message box saying "Unexpected termination of script, debugging ended.".

With 5.3 and a stable version of XDebug I could debug in the otherwise identical setup. Compiling Xdebug with PHP 5.4 works fine though.

Additional Information

$ ./eclipse-php -consoleLog -debug
...

!ENTRY org.eclipse.php.debug.core 4 4 2012-01-29 16:15:37.452
!MESSAGE class org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget
: DBGp Response Error: stdout:=4 msg:unimplemented command

!ENTRY org.eclipse.php.debug.core 4 4 2012-01-29 16:15:37.851
!MESSAGE class org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget
: DBGp Response Error: stderr:=4 msg:unimplemented command

!ENTRY org.eclipse.php.debug.core 4 150 2012-01-29 16:15:37.859
!MESSAGE Unexpected termination of script, debugging ended.

!ENTRY org.eclipse.php.debug.core 4 4 2012-01-29 16:15:37.863
!MESSAGE class
org.eclipse.php.internal.debug.core.xdebug.communication.XDebugCommunicationDaemon
: Unexpected Exception: Listener thread still listening
java.lang.NullPointerException
at
org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget.sendBreakpointAddCmd(DBGpTarget.java:1753)
at
org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget.breakpointAdded(DBGpTarget.java:1679)
at
org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget.loadPredefinedBreakpoints(DBGpTarget.java:1944)
at
org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget.initiateSession(DBGpTarget.java:426)
at
org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget.sessionReceived(DBGpTarget.java:276)
at
org.eclipse.php.internal.debug.core.xdebug.dbgp.model.DBGpTarget.sessionReceived(DBGpTarget.java:241)
at
org.eclipse.php.internal.debug.core.xdebug.communication.XDebugCommunicationDaemon.createLaunch(XDebugCommunicationDaemon.java:292)
at
org.eclipse.php.internal.debug.core.xdebug.communication.XDebugCommunicationDaemon.startConnectionThread(XDebugCommunicationDaemon.java:173)
at
org.eclipse.php.internal.debug.core.daemon.AbstractDebuggerCommunicationDaemon$ReceiverThread.run(AbstractDebuggerCommunicationDaemon.java:215)
at java.lang.Thread.run(Thread.java:722)

TagsNo tags attached.
Attached Files
phpinfo.txt (21,203 bytes)   
xdebug.log (2,383 bytes)
Operating SystemDebian GNU/Linux
PHP Version5.4-dev

Activities

derick

2012-03-07 19:36

administrator   ~0001950

Where did you get the Xdebug binary from in this case? Can you reproduce this by using Xdebug from github?

alexhofbauer

2012-03-08 00:57

reporter   ~0001960

The binary was compiled in the same environment it is being tested in. I am using Xdebug from github (commit 07405) here, that's what I meant by "the recent master branch in git".

PHP 5.4 and all the packages related to it are from the unstable distribution of Debian.

derick

2012-03-08 09:46

administrator   ~0001961

Okay, I need some more info:

  1. when does this issue show up? Straight away, or after some stepping over?
  2. Can you make a remote-debugging log and attach it? (See: http://xdebug.org/docs/all_settings#remote_log)
  3. Provide the code that's mentioned in the remote log
  4. What does the Apache error log say?
  5. Can you reproduce this with a command line script?
  6. If so, when it crashes, could you make a backtrace like is described at http://bugs.php.net/bugs-generating-backtrace.php ?

cheers,
Derick

alexhofbauer

2012-03-08 10:08

reporter   ~0001962

ad 1: Right after hitting the breakpoint.

ad 2: Please see the attachment above.

ad 3: It's "echo 'here';" executed in a shell by
XDEBUG_CONFIG="idekey=session_name" php index.php

ad 4: Nothing, the page executes normally (but I'm not sure what should I look for).

ad 5: Yes, that's what I did for the log provided above.

ad 6: I'll try to provide a backtrace (can't setup that right now). PHP itself is not crashing here though.

derick

2012-03-08 10:52

administrator   ~0001963

Forget about the backtrace, I think I see the problem :-)

derick

2012-03-12 16:15

administrator   ~0001967

Fixed on github.

Issue History

Date Modified Username Field Change
2012-03-06 15:33 alexhofbauer New Issue
2012-03-06 15:33 alexhofbauer File Added: phpinfo.txt
2012-03-07 19:36 derick Note Added: 0001950
2012-03-07 19:36 derick Assigned To => derick
2012-03-07 19:36 derick Status new => feedback
2012-03-08 00:57 alexhofbauer Note Added: 0001960
2012-03-08 00:57 alexhofbauer Status feedback => assigned
2012-03-08 09:46 derick Note Added: 0001961
2012-03-08 10:07 alexhofbauer File Added: xdebug.log
2012-03-08 10:08 alexhofbauer Note Added: 0001962
2012-03-08 10:52 derick Note Added: 0001963
2012-03-12 16:15 derick Note Added: 0001967
2012-03-12 16:15 derick Status assigned => closed
2012-03-12 16:15 derick Resolution open => fixed
2016-07-31 12:35 derick Category Debug client (console) => debugclient (debugging tool)
2016-07-31 12:35 derick Category debugclient (debugging tool) => (No Category)