Well, I made some tests with a Linux server where I have:
* the same Xdebug version compiled (2.0.0beta5)
* the same Apache 2.0.55 (running PHP as a module)
* the same PHP 5.1.2
* I configured and used the same pre-compiled Windows Debug
Client 0.7.3 (DBG) as earlier.
Both cases:
break test.php:15
and
break /usr/local/apache2/htdocs/test.php:15
works ok, so there is nothing wrong with the Linux version. But this
doesn't help me if I want to use the Weaverslave editor in Windows as
it supports only Windows notation when setting the breakpoints to files
:(
And as I don't have the environment to compile the Xdebug in Windows
I can't debug this problem.
-Pasi
> > > ---------------------------------
> > > xdebug.remote_handler=gdb
> > > ---------------------------------
> >
> > I don't quite develop more on that protocol, please use the dbgp
> > one if you can.
> Ok, when using the dbgp the file & line number combination works.
> The reason why I wanted to use the old protocol is that it's used
> by the Weaverslave editor.
>
> > > The Debug Client states: "1 Breakpoint set on file:line
> combination."
> > > and I can list it with show-breakpoints. But when I type:
> 'run' it
> > > just don't break at the wanted line.
> >
> > How exactly are you setting your break point? What is the full
> command
> > that you used?
> I tried with the older pre-compiled Windows Debug client 0.7.3 (GDB
):
> (init C:\tmp\test.php) break C|/tmp/test.php:15
> and
> (init C:\tmp\test.php) break test.php:15
> and
> (init C:\tmp\test.php) break C|\tmp\test.php:15
> ...all stated that the breakpoint is set but none of them really
> breaked.And I also tried with the Weaverslave 4 beta 3.9.18 that
> uses the first notation (break C|/tmp/test.php:15)
>
> BR,
> Pasi
>
>
Received on Mon Feb 06 2006 - 19:34:04 GMT
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST