On Wed, Jan 18, 2006 at 05:42:56PM +0100, Blaisorblade wrote:
> What about this? Inserting an asm volatile clobbering all unsaved registers
> (what I thought for long time)?
The gcc doc is somewhat confusing. I read your description as saying
that locals may be totally smashed to random numbers (and the first
sentence in the gcc description implies that as well). However, the
example they give is a pathological case where a local may have one of
two (well-defined) values, and it's not defined which of those two
well-defined values it will end up with.
> Or taking the libc implementation and suiting
> it for our use, solving the above problem?
Yuck. But how big is it?
Another possibility is to do the magic wakeup thing we do with
mconsole stack, and have it tell us what it registers are. Not sure
if that's any better.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
