Presumably, the applicable
ulimits are not (too) restrictive ?
If nothing else crops up, it might be worthwhile downloading & installing the SUNWscat package - which will give you extended crash analysis capability on the generated core file - which is a useful tool to have on a Solaris box anyway.
If you're interested, I can recommend 'Panic! Unix System Crash Dump Analysis' by Drake & Brown - it does have a leaning toward (rather old, but nontheless pertinent) Solaris, but seeks to maintain a general approach - I got my copy, 2nd hand, via Amazon UK.
Update:
Added book ref.
A user level that continues to overstate my experience :-))
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.