|
|
|
|
|
|
|
|
|
|
xen-devel
No, Xen poisons stack frames with 0xdeadbeef in debug builds to try to
detect use-after-clobbered bugs. It's only actually a bug if it causes
something to go wrong!
-- Keir
On 2/10/08 15:46, "John McDermott (U.S. Navy Employee)"
<john.mcdermott@xxxxxxxxxxxx> wrote:
> Is it the case that we should never see 0xdeadbeef in a stack trace,
> even if everything otherwise appears OK?
>
> John
> ----
> What is the formal meaning of the one-line program
> #include "/dev/tty"
>
> J.P. McDermott building 12
> Code 5542 mcdermott@xxxxxxxxxxxxxxxx
> Naval Research Laboratory voice: +1 202.404.8301
> Washington, DC 20375, US fax: +1 202.404.7942
>
>
>
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|