From: Simon on
Hi,

One of our app creates a crash dump file.

What we have is:

- VS2008 Pro
- /DEBUG, (Generate Debug Info)
- No private symbols.
- /Ox, (Full Optimization)
- /OPT:REF, (Eliminate Unreferenced data).
- No map file.

The dump itself is created using

- MiniDumpWriteDump(GetCurrentProcess(),
GetCurrentProcessId(),
...,
MiniDumpNormal,
...,
NULL,
NULL);

The dmp file created seems fine, (by that I mean it seems to work), I
can open the dmp file with VS2008 and VS2010 and it takes me straight to
the location of the crash, (NULL pointer allocation in my case).

But I don't seem able to get the value of any local variables.
I can get the value of the global variables.

Would anybody know off-hand what setting might be missing to include
stack/heap values?

Thanks

Simon
From: David Lowndes on
>The dmp file created seems fine, (by that I mean it seems to work), I
>can open the dmp file with VS2008 and VS2010 and it takes me straight to
>the location of the crash, (NULL pointer allocation in my case).
>
>But I don't seem able to get the value of any local variables.
>I can get the value of the global variables.
>
>Would anybody know off-hand what setting might be missing to include
>stack/heap values?

Simon,

Most likely because of /Ox.

Try disabling optimisation and see if that makes a difference.

Dave
From: David Ching on
"Simon" <bad(a)example.com> wrote in message
news:#sLNXmo8KHA.3840(a)TK2MSFTNGP02.phx.gbl...
> But I don't seem able to get the value of any local variables.
> I can get the value of the global variables.
>

Specify /Zi (Program DataBase)

-- David

From: Simon on
>> But I don't seem able to get the value of any local variables.
>> I can get the value of the global variables.
>>
>
> Specify /Zi (Program DataBase)
>
> -- David

Sorry, I should have said that this setting is on as well.
Without it you only get assembly code anyway.

Simon
From: Simon on
>
> Most likely because of /Ox.
>
> Try disabling optimisation and see if that makes a difference.
>

Hum, I am not sure I want to do away with this setting.
Luckily for us the app does not crash that often, (touch wood), so I am
not sure if the cost of removing optimisation, (how ever little it
really does help), outweigh the need to know about every single variables.

Interestingly I see that _some_ local variables are showing.

Simon