“Dump file is too large to map”

Gebis@discussions.microsoft.com Michael Gebis

unread,

Aug 30, 2007, 6:58:03 PM8/30/07

to

I have a large user dump file--1.83GB, in fact. When I try to open it in
WinDbg, I get an error that states: “Dump file is too large to map”.

The obvious guess is that the process crashed because of an out-of-memory
condition, but I would still like to open the file in windbg to further debug
the issue.

Is there any way to open this dump file? I've tried using both WinDbg
6.6.0007.5 and 6.7.0005.1. Various searches haven't turned anything up.

I even tried booting with the /3GB flag and used editbin to set the
LARGEADDRESSAWARE flag on the windbg executable--no dice, I still could not
open that gigantic dump file.

Thanks!

Ivan Brugiolo [MSFT]

unread,

Aug 31, 2007, 12:26:13 PM8/31/07

to

Can you use cdb.exe and then remote to it with windbg.exe ?
Can you use an x64 machine ?

--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Michael Gebis" <Michael Ge...@discussions.microsoft.com> wrote in message
news:2FEA7DB6-B050-4DB1...@microsoft.com...

Michael Gebis

unread,

Aug 31, 2007, 1:38:03 PM8/31/07

to

Unfortunately, I don't have access to a 64 bit system at the moment.

I tried cdb.exe too, but it immediately gave essentially the same error:
cdb -z Dump-20070826-180338-1172-284-0.dmp

Loading Dump File [Dump-20070826-180338-1172-284-0.dmp]

Dump file is too large to map

Could not open dump file [Dump-20070826-180338-1172-284-0.dmp], Win32 error
0n87
"The parameter is incorrect."
Debuggee initialization failed, Win32 error 0n87
"The parameter is incorrect."

Gebis@discussions.microsoft.com Michael Gebis

unread,

Sep 27, 2007, 7:54:01 PM9/27/07

to

Thanks, Ivan.

I finally managed to get my hands on an x64 machine and open this same dump.
WinDbg replied with the same "dump file is too large to map" error message.
(And as I indicated in my earlier post, cdb was not able to open the file,
either)

We have pretty much given up hope on being able to open up this particular
dump file. But since it is difficult to reproduce the crash, this gigantic
dump file is still our best clue as to our internal bug, so any other
suggestions that might allow us to open it would be welcome.

Thanks!

Michael

Ivan Brugiolo [MSFT]

unread,

Sep 28, 2007, 2:57:15 AM9/28/07

to

Are you positive you are using the 64-bit debuggers on the X64 box ?
I have myself opened several times a 2+ Gig dump-file without issues, and,
I'm told that a crashdump taken on an HP-Supedome 64-proc Itanium2
was several Gigabytes in size and it was manageable.

Assuming all of the above are verified,
I'm inclined to say the dump-file is corrupted.
--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Michael Gebis" <Michael Ge...@discussions.microsoft.com> wrote in message

news:B30733A9-F431-4615...@microsoft.com...