debugging exe - Missing image name, possible paged-out or corrupt

[j.a. harriman]

Hi,
I'm debugging a program in WinDbg and I have never had these messages occur
before.

When I use lml command, I have all my symbol information (private or private
pdb symbols).

The messages occur either when I pause the debugger at a random point during
execution:

(1514.14cc): Break instruction exception - code 80000003 (first chance)
eax=7ffdf000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005
eip=7c90120e esp=00e6ffcc ebp=00e6fff4 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
ntdll!DbgBreakPoint:
7c90120e cc int 3
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.

or when I hit a set break point in "MyProgram":
Breakpoint 1 hit
eax=00000001 ebx=00000000 ecx=2dc9cded edx=0000006c esi=00467e33 edi=0012ff17
eip=00451ebe esp=0012fec4 ebp=0012ff34 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
MyProgram!MyProgram::process_input_file+0x11e:
00451ebe 0fb60dcd314800 movzx ecx,byte ptr [MyProgram!some_function_call
(004831cd)] ds:0023:004831cd=00
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.

I've come up with little or nothing on "google" searches.

Any thoughts as to what the issue might be, what to check, etc.?

Thanks.

[Ivan Brugiolo [MSFT]]

The debugger, in order to build the module list, normally relies on the
loder-list that it reads from the target.
The loader list stores the module names separately from the loder entries.
If the debugger cannot read the memory of the names from the entries,
or cannot validate the length of the names, it will error out accordingly.
You may want to try commands such as `!peb` or `!dlls` since they
both gives you an alternated way to print the loader list,
including possbibly missing names.

As far as that error is concerned, I have only seen it myself on
kernel-debugging sessions with paged-out module names.

I can build a contrieved heap corrution in user-mode
for the sake of reproing that outside of paging in KD, but,
that would not be a good proof on anything besisdes that the error can
happen.

--
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

"j.a. harriman" <jeffrey_no...@nospam.nospam> wrote in message
news:D411E0A3-7DCF-481C...@microsoft.com...

[j.a. harriman]

I raun both !peb & !dlls and at a quick glance didn't see anything. is there
something specific I should be looking for?

It is still ocurring under both conditions listed below. The only odd thing
that happened last week was I 'accidently' turned on a number of registry &
kernel flags with gflags. I was able to get back in and clear them all, but
am wondering if it is somehow related. I just checked it again and it's
'clean' for registry, kernel, and there are no settings for the image. I
thought it might only be when I was using AppVerifier, but I removed the
image form that and it still occurs.

I don't have any such errors when I run it under the VS2005 debugger, however.

Jeff

[Ivan Brugiolo [MSFT]]

With gflags.exe you still have the ability to enable verifier globally on
the machine.
try to see what `gflags -r` shows you

--
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

"j.a. harriman" <jeffrey_no...@nospam.nospam> wrote in message

news:3C11C161-1DF4-4BE4...@microsoft.com...

[opedroso]

On Oct 7, 9:51 am, j.a. harriman <jeffrey_no_spam_al...@nospam.nospam>
wrote:

Sad to say, but this is extremely common when running in XP64
environment (i.e. every debugging session).

Once you get this message, if you enter !lm, you will also see that
the list of unloaded DLLs seems corrupt.
The base address (which must match the pattern xxxx0000) seem corrupt
with non-zero values for all entries but the very first.

Osiris Pedroso

[j.a. harriman]

I ran gflags -r & gflags-k, both of the results were:
Current Boot Registry Settings are: 00000000
Current Running Kernel Settings are: 00000000

In regards to opedroso's comments, my OS is XP Pro SP 3 32K.

[Ivan Brugiolo [MSFT]]

Are you debugging a 32bit application with a 32bit debugger on wow64,
or, are you debugging a native 64 bit application ?

--

--
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

"opedroso" <oped...@gmail.com> wrote in message
news:a94c498e-d0a5-4107...@l35g2000vba.googlegroups.com...

[j.a. harriman]

I ran gflags -r & gflags-k, both of the results were:
Current Boot Registry Settings are: 00000000
Current Running Kernel Settings are: 00000000

In regards to opedroso's comments, my OS is XP Pro SP 3 32K.
Jeff

[j.a. harriman]

I am hoping someone picks this up so I don't have to post a new thread.

I'm still trying to track down the "Missing image name, possible paged-out
or corrupt data." issue.

I am running the app under WinDbg & AppVerifier (doing "basics" checks [a
number of heap options set to true] + all "misc" items checked).

Here's the output:
(1438.5e0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=04f11000 ecx=7c802413 edx=0a841000 esi=04f11000 edi=00000000
eip=00424513 esp=0e34ff3c ebp=0e34ff40 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
MyProgam!alert_operator_thread+0x43:
00424513 0fb6420d movzx eax,byte ptr [edx+0Dh]
ds:0023:0a84100d=??

Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.

I do !analyze -v and when I click on the hyperlink for "MODULE_NAME:
MyProgram", I get the following:

0:009> lmvm MyProgram
start end module name
00400000 00471000 MyProgram (private pdb symbols)
d:\testing\MyProgram\Release\MyProgram.pdb
Loaded symbol image file: MyProgram.exe
Image path: MyProgram.exe
Image name: MyProgram.exe
Timestamp: Fri Nov 13 15:33:29 2009 (4AFDD0A9)
CheckSum: 0007A0F8
ImageSize: 00071000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.

Also did the following:
0:009> !teb
TEB at 7ffd4000
ExceptionList: 0e44fef4
StackBase: 0e450000
StackLimit: 0e44e000
SubSystemTib: 00000000
FiberData: 00001e00
ArbitraryUserPointer: 00000000
Self: 7ffd4000
EnvironmentPointer: 00000000
ClientId: 00001438 . 00001168
RpcHandle: 00000000
Tls Storage: 00000000
PEB Address: 7ffde000
LastErrorValue: 0
LastStatusValue: 0
Count Owned Locks: 0
HardErrorMode: 0

0:009> !dlls

0x01489000: D:\programs\FTP\MyProgram.exe
Base 0x00400000 EntryPoint 0x0037f4ad Size 0x00071000
Flags 0x00005000 LoadCount 0x0000ffff TlsIndex 0x00000000
LDRP_LOAD_IN_PROGRESS
LDRP_ENTRY_PROCESSED

Any ideas as to what's going on?

Thanks.

[Marc Sherman]

Are you using either of the 6.11 versions of the debugger? If so, try the
6.10 version. That got rid of an error (can't remember exact error mesaage)
for me.

"j.a. harriman" <jeffrey_no...@nospam.nospam> wrote in message

news:68ABF501-3CEF-4BF0...@microsoft.com...