[lug] Stack trace question

D. Stimits stimits at idcomm.com
Fri Aug 18 18:00:37 MDT 2000

I've found something that may be relevant to your application. It is
actually about stack overflow attacks, but what you are wanting to
determine is very closely related in technology. Check out:

It is an interesting middle ground between security, debugging, and just
interesting from the geek view.

Dan Wilson wrote:
> D. Stimits
> >references. One can disassemble almost anything, but it doesn't
> >necessarily get you anywhere in terms of useful information. So one big
> >question is whether tracing is going to be a one-way or two-way thing.
> >Do unknown functions have to get info from yours, or does yours have to
> >get info from others?
> >
> This is one way. just myfunction() from myfunction.so will examine
> the stack and associated modules.
> 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.
> Thanks
> Dan
> Thanks
> Dan
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

More information about the LUG mailing list