Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Win7 Symbol Problems... Fix Coming (we hope)
Peter_Viscarola_(OSR)
Administrator Posts: 9,113
in WINDBG
This problem just came to my attention last week (sorry... been busy). So, I asked around a bit to find out what was going on.
Apparently, one or more of the folks who got Mr. O'Brien's email to "WinDbgFb" was interested enough to follow-up on the problem. My sources tell me the problem is recognized, and that the fix is in progress. The fix apparently involves a ton of work. It's not merely a matter of grabbing the right symbols and publishing them.
In terms of a time-frame, no estimates have been released or even committed internally to the best of my knowledge. But the best guess by my sources was that we should see a fix hit the symbol server in the next week or two. I wouldn't be surprised if it took longer than that.
But the main message here is: People know about the problem, they understand the problem, and somebody's working on the problem.
I think we should all recognize that it's pretty cool that MSFT is fixing the problem, and not just saying "yeah, sorry... we'll fix that going forward." Especially given the amount of work the fix apparently requires.
Now you know what I know,
Peter
OSR
@OSRDrivers
Apparently, one or more of the folks who got Mr. O'Brien's email to "WinDbgFb" was interested enough to follow-up on the problem. My sources tell me the problem is recognized, and that the fix is in progress. The fix apparently involves a ton of work. It's not merely a matter of grabbing the right symbols and publishing them.
In terms of a time-frame, no estimates have been released or even committed internally to the best of my knowledge. But the best guess by my sources was that we should see a fix hit the symbol server in the next week or two. I wouldn't be surprised if it took longer than that.
But the main message here is: People know about the problem, they understand the problem, and somebody's working on the problem.
I think we should all recognize that it's pretty cool that MSFT is fixing the problem, and not just saying "yeah, sorry... we'll fix that going forward." Especially given the amount of work the fix apparently requires.
Now you know what I know,
Peter
OSR
@OSRDrivers
Peter Viscarola
OSR
@OSRDrivers
Howdy, Stranger!
| Upcoming OSR Seminars | ||
|---|---|---|
| OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
| Kernel Debugging | 16-20 October 2023 | Live, Online |
| Developing Minifilters | 13-17 November 2023 | Live, Online |
| Internals & Software Drivers | 4-8 Dec 2023 | Live, Online |
| Writing WDF Drivers | 10-14 July 2023 | Live, Online |
Comments
On behalf of the driver development community out there, thanks for chasing
this.
> I think we should all recognize that it's pretty cool that MSFT is fixing
> the problem,
> and not just saying "yeah, sorry... we'll fix that going forward."
> Especially given the
> amount of work the fix apparently requires.
Yea, +1 to that.
/Rod
Waiting for the fix for some time now.
On Tue, Oct 6, 2015 at 6:10 PM, Rod Widdowson
wrote:
> Peter,
>
> On behalf of the driver development community out there, thanks for
> chasing this.
>
> I think we should all recognize that it's pretty cool that MSFT is fixing
>> the problem,
>> and not just saying "yeah, sorry... we'll fix that going forward."
>> Especially given the
>> amount of work the fix apparently requires.
>>
>
> Yea, +1 to that.
>
> /Rod
>
> ---
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
> 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
>
--
Bercea. G.
Cheers,
Gabriel
And Microsoft's Windows Serviceability group must be unhappy that they can't run !process 0 0 and many other commands on kernel dumps provided by customers.
On 10/6/2015 9:10 AM, Rod Widdowson wrote:
> Peter,
>
> On behalf of the driver development community out there, thanks for chasing this.
>
>> I think we should all recognize that it's pretty cool that MSFT is fixing the problem,
>> and not just saying "yeah, sorry... we'll fix that going forward." Especially given the
>> amount of work the fix apparently requires.
>
> Yea, +1 to that.
>
> /Rod
And Microsoft's Windows Serviceability group must be unhappy that they can't run !process 0 0 and many other commands on kernel dumps provided by customers.
</quote>
Microsoft's internal groups would have access to private PDBs, which will have all the symbols. Indeed, this is one reason these things happen: the Microsoft folks use the full PDBs so commands work. The rest of the world must use the public symbols and if someone changes a debugger extension to require a symbol that isn't in the public symbols, they won't know it doesn't work until someone in the field notices and brings it to their attention.
Tony
OSR
> world must use the public symbols
> and if someone changes a debugger extension to require a symbol that isn't
> in the public symbols, they won't
> know it doesn't work until someone in the field notices and brings it to
> their attention.
yea, I've given up every expecting !fltkd to work when I need it to.
> Tuesday maintenance has good symbols, as does the accompanying
> KERNEL32.dll.
That is excellent news. Thanks again to all involved.
/Rod
Good job all !
On Wed, Oct 14, 2015 at 5:00 PM, Rod Widdowson
wrote:
> The 7601.19018.x86fre.win7sp1_gdr.150928-1507 kernel in today's Patch
>> Tuesday maintenance has good symbols, as does the accompanying KERNEL32.dll.
>>
>
> That is excellent news. Thanks again to all involved.
>
> /Rod
>
> ---
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
> 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
>
--
Bercea. G.
Cheers,
Gabriel
A big thanks to our friends at MSFT.