Re: Interpreting program core dump in mdb

EricF wrote:

So anyway, some pointers to interpreting the context around a crash
using mdb would be appreciated.

TIA

It would help if you built with debug enabled, which is a -g parameter.

Eric

We did build a -g version here and purposely bombed it by feeding NULL
as the strncpy source argument. For some reason, the ::stack display
was no more symbolic, remaining cryptic without a secret decoder ring.

We put the customer through a lot trying various things prior to
obtaining the core dump. So we are kind of laying off them for
a little bit. We'd like to understand what we are seeing before
bothering them again with another binary. (And honestly, the nature
of this thing makes me suspect that -g will make the problem go
away. Sticking debug statements near the strncpy seemed to heal
things...)

Nobody can tell what the values being displayed by ::stack are?

--
Clem
"If you push something hard enough, it will fall over."
- Fudd's first law of opposition
.