Re: Debugging a PHP Extension via GDB
| From: | Sebastian Kurfürst | Date: | Thu, 01 Jan 1970 00:00:00 +0000 |
| Subject: | Re: Debugging a PHP Extension via GDB | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48059@lists.php.net to get a copy of this message | ||
Hi Mathieu,
I've figured out that it always worked with GDB when specifying the file
name like Derick suggested (break objectmonitor.c and saying "yes" at
the question) -- that was a problem on my side when calling the script.
However, in Eclipse, it still did not work nicely, i.e. the breakpoints
I have set are not taken. However, when adding the code from you:
> __asm__("int3");
it nicely breaks inside eclipse as well.
So, it's not the 100% solution yet (as you can't just click the line
number in eclipse), but it's pretty close, as one can add the above
statement, and then have all debugging controls available in eclipse.
So, if anybody uses eclipse and has a functioning configuration, that'd
still be interesting, but if not, thanks everybody for your quick help!
Thanks a bunch and greets,
Sebastian