daoth / xdebugclient Goto Github PK

Open property windows should be reloaded after every run period to reflect
the current state.

The program now gives an error when you try to open a file localy or with 
a ftp network connection.

What steps will reproduce the problem?
1. start debugging
2. use inspect window
3. click "close" at bottom of window

What is the expected output? What do you see instead?
Window should be closed. ;]

What version of the product are you using? On what operating system?
XDC 1.0 b5, WXP SP2

When a file is edited on the server, one has to close the file to have it
reloaded. When doing so, breakpoint should be cleared because they are
probably in different lines now.

Port configuration + Proxy support

What steps will reproduce the problem?
1. Run XDebugClient. Start listening
1. Run a PHP5 script with xdebug 2 pointed at xdc
2. Accept the connection, "ask the debugger to retrieve the source file"
3. Program appears to do nothing, so press F5 to start debugging

What is the expected output? What do you see instead?

I expect the program to start with the first line of the program
highlighted. However, it seems to jump straight into a function much
further down the line.

What version of the product are you using? On what operating system?

1.0 beta 3 on XP SP2

Please provide any additional information below.

I don't mind providing the source code for the script that causes this,
although it seems to happen with all of the scripts I've tested it with.

Jon

It appears that you may have altered some of the following libraries
sources. Please make those available per their licenses.

The Dockpanel Suite by Weifen Luo
http://sourceforge.net/projects/dockpanelsuite/

The Advanced Treeview component by Andrey Gliznetsov
http://www.codeproject.com/cs/miscctrl/treeviewadv.asp 

Thank you for your efforts on the xdebugclient.

Automatically start debugging with a breakpoint on the first line when
Xdebug connects.

1. Create a page that throws an exception :

<?php

throw new Exception();

?>

2. Launch xdc and start listening

3. Hit the page

4. In xdc -> "Run" and you get the following exception :

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be
non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument
argument, ExceptionResource resource)
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at xdc.XDebug.Client.Run(String command)
   at xdc.MainForm.SendContinuationCommand(String command)
   at xdc.MainForm.runToolStripMenuItem_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e,
ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e,
ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripMenuItem.ProcessCmdKey(Message& m, Keys
keyData)
   at System.Windows.Forms.ToolStripManager.ProcessShortcut(Message& m,
Keys shortcut)
   at System.Windows.Forms.ToolStripManager.ProcessCmdKey(Message& m, Keys
keyData)
   at System.Windows.Forms.ContainerControl.ProcessCmdKey(Message& msg,
Keys keyData)
   at System.Windows.Forms.Form.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.ContainerControl.ProcessCmdKey(Message& msg,
Keys keyData)
   at System.Windows.Forms.Form.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.ContainerControl.ProcessCmdKey(Message& msg,
Keys keyData)
   at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.PreProcessMessage(Message& msg)
   at System.Windows.Forms.Control.PreProcessControlMessageInternal(Control
target, Message& msg)
   at
System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
xdc
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///H:/PHP/_xdebug-frontend/xdc.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e
089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy
stem.Drawing.dll
----------------------------------------
WeifenLuo.WinFormsUI.Docking
    Assembly Version: 2.0.2649.16786
    Win32 Version: 2.0.2.0
    CodeBase: file:///H:/PHP/_xdebug-frontend/WeifenLuo.WinFormsUI.Docking.DLL
----------------------------------------
ICSharpCode.TextEditor
    Assembly Version: 2.0.0.1591
    Win32 Version: 2.0.0.1591
    CodeBase: file:///H:/PHP/_xdebug-frontend/ICSharpCode.TextEditor.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50
a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System
.Xml.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.W
eb.dll
----------------------------------------

===================

My php.ini for XDebug :
xdebug.remote_enable=1
xdebug.remote_host="localhost"
xdebug.remote_port=9000
xdebug.remote_autostart=1
xdebug.remote_mode="req"
xdebug.show_exception_trace=1
xdebug.auto_trace=1
xdebug.profiler_enable=1

What steps will reproduce the problem?
1. click on links or
2. look at the version number

What is the expected output? What do you see instead?
I expect correct version number (I was really confused if I had executed 
correct version after update). Links don't work too.

What version of the product are you using? On what operating system?
XDC 1.0 b5, WXP SP2

What steps will reproduce the problem?
1. telnet remotehost 9000
2. type a then hit enter
3. quit telnet click

What is the expected output? What do you see instead?
client is not supposed to freeze

What version of the product are you using? On what operating system?
1beta3
windows 2003
i am not an admin

Please provide any additional information below.
after following the steps above the client just freezes

