artbek / chrome-xdebug-client

Xdebug Chrome App/Extension

Xdebug Chrome App

Features:

• stepping through code,
• setting breakpoints,
• viewing stack backtrace,
• evaluating expressions.

How to get started:

1. Install the app: Google Webstore or go to chrome://extensions/ and use 'Load unpacked extension...' button.
2. Press Listen.
3. Run your code, e.g.:

http://artbek.co.uk?XDEBUG_SESSION_START=xxx
(should work without 'xxx' value, but use it if you want 'XDEBUG_SESSION' cookie to be created)

or

> export XDEBUG_CONFIG="remote_host=0.0.0.0" ('remote_host=0.0.0.0' is optional)
> php myscript_1.php
> php myscript_2.php

or

> XDEBUG_CONFIG="" php myscript.php

chrome-xdebug-client's Issues

[Feature] Break on Error

Hello, is there anyway to make Chrome xDebug break on error when connect? Thanks

A way to disable "Break at first line" behavior

As a traitor to Eclipse, I used to have the ability to un check break at first line... is there a way to disable that and only break at breakpoints such as the ones set when I xdebug_break() ?

It's very cumbersome to break at every first line in programs that use lots of ajax calls.

Keyboard shortcuts fire after setting...

When trying to set the keyboard shortcuts, they fire when you press a button so in turn it closes the settings window, which prevents you from being able to save the settings.

Atom Shell

Hey!

Would it make sense to use this as part of Atom Shell (https://github.com/atom/atom-shell)? So that you can produce a cross-platform library.

cheers,
Derick

Can't set deep breakpoints...

On your screenshot you are debugging magento, which has a million levels... surely there is a way to debug a block controller without having to step in all the way through Index.php, Mage. autoload, etc. How is that done?

All I need is to set a breakpoint in a file that's waaay down the stack, without hunting it down from the top... thats specially difficult if you don't know the exact call stack to it.

-- Thanks for the app, it's a life saver.
Also, this packaged app works fantastically with the Xdebug helper chrome extension, that should perhaps be option #1 on the readme.md

xdebug client cant listen

I download from chrome web store, and config with my virtual machine php environment

but find listening failed

there was a tcp reset response from wireshark

192.168.0.103 is my xdebug client addr, 192.168.0.102 is my remote php linux environment addr

No support for PHP interactive shell / source-less php

XDEBUG_CONFIG="idekey=dr" php -a -d xdebug.remote_enable=1

Will run xdebug properly and trigger the "Working..." message on Chrome Xdebug Client.However, it will get stuck in that state, and running xdebug_break(); will not break the program.

It is helpful to use the php -a interactive shell to load programs, run tests and debug. It would be nice if I could force a stop using Xdebug to analyze the state.

I originally thought this was a bug in Xdebug it's self.
https://bugs.xdebug.org/view.php?id=1269#c3517
http://stackoverflow.com/questions/35413401/xdebug-in-a-php-a-interactive-shell/35413837#35413837

Please add some keyboard shortcuts for debugging

This is a great piece of software that you've built. Love it. One thing that it is desperately missing is the ability to do the stepping (in, out, over etc.) using the keyboard.

Key mappings with the function keys, for example, would be nice. Something conventional, like:
F8 Step Over
F7 Step Into
F9 Step Out

What do you say?

PsySH support would be awesome

Currently I can run sites on the php server using php -S localhost:8000 -t /var/www If I do that and then run

require '/home/amama/.composer/vendor/bin/psysh';
eval(\Psy\Sh());

I get a world class repl with gorgeous views of classes on the terminal. It would be nice to have it built in. As it stands, terminal support is quite cumbersome.

http://psysh.org/#usage

Perhaps a pipe dream? Perhaps this would be better implemented as custom Snippets?

Only port 9000 is allowed in manifest

In manifest.json is the following snippet:

"tcpServer": {
  "listen": "*:9000"
}

which means that if you try to configure the extension to use a custom port (i.e. other than 9000), you get the following error:

Unchecked runtime.lastError while running sockets.tcpServer.listen: Does not have permission
    at Object.callback (chrome-extension://nhodjblplijafdpjjfhhanfmchplpfgl/js/socket.js:108:29)

This makes the extension useless for me, since port 9000 is blocked by another app.

what's the `Profile` and `Trace` doing

Hi there,

There're four options for the extension, but I'm not sure what the Profile and Trace options does.

Does it log something in xdebug.remote_log or else ?

don't show source files

it shows like below:
Couldn't get source:
file:///srv/mlearning-lab.com/www/bootstrap/autoload.php:3

my settings like this:
Listening IP:
10.8.0.8
(xdebug will try to establish connection with this IP)

Listening Port:
9001
(this should match xdebug.remote_port in your php.ini)

Number of source code lines that will be fetched - before and after current line.
Used only if no 'Source URL' was specified.
Number of lines:
50

If the native xdebug source doesn't work as expected try using your own api, e.g. source.php
Source URL:
/Users/yangchunyong/mlearning-lab.com/public/index.php

my xdebug log:show it's connect with the app,but some errors:
->

"""please help me!!!

Set breakpoints in arbitrary files?

Instead of putting xdebug_break(); in our code, is it possible in the client to set where we want a break to occur if we know the file name and line?

Remember breakpoints

When you are seeing the source code you can put a breakpoint but as soon as you reload the page breakpoints disappeared.

I don't know how difficult is to implement this but it will be a very nice feature.

Maybe you can remember the breakpoints and reset them when a file is reloaded. Although the line number don't match, it will be near and is better than stepping over again until is found.

Missing features

I just took this to a spin, on a hurry. There was a big fat bug in my CLI component and i just couldn't figure out where. So, I took this for a spin.

Turns out that it is really great, actually! I really like to use shortcuts, and the ones provided can even be changed. So that is pretty nice.

But I totally missed variable inspection. Like I kept trying to copypaste the variables from the source into the tiny box at the bottom. Clicking on a variable should reveal it's value - that would feel way more natural. Or, like, just something like that. But copypaste is broken on OS X in Chrome Apps, if the shortcut is not provided. So I was stuck copytyping.

Kind regards, Ingwie