From: bzs@theworld.com
To: Jim Hyslop <jhyslop@dreampossible.ca>
Cc: cygwin@cygwin.com
Subject: Re: Debugging PHP with GDB and php-debuginfo
Date: Wed, 21 Jul 2021 01:26:44 -0400 [thread overview]
Message-ID: <24823.45076.15657.755748@gargle.gargle.HOWL> (raw)
In-Reply-To: <6761b93277958c240961339bc5a1f2e2@dreampossible.ca>
As much as I love GDB dearly and rely on it regularly you might want
to have a look at netbeans.apache.org which is also free and a more
general fancy UI IDE. If it's a web site you're developing for example
it will let you fire up a browser, put breakpoints in the php code,
and examine variables etc.
It's a little more complicated to set up than just using GDB but not
too bad (hint: install the Chrome browser ZDebug/XDebug/whateveritis
extension they recommend, and/or Firefox, or netbeans has a built-in
browser tho you probably want to know how your code works with chrome
and/or ff not their browser other than initial devpt.)
P.S. I generally edit my code with emacs. Netbeans notices a file has
changed and reloads -- it's magic (aka inotify(7)) tho use one (IDE
editing) or the other (emacs/vi/joe/jove/pico/externaleditor.)
The latest releases of netbeans (12.x) have gotten very good but once
in a while you just have to exit and restart it ("a communication
failure has occurred...") but no big deal just restart it, it
remembers your breakpoints etc., just to save you five minutes of
WTF?!
--
-Barry Shein
Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com
Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD
The World: Since 1989 | A Public Information Utility | *oo*
next prev parent reply other threads:[~2021-07-21 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 22:54 Jim Hyslop
2021-07-21 1:24 ` Russell VT
2021-07-21 5:26 ` bzs [this message]
2021-07-21 8:06 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24823.45076.15657.755748@gargle.gargle.HOWL \
--to=bzs@theworld.com \
--cc=cygwin@cygwin.com \
--cc=jhyslop@dreampossible.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).