segmentation fault on Unix - possible stack corruption
Posted
by bob
on Stack Overflow
See other posts from Stack Overflow
or by bob
Published on 2009-02-26T17:02:39Z
Indexed on
2010/05/07
0:38 UTC
Read the original article
Hit count: 447
hello,
i'm looking at a core from a process running in Unix. Usually I can work my around and root into the backtrace to try identify a memory issue. In this case, I'm not sure how to proceed.
Firstly the backtrace only gives 3 frames where I would expect alot more. For those frames, all the function parameters presented appears to completely invalid. There are not what I would expect.
Some pointer parameters have the following associated with them - Cannot access memory at address
Would this suggest some kind of complete stack corruption. I ran the process with libumem and all the buffers were reported as being clean.
umem_status reported nothing either.
so basically I'm stumped. What is the likely causes? What should I look for in code since libumem appears to have reported no errors.
Any suggestions on how I can debug furhter? any extra features in mdb I should consider?
thank you.
© Stack Overflow or respective owner