.th CORE V 2/11/75.sh NAMEcore \*- format of core image file.sh DESCRIPTIONUNIXwrites out a core image of a terminatedprocess when any of various errors occur.See.it "signal (II)"for the list of reasons;the most common are memory violations, illegalinstructions, bus errors, and user-generatedquit signals.The core image is called ``core'' and is written in the process'sworking directory (provided it can be; normalaccess controls apply)..s3The first 1024 bytes of the core imageare a copy of the system's per-userdata for the process, including the registersas they were at the time of the fault.Theremainder represents the actual contents ofthe user's core area when the core imagewas written.If the text segmentis write-protected and shared,it is not dumped; otherwise the entireaddress space is dumped..s3The format of theinformation in the first 1024 bytesis described bythe.it userstructure of the system.The important stuff not detailed therein is the locations of the registers.Here are their offsets.The parenthesized numbers for the floating registers areused if the floating-point hardware is insingle precision mode,as indicated in the status register..s3.lp +10 7fpsr	0004.lp +10 7fr0	0006  (0006).lp +10 7fr1	0036  (0022).lp +10 7fr2	0046  (0026).lp +10 7fr3	0056  (0032).lp +10 7fr4	0016  (0012).lp +10 7fr5	0026  (0016).lp +10 7r0	1772.lp +10 7r1	1766.lp +10 7r2	1750.lp +10 7r3	1752.lp +10 7r4	1754.lp +10 7r5	1756.lp +10 7sp	1764.lp +10 7pc	1774.lp +10 7ps	1776.s3.i0In general the debuggers.it "db (I)"and.it "cdb (I)"are sufficient to deal with core images..sh "SEE ALSO"cdb (I), db (I), signal (II)