Convert user mode handle to event structure?

  • Follow


I have a user mode dump from which  I was able to find a questionable handle 
to an event and would like to view the event structure itself. Is there any 
way in WinDbg to get from this handle to the actual event structure?

The reason I want to do this is because there is a list of 33 event handles 
being passed in from Outlook to a ntdll!ZwWaitForMultipleObjects. An 
exception is being thrown within this call that says to the effect that 

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments 
are invalid

I wanted to check the list of event handles to see which one was wonky. 
Using !handle <handle> does not reveal anything questionable. It seems to 
think that all of the handles are reasonably fit.
0
Reply Utf 12/4/2009 3:52:02 PM

Well the simple thing is to use

!handle <handle number> f

This should display all you need.


-- 
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr


"Richard Lewis Haggard" <RichardLewisHaggard@discussions.microsoft.com> 
wrote in message news:8A13ACEB-A4AB-4ED9-9024-DEC313E3BD94@microsoft.com...
>I have a user mode dump from which  I was able to find a questionable 
>handle
> to an event and would like to view the event structure itself. Is there 
> any
> way in WinDbg to get from this handle to the actual event structure?
>
> The reason I want to do this is because there is a list of 33 event 
> handles
> being passed in from Outlook to a ntdll!ZwWaitForMultipleObjects. An
> exception is being thrown within this call that says to the effect that
>
> EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments
> are invalid
>
> I wanted to check the list of event handles to see which one was wonky.
> Using !handle <handle> does not reveal anything questionable. It seems to
> think that all of the handles are reasonably fit.
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 4661 (20091204) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> 



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4661 (20091204) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com




0
Reply Don 12/4/2009 3:59:14 PM


>Is there any way in WinDbg to get from this handle to the actual event 
>structure?

User mode dumps don't have kernel mode memory, so you can't get the actual 
event object. So, anything you can get from !handle is about it.

> EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments
> are invalid

0x80000003 is also the NTSTATUS code for STATUS_BREAKPOINT.

-scott

-- 
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com


"Richard Lewis Haggard" <RichardLewisHaggard@discussions.microsoft.com> 
wrote in message news:8A13ACEB-A4AB-4ED9-9024-DEC313E3BD94@microsoft.com...
>I have a user mode dump from which  I was able to find a questionable 
>handle
> to an event and would like to view the event structure itself. Is there 
> any
> way in WinDbg to get from this handle to the actual event structure?
>
> The reason I want to do this is because there is a list of 33 event 
> handles
> being passed in from Outlook to a ntdll!ZwWaitForMultipleObjects. An
> exception is being thrown within this call that says to the effect that
>
> EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments
> are invalid
>
> I wanted to check the list of event handles to see which one was wonky.
> Using !handle <handle> does not reveal anything questionable. It seems to
> think that all of the handles are reasonably fit. 


0
Reply Scott 12/4/2009 4:32:54 PM

Richard Lewis Haggard <RichardLewisHaggard@discussions.microsoft.com>
wrote:
>...
>The reason I want to do this is because there is a list of 33 event handles 
>being passed in from Outlook to a ntdll!ZwWaitForMultipleObjects. An 
>exception is being thrown within this call that says to the effect that 
>
>EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments 
>are invalid

0x80000003 is not "invalid argument".  It's a breakpoint, possibly from an
assert.  How did you determine there was an invalid argument?
-- 
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
0
Reply Tim 12/6/2009 6:17:38 AM

3 Replies
282 Views

(page loaded in 0.074 seconds)

Similiar Articles:
















7/28/2012 4:02:40 AM


Reply: