Subject: Re: sanity checking arguments to library functions...
To: None <firstname.lastname@example.org, email@example.com>
From: Ross Harvey <firstname.lastname@example.org>
Date: 04/16/1999 10:53:29
> To: "Brian C. Grayson" <email@example.com>
> Cc: "Chris G. Demetriou" <firstname.lastname@example.org>, email@example.com,
> Subject: Re: sanity checking arguments to library functions...
> cc: firstname.lastname@example.org
> From: Julian Assange <email@example.com>
> Date: 16 Apr 1999 23:49:58 +1000
> User-Agent: Gnus/5.070066 (Pterodactyl Gnus v0.66) XEmacs/21.0(beta67) (20 minutes to Nikko)
> "Brian C. Grayson" <firstname.lastname@example.org> writes:
> > I've implemented a stack dump in such a way that it works
> > for any gcc/egcs-compiled program, and I'm sure others have done
> > similar stuff. Interested parties can contact me off-line for
> > more details. With this functionality, an abort actually
> > provides _some_ useful info.
> > Brian
> Can we see this in the tree, brian?
If the thing works by using gcc builtins like:
Well...actually...that doesn't work on "any gcc/egcs-compiled program"
because the builtin isn't implemented on all architectures. (And, for
those that it isn't implemented for, I don't think it errors out, so
you just get a run-time exception.)