| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | core dump |
Original from Paul Edwards to All on 10-20-1996
Original Subject: core dump
---------------------------------------
PE> On a unix system, when your application crashes
PE> (traps/abends), you get a file called "core" containing all
PE> the program and data for that application, so that you can
PE> debug what was happening at the time. On MVS, you get a
PE> dump file sent to SYSUDUMP. With OS/2, if the whole system
PE> crashes, you can go ctrl-alt-numlock numlock and get a dump
PE> of all of your memory for all applications.
PE>
PE> How do I get a dump for just my one task, when that one
PE> task has a trap-d? BFN. Paul.
DUMPPROCESS=x in your config.sys. Creates files PDUMP.001, PDUMP.002,
etc. Use PMDF (from devcon or product CDROM) to analyze.
Not nearly as useful as it is in MVS. It only dumps the regs and the
stack. No code or data areas.
It is a little more useful under Warp 4, but I have not yet decided
on how useful it would be without complete source/compile/link reorts
files. I suspect this will continue to be a developer only (not
support) oriented facility.
Oh.. Check the use of the TRAPDUMP and TRACE facility too.. Although
not quite what you are asking, it is quite useful in debugging.
Denis
Certified OS/2 Engineer, Certified OS/2 Instructor, Certifiable....
All opinions are my very own, IBM has no claim upon them
.
--- Maximus/2 3.01
* Origin: T-Board - (604) 277-4574 (1:153/908)SEEN-BY: 50/99 270/101 620/243 625/160 711/401 409 410 413 430 808 809 934 SEEN-BY: 711/955 712/407 515 624 628 713/317 800/1 @PATH: 153/908 8086 800 270/101 712/515 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.