[lug] Stack trace question

D. Stimits stimits at idcomm.com
Fri Aug 18 18:23:42 MDT 2000


Chan Kar Heng wrote:
> 
> y not just rip stuff out from strace source code? hehe!
> 
> >>
> >> I think I am much closer to finding my answer.  If I get the pid I can
> >> look at /proc/pid/maps which tells me which modules are loaded and where.
> >> Now I just need to get the stack from myfunction() to the top and see
> >> where each function lands in the range that I have from /proc/pid/maps.  So
> >> my question is now only how do
> >> I get the stack trace.  I need the address. I think I must write an assembly
> >> code to walk through the stack.
> >>
> 
> --------------------------------------------
> i don't suffer from stress... i'm a carrier.
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

Look for my other post. I mentioned a link to a security of stack
overflow article. Stack overflow attack and preventing it basically have
the same requirements, and the stack protection code shown may be just
what the doctor ordered for addresses.
http://www.bell-labs.com/org/11356/libsafe.html




More information about the LUG mailing list