--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Re. http://mail-index.NetBSD.org/netbsd-help/2004/02/10/0002.html

Yes, it is possible to debug a shared library at the source level.
I've traced the GLUT library that way (which, unless I completely
misunderstood, was provided as, and used as, a shared library).
(I won't say that I debugged GLUT.  I was seeing a very bizarre
behavior, that only got more bizarre when I watched the variables
change "live".  I eventually gave up on it, since I had caught
wind of a GLUT-replacement library (freeglut), which turns out
to not have that particular bug, and is actively maintained.)

I can't remember if I had to do anything special to make GLUT
traceable, or if it built that way by default from pkgsrc.
I do clearly remember tracing it into its event loop and watching
it grab X events...


--=20
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/

--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAKWRET0R9S8K3/JQRAnWqAJ9KZLJFBGW2j6kumFXMHxtWjGDRWgCeLTOr
xczr8a661MqOomuP6LiHuCo=
=6Geq
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--