344        core file can contain entries for CTF, symbol table, and string table
 345        sections. The sh_addr fields are set to the base address of the first
 346        mapping of the load object that they came from to. This can be used to
 347        match those sections with the corresponding load object.
 348 
 349 
 350        The size of the core file created by a process can be controlled by the
 351        user (see getrlimit(2)).
 352 
 353 SEE ALSO
 354        elfdump(1), gcore(1), mdb(1), proc(1), ps(1), coreadm(1M),
 355        getrlimit(2), setrlimit(2), setuid(2), sysinfo(2), uname(2),
 356        getzonenamebyid(3C), getzoneid(3C), elf(3ELF), signal.h(3HEAD),
 357        a.out(4), proc(4), zones(5), security-flags(5)
 358 
 359 
 360        ANSI C Programmer's Guide
 361 
 362 
 363 
 364                                  July 23, 2015                         CORE(4)

 344        core file can contain entries for CTF, symbol table, and string table
 345        sections. The sh_addr fields are set to the base address of the first
 346        mapping of the load object that they came from to. This can be used to
 347        match those sections with the corresponding load object.
 348 
 349 
 350        The size of the core file created by a process can be controlled by the
 351        user (see getrlimit(2)).
 352 
 353 SEE ALSO
 354        elfdump(1), gcore(1), mdb(1), proc(1), ps(1), coreadm(1M),
 355        getrlimit(2), setrlimit(2), setuid(2), sysinfo(2), uname(2),
 356        getzonenamebyid(3C), getzoneid(3C), elf(3ELF), signal.h(3HEAD),
 357        a.out(4), proc(4), zones(5), security-flags(5)
 358 
 359 
 360        ANSI C Programmer's Guide
 361 
 362 
 363 
 364                                  June 6, 2016                          CORE(4)