Type conflict error at '<EOL>'

I’ve used windbg for decades. Never saw this error until today.

When I type

bu module!routine
I get
Type conflict error at ‘’

No matter what the module is. I have correct symbols for nt.

thanks,

Try .reload

It seems that windbg 6.11, 6,12 often fails to detect that target
has restarted, and get extremely confused.

– pa

wrote in message news:xxxxx@windbg…
>
> I’ve used windbg for decades. Never saw this error until today.
>
> When I type
>>bu module!routine
> I get
>>Type conflict error at ‘’
>
> No matter what the module is. I have correct symbols for nt.
>
> thanks,
>
>
>

Thanks. Also it used to be easy to get the latest windbg, now it seems to be bundled with an sdk?
Can you still get the latest, stand alone?

Are you doing something that isn’t really a shutdown when you ‘restart’ the target (such as resuming a previous VM snapshot or the like)?

  • S

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Tuesday, July 27, 2010 1:23 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Type conflict error at ‘’

Try .reload

It seems that windbg 6.11, 6,12 often fails to detect that target has restarted, and get extremely confused.

– pa

wrote in message news:xxxxx@windbg…
>
> I’ve used windbg for decades. Never saw this error until today.
>
> When I type
>>bu module!routine
> I get
>>Type conflict error at ‘’
>
> No matter what the module is. I have correct symbols for nt.
>
> thanks,
>
>
>


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Any messages in there about not being able to find the debugger datablock?

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Tuesday, July 27, 2010 2:58 PM
To: Kernel Debugging Interest List
Subject: RE: Re:[windbg] Type conflict error at ‘’

Are you doing something that isn’t really a shutdown when you ‘restart’ the
target (such as resuming a previous VM snapshot or the like)?

- S

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Tuesday, July 27, 2010 1:23 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Type conflict error at ‘’

Try .reload

It seems that windbg 6.11, 6,12 often fails to detect that target has
restarted, and get extremely confused.

– pa

wrote in message news:xxxxx@windbg…
>
> I’ve used windbg for decades. Never saw this error until today.
>
> When I type
>>bu module!routine
> I get
>>Type conflict error at ‘’
>
> No matter what the module is. I have correct symbols for nt.
>
> thanks,
>
>
>


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

“Skywing” wrote in message
news:xxxxx@windbg…
> Are you doing something that isn’t really a shutdown when you ‘restart’
> the target (such as resuming a previous VM snapshot or the like)?
>
> - S

Yes, sometimes with VMs and sometimes when a real machine connected over
serial, resets.
Windbg displays the usual startup messages from the target, but for whatever
reason
won’t understand that the target has restarted, so all its cached modules
and symbols
info is stale. Instead, it complains about overlapping modules, etc.

Regards,
–pa

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
> Sent: Tuesday, July 27, 2010 1:23 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] Type conflict error at ‘’
>
> Try .reload
>
> It seems that windbg 6.11, 6,12 often fails to detect that target has
> restarted, and get extremely confused.
>
> – pa
>
> wrote in message news:xxxxx@windbg…
>>
>> I’ve used windbg for decades. Never saw this error until today.
>>
>> When I type
>>>bu module!routine
>> I get
>>>Type conflict error at ‘’
>>
>> No matter what the module is. I have correct symbols for nt.
>>
>> thanks,
>>
>>
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Negative - you have to download either the SDK or WDK.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Tuesday, July 27, 2010 2:58 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Type conflict error at ‘’

Thanks. Also it used to be easy to get the latest windbg, now it seems to be
bundled with an sdk?
Can you still get the latest, stand alone?


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OK thanks, I’ll download the DDK.
But, back to symbols. Here is what I’m used to:
With bp you have to have correct symbols.
With bu it should defer symbols resolution till later, and never complain on the spot if the module is not loaded. Once, the module is loaded it can complain about mismatch or any other issue.
So if module m is not loaded, then
bu m!routine
should always succeed.

But … I do believe there is a separate install for the debugger in the
WDK.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O’Brien
Sent: Tuesday, July 27, 2010 7:36 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Type conflict error at ‘’

Negative - you have to download either the SDK or WDK.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Tuesday, July 27, 2010 2:58 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Type conflict error at ‘’

Thanks. Also it used to be easy to get the latest windbg, now it seems to be
bundled with an sdk?
Can you still get the latest, stand alone?


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

When errors like this occur (or that sound like this), windbg does some very
strange stuff. If you’re relying on the error message being meaningful,
that might be a mistake.

Good luck,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Tuesday, July 27, 2010 9:09 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Type conflict error at ‘’

OK thanks, I’ll download the DDK.
But, back to symbols. Here is what I’m used to:
With bp you have to have correct symbols.
With bu it should defer symbols resolution till later, and never complain on
the spot if the module is not loaded. Once, the module is loaded it can
complain about mismatch or any other issue.
So if module m is not loaded, then
bu m!routine
should always succeed.


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer