From: Danny Backx <danny.backx@scarlet.be>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: Post mortem debugging for Windows CE
Date: Tue, 28 Apr 2009 14:45:00 -0000 [thread overview]
Message-ID: <1240929901.29047.110.camel@dannypc> (raw)
Hi,
I wrote a program, see below, that can be used either on a development
host, or on a Windows CE target, to decode stuff from a dump file as
generated by CE.
I don't think gdb currently has this capability (to inspect postmortem
dump files) for debugging CE applications.
Is this something I should port into the gdb source tree and submit, or
is it not worth it ? If yes, please advise where this belongs.
Sources are in the SVN of the cegcc project
(https://cegcc.svn.sourceforge.net/svnroot/cegcc/trunk/cegcc/tools/cedump) .
Danny
dannypc: {1273} rsh
ipaq /temp/cedump /windows/system/dumpfiles/Ce042709-01/Ce042709-01.kdmp
Number of streams 10
stream 0, type 8001 (System info), size 72
System info :
arch 5, 1 processors
Proc type 2577 level 4 rev 1
Proc family 4 Platform 3
Locale id 2067 813
OEM {hp iPAQ 210}
stream 1, type 8002 (Exception), size 160
Exception : code C0000005, flags 0, address 1117C
Parameter 0 : [1]
Parameter 1 : [26000000]
stream 2, type 8003 (Module), size 336
Element 0 :
Name : NK.EXE
Base Ptr : 0x80001000
Element 1 :
Name : null2.exe
Base Ptr : 0x26010000
Element 2 :
Name : coredll.dll.0409.mui
Base Ptr : 0x7FFE0000
Element 3 :
Name : coredll.dll
Base Ptr : 0x03F4E000
stream 3, type 8004 (Process), size 208
Element 0 :
ProcSlot# : 0
Name : NK.EXE
VMBase : 0xC2000000
BasePtr : 0x80001000
pProcess : 0x8034D260
Element 1 :
ProcSlot# : 18
Name : null2.exe
VMBase : 0x26000000
BasePtr : 0x00010000
pProcess : 0x8034E340
stream 4, type 8005 (Thread), size 416
Element 0 :
pThread : 0x8172B640
RunState : Awak,Rung
hThread : 0x22CE3EAE
LastError : 0x00000000
PC : 0x0001117C
StkRetAddr : 0x00000000
stream 5, type 8006 (Thread Context), size 48
Element 0 :
ThreadID : 0x22ce3eae
stream 6, type 8007 (Thread Callstack), size 24
Thread Call Stack List : 1 entries
Process 22E4A1C6 thread 22CE3EAE, 1 frames
Frame 0 : RetAddr 0x2601117C FP 0x2611FE04
stream 7, type 800a (Bucket parameters), size 64
stream 8, type 8008 (Memory virtual list), size 56
stream 9, type 8009 (Memory physical list), size 8
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
next reply other threads:[~2009-04-28 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 14:45 Danny Backx [this message]
2009-04-28 16:02 ` Pedro Alves
2009-04-28 17:48 ` Danny Backx
2009-04-28 19:18 ` Danny Backx
2009-04-29 7:10 ` Eli Zaretskii
2009-04-29 7:19 ` Danny Backx
2009-04-29 7:44 ` Eli Zaretskii
2009-04-30 7:25 ` Danny Backx
2009-04-30 9:58 ` Pedro Alves
2009-05-01 14:35 ` Danny Backx
2009-05-01 15:37 ` Pedro Alves
2009-05-05 13:31 ` Danny Backx
2009-05-05 16:53 ` Pedro Alves
2009-05-06 14:13 ` Danny Backx
2009-05-06 14:34 ` Pedro Alves
2009-05-06 20:05 ` Danny Backx
2009-05-06 20:47 ` Pedro Alves
2009-05-07 1:21 ` Danny Backx
2009-05-10 19:21 ` Pedro Alves
2009-05-11 14:03 ` Danny Backx
2009-05-11 15:00 ` Danny Backx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1240929901.29047.110.camel@dannypc \
--to=danny.backx@scarlet.be \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox