Mail Archives: cygwin/2008/08/04/23:13:26
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Charles Wilson wrote:
| (1) How do you debug the Xserver if your debugger depends on it?
|
| Of course, there is nobody currently trying to debug the Xserver on
| cygwin -- or develop it in any way -- so that's most likely a moot
| point. And besides, this same issue faces *nix developers: there are
| ways around it. For instance, use a stable Xserver on a different
| display, and run insight on that display to debug the unstable target
| Xserver (or a program running on that Xserver).
Or in our case, use Xming.
| (2) Red Hat's paying customers expected a standalone debugger, and would
| balk at a Xserver requirement.
|
| This is even more true now, I would imagine, as cygwin-xfree has been
| all-but-dead for years. (What? Your debugger requires an Xserver, but
| you don't provide a current one?) Hopefully some of these problems will
| soon improve, at least on the X-library, if not X-server, side --
| </raises beer vaguely in Yaakov's direction>
Keep in mind that Tk requires only libX11, so it's fairly light on the
client side.
| Also, this may impact the ability to do
| error_start=X:\somewhere\insight.exe -- but that's probably not a big
deal.
| I could certainly see splitting the distribution into two packages. This
| means that 'gdb -w' would fail in strange and wonderful ways if the
| "insight" package with all of its tcl scripts were not installed,
| but...maybe that's okay.
FWIW Debian provides gdb and insight in separate *source* packages,
neither of which depend on the other:
http://packages.debian.org/sid/gdb
http://packages.debian.org/sid/insight
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkiXxSEACgkQpiWmPGlmQSMqoACaAtwDvuBNvznL8tmxjryA9w/u
sokAn0OLyJzka3dqy3zP8MyYO8RPVY98
=zmk3
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -