Some break points not actually stopping

I'm using a linux dev system properly configured. Debugging PHP with xdebug works... except in some files.

- if I set up a breakpoint in a function of the "weird" file, the IDE changes like the breakpoint is hit, but doesn't actually stop (just scrolls to the breakpoint line)
- if I set up a breakpoint in the caller of this function, I can step normally until I step in the "weird"' function

It behaves like any break inside this file is immediatly followed by a "resume".

All files are under the same root folder.

I'm puzzled, what am I missing???

TIA

greg

PS 133-168 JRE 1.7.0_45 Ubuntu 12.10 xdebug 2.2.1

7 comments
Comment actions Permalink

Note: if I select "Log message to console" in the breakpoint dialog, a line is displayed in the debug console.

0
Comment actions Permalink

Note2: I put these lines in the caller after the call:

        error_log('passed');
        xdebug_break();

The word "passed" appears in Apache's log file and the code runs over the break instruction without breaking into PHPStorm...

0
Comment actions Permalink

Hi there,

The word "passed" appears in Apache's log file and the code runs over the break instruction without breaking into PHPStorm...


This most likely means that file is not properly mapped (if code is executed on another machine/virtual) or symbolic link is used (mapping to real file is required, as xdebug only works with resolved/final file names) .. or file is outside of the project (which is unlikely, based on your description).

Collect detailed logs and look into it:

0
Comment actions Permalink

Thanks for your answer. It's a regular file no different mapping from the working files.

However when I look at the files you point at, I can see a lot of errors, such as:

idea.log:

WARN - php.debug.xdebug.dbgp.DbgpUtil - Could not parse packet
DEBUG - .connection.PhpDebugConnection - 577398170#---Invalid packet

It seems to be a problem of communication between xdebug and PHPStorm. Should I open a ticket and upload the logs files there?

0
Comment actions Permalink

Better upgrade xdebug to latest stable version first, which is 2.2.3.

If nothing will change -- then yes -- submit a ticket to the Issue Tracker

0
Comment actions Permalink

I manually compiled xdebug 2.2.3, same result, so I filed a report:

http://youtrack.jetbrains.com/issue/WI-21344

greg

0

Please sign in to leave a comment.