Forum rules: Forum rule Nº 15 is strictly enforced in this subforum.
#233166 by hgoel0974
Tue Jan 29, 2013 1:59 am
I am looking at some exploit and in the debugger, I see lots of deadbeef, is that like null for the registers?
#233175 by DS_Marine
Tue Jan 29, 2013 2:16 am
hehe I made the same question few days after registering here.
I found a nice read here
or was it this?

anyway, the hijacked thread was this :p
FrEdDy wrote:When returning from a syscall, the syscall handler stores 0xDEADBEEF in all argument and temp registers to avoid data leaks.
#233180 by hgoel0974
Tue Jan 29, 2013 2:39 am
Thanks! I am new to all these things.
#234010 by noname120
Thu Jan 31, 2013 11:21 am
When there is a return from a syscall, 0xDEADBEEF are placed all over to avoid data leak.
#240624 by poettlr
Fri Feb 22, 2013 10:49 am
Some memory managers write deadbeef arround memobjects to know if there is a leak.

at least i do that.. I'd say its actully pretty normal for a c++ dev

Who is online

Users browsing this forum: Yahoo [Bot] and 0 guests