View Issue Details

Jump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0000777XdebugUncategorizedpublic2012-02-13 15:382012-04-23 18:03
ReporterJim Bacon Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformXAMPP 1.7.7OSWindowsOS VersionXP SP3
Fixed in Version2.1.4 
Summary0000777: Connection to NetBeans Reset on stepping over call to mysqli_init
Description

Using XDebug 2.1.1 supplied with XAMPP and Netbeans 7.1 I have no problem.

I upgraded to XDebug 2.1.3-5.3-vc9 and could no longer debug my scripts because the connection to NetBeans would reset after hitting a breakpoint.

I found that the connection would always break after a call to mysqli_init().

Steps To Reproduce
  1. Create the script below.

<?php
if (!function_exists('mysqli_init') && !extension_loaded('mysqli')) {
echo('MySQLi extension for PHP is not installed. ');
} else {
$connection = mysqli_init();
var_dump($connection);
}
?>

  1. Set a break point on call to mysqli_init()
  2. Run debug.
  3. On break, F8 to step to the next line.
  4. The connection is reset and debug session aborted.
Additional Information

Upgraded from PHP 5.3.8 to 5.3.10 problem remained.
Downgraded to XDebug 2.1.1 to continue working.

TagsNo tags attached.
Operating SystemWindows XP SP3
PHP Version5.3.8

Activities

derick

2012-02-13 15:43

administrator   ~0001913

Hi Jim,

could you add a remote debugging log as described at http://xdebug.org/docs/all_settings#remote_log ?

cheers,
Derick

Jim Bacon

2012-02-13 15:57

reporter   ~0001914

Hi, Log added. Jim.

derick

2012-02-13 22:51

administrator   ~0001915

Hi!

This crashes for me even when Xdebug is not loaded. I've file a bug report with PHP: https://bugs.php.net/bug.php?id=61079

cheers,
Derick

Jim Bacon

2012-02-14 14:23

reporter   ~0001916

I think perhaps there are two issues then. The call to mysqli_init does not cause a problem with the released versions of PHP as far as I know.

I can run my scripts containing this function call.
I can run and debug them with XDebug 2.1.1.
I have just tried XDebug 2.1.2 and that also works for me.
I can run and debug scripts with XDebug 2.1.3 that do not contain that function call.

When I try to reproduce your bug report to PHP the -n option results in the function not being found as the mysqli module is not loaded.

Thanks for your great work, by the way, Jim.

derick

2012-02-19 10:33

administrator   ~0001921

I think I managed to do a fix for this. Could you try the latest version from github?

Jim Bacon

2012-02-21 09:36

reporter   ~0001922

If you can point me at a compiled version (5.3-vc9) I would gladly try it but I am not in a position to compile it from source myself.

derick

2012-02-22 21:40

administrator   ~0001923

I've just put some up at : http://xdebug.org/files/xdebug-latest.tgz

Jim Bacon

2012-02-23 10:02

reporter   ~0001926

Great. Tried 2.1dev-5.3-vc9 and 2.2dev-5.3-vc9 with PHP 5.3.8. Both appear to fail in the same way as the release, 2.1.3-5.3.vc9.

Attached another remote log from tests with 2.1dev.

Additional information. On stepping over the call to mysqli_init an "Unhandled exception occurred in httpd.exe" message is received with an option to debug. Screenshot from debugger attached.

codewaggle

2012-02-28 08:39

reporter   ~0001928

Hi,

I'm experiencing the same problem with xdebug version 2.1.3 on a LAMP with php5.3
I'm using netbeans 7.1 on a Win XP box to do remote debugging

mysqli_init causes a Segmentation fault when I step past it. If I run the code with no breakpoints, I don't see the Segmentation fault, but I still get the server reset error.

I have another LAMP server with php5.2.10 and xdebug 2.1.0. The exact same code runs without problems.

I've uploaded a file that has snippets from my apache error log and my xdebug log: xdebug_logs_mysqli_init_20120228.txt

Let me know if I can provide additional info that would be helpful.

Be Well,
Joe

derick

2012-02-29 13:09

administrator   ~0001930

It's still crashing on the PHP bug: https://bugs.php.net/bug.php?id=61003

That's not something I can fix in Xdebug, so I'm closing this issue. Please add comments to the PHP bug to show you are having the same issue.

Jim Bacon

2012-02-29 14:28

reporter   ~0001941

I just wanted to add a final note, then, to say that, from a user's perspective, the resolution to this problem is to use xdebug 2.1.2 until such time as the bug in PHP is fixed (or some change that must have been made in version 2.1.3, is reverted). I guess this also means that, even if PHP is fixed, xdebug 2.1.3 will never play nicely with the older versions of PHP. I am continuing very happily in this manner.
Thanks for your time and effort,
Jim.

derick

2012-03-12 16:36

administrator   ~0001972

Thanks! And closing this issue.

derick

2012-04-23 18:03

administrator   ~0002085

Seems like this is fixed in PHP as well now.