Date: Tue, 27 Sep 2005 18:48:45 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Phil Cryer <phil@cryer.us> Cc: ports@FreeBSD.org, ale@FreeBSD.org, kris@obsecurity.org Subject: Re: Re: How to deal with a port that uses /proc in FreeBSD 6.0? Message-ID: <20050927224845.GB46689@xor.obsecurity.org> In-Reply-To: <1127853836.8699c9cphil@cryer.us> References: <1127853836.8699c9cphil@cryer.us>
next in thread | previous in thread | raw e-mail | index | archive | help
--KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 27, 2005 at 03:43:56PM -0500, Phil Cryer wrote: > anytime I need to debug some code, and that works, I was just > wondering if there was any sort of better/long term solution. A > current open source project I'm working is written in C, and there's > plenty to debug since they devel on Linux only, so I have to run gdb > and the like rather often. Just wondering if this is the best way > to deal with this or if there's some "official" way that I don't > know about. The better solution is to fix the code to use other C interfaces to obtain the same information exported by procfs. Kris --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDOcxNWry0BWjoQKURAgsaAJ45xlZJaEV+oNnzQ6DnVlUboja5zQCeLePc oPTG7Vd2uWzDMrIRAd+sOYU= =HCIy -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050927224845.GB46689>