What steps will reproduce the problem?
1. Debug with xdebug
2. Step through code that opens multiple additional libraries.  Eventually
this error will occur.

What is the expected output? What do you see instead?
"Invalid length for a Base-64 char array" error while stepping through code.

What version of the product are you using? On what operating system?
xdc-1.0b3

Please provide any additional information below.

In many PHP frameworks and larger scripts, there is a stack trace of all 
variables used in scripts. I think that variables tree next to the code 
with them would be a great feature.

Now, it's necessary to point each variable by cursor and then use inspect. 
Using variables tree would much improve readability and user experience. ;)

I wan't to try xdebugclient but my proyect use a Virtual Machine and I need 
debug in a remote IP not in localhost, i suggest made this configurable. Thanks

MainForm.cs
Line 61 localhost -> for other IP.

What steps will reproduce the problem?
1. Set PHP server encoding to UTF-8.
2. Set a UTF-8(non-ascii) text to a variable in a PHP script.
3. Debug the script and inspect the variable.

What is the expected output? What do you see instead?
The variables are displayed like '??????'.

What version of the product are you using? On what operating system?
Apache
Windows


Please provide any additional information below.

Changing
System.Text.Decoder decoder = new System.Text.ASCIIEncoding().GetDecoder();
to
                        System.Text.Decoder decoder = new System.Text.UTF8Encoding().GetDecoder();
works fine for me.

While debugging a large application, execution stops at several places for
reasons beyond my understanding.  There are no breakpoints at these places
and as far as I am aware there are no warnings or errors being generated here.

One of the lines it breaks on is:

if( is_array( self::$channels[ $channel_name ] ) )

self::$channels is an array and $channel_name is defined and a valid index.
 There are several other places that it breaks out too.

It makes it impractical to use the client at all because I have to ht f5
dozens of times just to reach my first actual breakpoint, and must take it
slow so as not to miss it!

It should be possible to break on script start only if there are no
breakpoints in no files. This shoould be the default.

What steps will reproduce the problem?
1. point mouse over listing
2. scroll the wheel

What is the expected output? What do you see instead?
I expect to scroll code with wheel. Now it isn't possible.

What version of the product are you using? On what operating system?
XDC 1.0b5, WXP SP2

It should be possible to open files from the server by manually giving the
file path on the server.

Alternatively or additionally break on every new file to have xdc load that
file.

What steps will reproduce the problem?
1. Create a page (in my case info.php containing: <?php phpinfo(); ?>)
2. Load this in your browser -even without ?XDEBUG_SESSION_START=1 this 
works-
3. When the script is loading, stop your server
4. Then the page will return a 500 status code
5. Open XDebugClient and click on `Debug` -> `Run`
6. XDebugClient will now throw an unhandled exception `De externe host 
heeft een verbinding verbroken`

What is the expected output? What do you see instead?
Wanting to see a messagebox containing: `Connection lost`. In return I get 
an unhandled exception dialog

What version of the product are you using? On what operating system?
XDC 1.0b3 on Windows XP Home edition SP2+

Please provide any additional information below.
The unhandled exception dialog contained this:
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.Sockets.SocketException: De externe host heeft een verbinding 
verbroken
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 
size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at xdc.XDebug.Client.SendCommand(Command c)
   at xdc.XDebug.Client.Run(String command)
   at xdc.MainForm.SendContinuationCommand(String command)
   at xdc.MainForm.runToolStripMenuItem_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs 
e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, 
ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, 
ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons 
button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& 
m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, 
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: 
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
xdc
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/PHP/XDebugClient/xdc.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: 
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c56
1934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: 
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/Syste
m.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: 
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a
3a/System.Drawing.dll
----------------------------------------
WeifenLuo.WinFormsUI.Docking
    Assembly Version: 2.0.2649.16786
    Win32 Version: 2.0.2.0
    CodeBase: file:///C:/PHP/XDebugClient/WeifenLuo.WinFormsUI.Docking.DLL
----------------------------------------
ICSharpCode.TextEditor
    Assembly Version: 2.0.0.1591
    Win32 Version: 2.0.0.1591
    CodeBase: file:///C:/PHP/XDebugClient/ICSharpCode.TextEditor.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: 
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f
11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: 
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/S
ystem.Xml.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.210 (QFE.050727-2100)
    CodeBase: 
file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/Sys
tem.Web.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

This is new feature request

1. yellow tips with variable when mouse stops over a variable

2. dockable watch

There needs to be a configuration option to broadcast the IDE and IDE-KEY to 
a DBGp Proxy so that multiple users can be debugging at the same time.