I have discover that if you have your symbols on a mapped drive, wndbg will
not see them (even though the driver letter is browse-able) until you do
something like use the Symbol File Path to browse the mapped drive ( you
don’t need to actually set the path, as it is presumably already correctly
set, just open the mapped drive). Vista has other issues with mapped drives,
so this may not really be a windbg problem.
Then, the symbols will be seen.
I’m not entirely clear what you mean by ‘just open the mapped drive’ in the context of windbg, but it sounds different than at least the uac related mapped drive issue that I’m thinking of that drives me out of mind pretty much every time I map a drive in cmd32 and then can’t see it in Explorer. One would think that after say three years of this, I would learn, but more often than not, not so much.
In any case, is that what you’re seeing/expecting?
mm
Post output of an attempt to load symbols in this state with !sym noisy active?
- S
From: Jim Donelson
Sent: Friday, May 29, 2009 06:31
To: Kernel Debugging Interest List
Subject: [windbg] minor windbg issue 6.11 404 vista
I have discover that if you have your symbols on a mapped drive, wndbg will not see them (even though the driver letter is browse-able) until you do something like use the Symbol File Path to browse the mapped drive ( you don’t need to actually set the path, as it is presumably already correctly set, just open the mapped drive). Vista has other issues with mapped drives, so this may not really be a windbg problem.
Then, the symbols will be seen.
— 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
To clarify:
If you select “Symbol File Path” from the file directory, click browse,
click the mapped drive to “open it” then it works.
As I said, I see other strange issues with mapped drives - You see them in
explorer, but if you go to a command line, you may or may not see them.’
On Fri, May 29, 2009 at 9:37 AM, wrote:
> I’m not entirely clear what you mean by ‘just open the mapped drive’ in the
> context of windbg, but it sounds different than at least the uac related
> mapped drive issue that I’m thinking of that drives me out of mind pretty
> much every time I map a drive in cmd32 and then can’t see it in Explorer.
> One would think that after say three years of this, I would learn, but more
> often than not, not so much.
>
> In any case, is that what you’re seeing/expecting?
>
> mm
>
> —
> 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
>
I will next time I get this, but the issue is it simply does not see the
mapped drive until I do as I said above.
Once it sees the drive, no issues.
On Fri, May 29, 2009 at 10:55 AM, Skywing wrote:
> Post output of an attempt to load symbols in this state with !sym noisy
> active?
>
> - S
>
> ------------------------------
> From: Jim Donelson
> Sent: Friday, May 29, 2009 06:31
> To: Kernel Debugging Interest List
> Subject: [windbg] minor windbg issue 6.11 404 vista
>
> I have discover that if you have your symbols on a mapped drive, wndbg
> will not see them (even though the driver letter is browse-able) until you
> do something like use the Symbol File Path to browse the mapped drive ( you
> don’t need to actually set the path, as it is presumably already correctly
> set, just open the mapped drive). Vista has other issues with mapped drives,
> so this may not really be a windbg problem.
> Then, the symbols will be seen.
>
> — 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
>
Before you do the symbol file path thing (which I completely misunderstood originally; my bad), what does ‘net use’ report about the drives status? If you’re seeing them in explorer but not in cmd, I would say that the odds are excellent that you’re running an elevated UAC. I don’t see how that could be your problem here, but I do wonder is whether the status shows as ‘disconnected,’ because as I recall, trying to use a drive in such state from CMD fails at least for some operations, but selecting it in explorer will usually work, all other things equal, so maybe windbg works like that?
Just a theory; I have no idea, and Key certainly has already provided the best diagnostic path.
Good luck,
mm
If that is so, then I would like to see the error status returned from the attempt to access the path.
- S
From: Jim Donelson
Sent: Friday, May 29, 2009 10:37
To: Kernel Debugging Interest List
Subject: Re: [windbg] minor windbg issue 6.11 404 vista
I will next time I get this, but the issue is it simply does not see the mapped drive until I do as I said above.
Once it sees the drive, no issues.
On Fri, May 29, 2009 at 10:55 AM, Skywing > wrote:
Post output of an attempt to load symbols in this state with !sym noisy active?
- S
________________________________
From: Jim Donelson >
Sent: Friday, May 29, 2009 06:31
To: Kernel Debugging Interest List >
Subject: [windbg] minor windbg issue 6.11 404 vista
I have discover that if you have your symbols on a mapped drive, wndbg will not see them (even though the driver letter is browse-able) until you do something like use the Symbol File Path to browse the mapped drive ( you don’t need to actually set the path, as it is presumably already correctly set, just open the mapped drive). Vista has other issues with mapped drives, so this may not really be a windbg problem.
Then, the symbols will be seen.
— 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
— 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