crashpad

3party/crashpad

Fork 0

mirror of https://github.com/chromium/crashpad.git synced 2025-03-10 06:36:02 +00:00

Commit Graph

Author	SHA1	Message	Date
Scott Graham	ecf3b37863	win: Save contents of TEBs allowing !teb and !gle to work in windbg crashy_program's log looks something like this now: 0:000> .ecxr eax=00000007 ebx=7f24e000 ecx=7f24d000 edx=00000000 esi=00497ec8 edi=00d39ca0 eip=00cf5d12 esp=001ffcd8 ebp=001ffcdc iopl=0 nv up ei ng nz ac po cy cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010293 crashy_program+0x5d12: 00cf5d12 ?? ??? 0:000> !teb TEB at 7f24d000 ExceptionList: 001ff548 StackBase: 00200000 StackLimit: 001fd000 SubSystemTib: 00000000 FiberData: 00001e00 ArbitraryUserPointer: 00000000 Self: 7f24d000 EnvironmentPointer: 00000000 ClientId: 00003658 . 00004630 RpcHandle: 00000000 Tls Storage: 7f24d02c PEB Address: 7f24e000 LastErrorValue: 2 LastStatusValue: c000000f Count Owned Locks: 0 HardErrorMode: 0 0:000> !gle LastErrorValue: (Win32) 0x2 (2) - The system cannot find the file specified. LastStatusValue: (NTSTATUS) 0xc000000f - {File Not Found} The file %hs does not exist. R=mark@chromium.org BUG=crashpad:46 Review URL: https://codereview.chromium.org/1364803004 .	2015-10-01 14:04:49 -07:00
Scott Graham	5a21de6a1b	win: Retrieve thread context for x64 Retrieve context and save to thread context. NtQueryInformationThread is no longer required (right now?) because to retrieve the CONTEXT, the thread needs to be Suspend/ResumeThread'd anyway, and the return value of SuspendThread is the previous SuspendCount. I haven't handle the x86 case yet -- that would ideally be via Wow64GetThreadContext (I think) but unfortunately that's Vista+, so I'll likely need to to a bit of fiddling to get that sorted out. (It's actually likely going to be NtQueryInformationThread again, but one thing at a time for now.) R=cpu@chromium.org, rsesek@chromium.org TBR=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/1133203002	2015-05-14 17:37:02 -07:00
Scott Graham	658cd3e1a7	win: Add thread snapshot and memory snapshot for stacks The next big piece of functionality in snapshot. There's a bit more grubbing around in the NT internals than would be nice, and it has made me start to question the value avoiding MinidumpWriteDump. But this seems to extract most of the data we need (I haven't pulled the cpu context yet, but I hope that won't be too hard.) R=mark@chromium.org BUG=crashpad:1 Review URL: https://codereview.chromium.org/1131473005	2015-05-11 13:29:52 -07:00

Author

SHA1

Message

Date

Scott Graham

ecf3b37863

win: Save contents of TEBs allowing !teb and !gle to work in windbg

crashy_program's log looks something like this now:

0:000> .ecxr
eax=00000007 ebx=7f24e000 ecx=7f24d000 edx=00000000 esi=00497ec8 edi=00d39ca0
eip=00cf5d12 esp=001ffcd8 ebp=001ffcdc iopl=0         nv up ei ng nz ac po cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
crashy_program+0x5d12:
00cf5d12 ??              ???
0:000> !teb
TEB at 7f24d000
    ExceptionList:        001ff548
    StackBase:            00200000
    StackLimit:           001fd000
    SubSystemTib:         00000000
    FiberData:            00001e00
    ArbitraryUserPointer: 00000000
    Self:                 7f24d000
    EnvironmentPointer:   00000000
    ClientId:             00003658 . 00004630
    RpcHandle:            00000000
    Tls Storage:          7f24d02c
    PEB Address:          7f24e000
    LastErrorValue:       2
    LastStatusValue:      c000000f
    Count Owned Locks:    0
    HardErrorMode:        0
0:000> !gle
LastErrorValue: (Win32) 0x2 (2) - The system cannot find the file specified.
LastStatusValue: (NTSTATUS) 0xc000000f - {File Not Found}  The file %hs does not exist.

R=mark@chromium.org
BUG=crashpad:46

Review URL: https://codereview.chromium.org/1364803004 .

2015-10-01 14:04:49 -07:00

Scott Graham

5a21de6a1b

win: Retrieve thread context for x64

Retrieve context and save to thread context. NtQueryInformationThread
is no longer required (right now?) because to retrieve the CONTEXT, the
thread needs to be Suspend/ResumeThread'd anyway, and the return value
of SuspendThread is the previous SuspendCount.

I haven't handle the x86 case yet -- that would ideally be via
Wow64GetThreadContext (I think) but unfortunately that's Vista+, so I'll
likely need to to a bit of fiddling to get that sorted out. (It's actually
likely going to be NtQueryInformationThread again, but one thing at a
time for now.)

R=cpu@chromium.org, rsesek@chromium.org
TBR=mark@chromium.org
BUG=crashpad:1

Review URL: https://codereview.chromium.org/1133203002

2015-05-14 17:37:02 -07:00

Scott Graham

658cd3e1a7

win: Add thread snapshot and memory snapshot for stacks

The next big piece of functionality in snapshot. There's a bit more
grubbing around in the NT internals than would be nice, and it has
made me start to question the value avoiding MinidumpWriteDump. But
this seems to extract most of the data we need (I haven't pulled
the cpu context yet, but I hope that won't be too hard.)

R=mark@chromium.org
BUG=crashpad:1

Review URL: https://codereview.chromium.org/1131473005

2015-05-11 13:29:52 -07:00

3 Commits