I agree that it wouldn’t hurt to have the actual feedback address printed
somewhere, but I’m not sure that this is quite the outrage that you think
it is.
I mean, if I were to make a list of the problems with the windbg docs and
why it’s not worth the time to submit feedback, personally, I would start
with that the docs do not appear to have been touched in years (I know they
weren’t for several years; may not be true anymore).
Mm
On Apr 20, 2012 7:25 PM, wrote:
> Clicking a mailto: requires that there be an email system installed on my
> machine, which there often isn’t, and that (in the one machine that still
> has Outlook Express) that the email is configured to actually be usable.
>
> Since I keep my documentation on my right-hand montitor, I can switch the
> left-hand monitor to the email machine, and type in anything I want.
>
> To me, the idea that I am assumed to have a machine configured like the
> one at the developer’s desktop is bizarre in the extreme, and I don’t
> bother going through the extra steps to view the source and find the link.
> It isn’t worth my time.
> joe
>
>
> > I still don’t understand. There’s only one email address for
> documentation
> > feedback, the link on the bottom is just a mailto that fills in the
> > subject
> > so that doc writers/maintainers know what you’re talking about. If there
> > was
> > just an email address on the bottom, they would have to put the onus on
> > the submitter to mention the doc page, date, source, etc. (in a standard
> > format, of course) when submitting the feedback. Though, if you really
> see
> > this as a problem and you prefer to do it that way, it doesn’t take much
> > to
> > parse the mailto link and figure out what the email address is.
> >
> > -scott
> >
> > –
> > Scott Noone
> > Consulting Associate and Chief System Problem Analyst
> > OSR Open Systems Resources, Inc.
> > http://www.osronline.com
> >
> > “Martin O’Brien” wrote in message news:xxxxx@windbg…
> >
> > Ah, my bad - I missed that part. I thought you wanted them to use some
> > other form of communication.
> >
> > mm
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of
> > xxxxx@flounder.com
> > Sent: Thursday, April 19, 2012 6:10 PM
> > To: Kernel Debugging Interest List
> > Subject: RE: [windbg] strange stack outputs in WinDBG
> >
> > Include an email address that is visible to the reader.
> > joe
> >
> >> What would you suggest they do instead?
> >>
> >>
> >>
> >> mm
> >>
> >>
> >> -----Original Message-----
> >> From: xxxxx@lists.osr.com
> >> [mailto:xxxxx@lists.osr.com] On Behalf Of
> >> xxxxx@flounder.com
> >> Sent: Thursday, April 19, 2012 5:22 PM
> >> To: Kernel Debugging Interest List
> >> Subject: Re: [windbg] strange stack outputs in WinDBG
> >>
> >> The problem is that the “send feedback” link, at least the last time I
> >> clicked on one, wanted to send email. I have ten machines here, and
> >> only two of them have email capability. Neither of these machines are
> >> my development machine, where I read the documentation.
> >>
> >> There are many unfortunate assumptions Microsoft makes, and one of
> >> them is that every machine has email connectivity.
> >> joe
> >>
> >>
> >>
> >>> Yeah, I will have to start doing this… Let’s see.
> >>>
> >>>
> >>> On Thu, Apr 19, 2012 at 11:38 AM, Skywing
> >>> wrote:
> >>>
> >>>> Use the ‘Send Feedback’ link conveniently placed on every doc page
> >>>> in these circumstances (otherwise the chances are slim to none that
> >>>> the documentation will change on its own based on unvoiced
> >>>> feedback).
> >>>>
> >>>> **
> >>>>
> >>>> - S (Msft)
> >>>>
> >>>> ****
> >>>>
> >>>> From: xxxxx@lists.osr.com [mailto:
> >>>> xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
> >>>> Sent: Thursday, April 19, 2012 8:10 AM
> >>>> To: Kernel Debugging Interest List
> >>>> Subject: Re: [windbg] strange stack outputs in WinDBG
> >>>>
> >>>> **
> >>>>
> >>>> This is where the Black Art resides 
> >>>>
> >>>> ****
> >>>>
> >>>> I usually look at the windbg help, then fire .chain then look at
> >>>> the helps related to those extension commands. Finally the blogs (
> >>>> including Urs :).
> >>>>
> >>>>
> >>>>
> >>>> But docs fail very short of what one would like to see. Dang I
> >>>> thought it is a piler and it is working as a wrench.
> >>>>
> >>>> ****
> >>>>
> >>>> As a TA, I once had to tell a student, Your answers to these
> >>>> probability questions themselves are probabilities - now I think
> >>>> about them, applies to myself and smile…
> >>>>
> >>>>
> >>>>
> >>>> -pro
> >>>>
> >>>> ****
> >>>>
> >>>> On Thu, Apr 19, 2012 at 7:18 AM, Scott Noone
> >>>> wrote:
> >>>>
> >>>> For completeness, !thread also supports flag 0x10 (which is the
> >>>> important one for including user mode state). Both of these are
> >>>> explained in the article for the curious.
> >>>>
> >>>>
> >>>>
> >>>> -scott
> >>>>
> >>>> –
> >>>> Scott Noone
> >>>> Consulting Associate and Chief System Problem Analyst OSR Open
> >>>> Systems Resources, Inc.
> >>>> http://www.osronline.com
> >>>>
> >>>> “Skywing” wrote in message news:xxxxx@windbg…
> >>>>
> >>>>
> >>>>
> >>>> You can use “!process 1f” as a shorthand, to dump all of
> >>>> the threads out while using the PTEs of that process.
> >>>>
> >>>> Note that if the data was paged out then there’s nothing you can
> >>>> really do here.
> >>>>
> >>>> - S (Msft)
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: xxxxx@lists.osr.com [mailto:
> >>>> xxxxx@lists.osr.com] On Behalf Of
> >>>> xxxxx@comcast.net
> >>>> Sent: Wednesday, April 18, 2012 4:12 PM
> >>>> To: Kernel Debugging Interest List
> >>>> Subject: RE:[windbg] strange stack outputs in WinDBG**
> >>>>
> >>>> Thank You Tim! and lucky for me I took an Entire Memory Dump. While
> >>>> I was poking around in the registry I decided it would be a good
> >>>> idea to manually enable that. So what I should be looking for is how
> >>>> to follow stacks going from ring 0 to ring 3 (for example) ?
> >>>>
> >>>> Thanks in advance,
> >>>>
> >>>> -JC
> >>>>
> >>>> —
> >>>> 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 ****
> >>>>
> >>>> —
> >>>> 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
> >>
> >>
> >> —
> >> 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
> >
>
>
>
> —
> 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
>