On Fri, 3 Nov 2006, James Carlson wrote:
Hema Huchegowda writes:
I tried what you suggested and that didn't seem to help me.
The core is from a solaris 9 box and I'm trying to read it from a
solaris 10 system:
Why not find an S9 box to do this?
I've brought in all the libraries this application dependents (as seen
in pldd output) on to the target system and placed them under: /test/libs
Mdb isn't quite the same as dbx.
In general, that's just not going to work. The philosophy behind mdb
Well James ... you've already become way too used to the new features of
Solaris 10 :)
The DBX approach is the "traditional" one so "solve" a long-standing
problem on UNIX - coredumps are incomplete, they're not self-consistent
entities but you need the rest of the "environment" to get at all of the
contents.
On closer inspection, this isn't a solution but a hacky workaround.
Because it requires the user of the debugger to know exactly what the
environment was that this coredump was created in. If you rely on third
parties (customers sending you a dump) for that information, it's prone to
be wrong/incomplete and you can just as well make a best-guess attempt.
Solaris 10 and later have therefore solved this problem in a different
way: by putting everything into the actual corefile to make it self-
consistent, and self-contained, so that the debugger itself no longer has
the need to be told "look at this library". This is what James refers to,
it's so useful to have this that one quickly forgets it's yet another one
of these "Solaris 10+ distinguishers" ...
See coreadm(1M) for details.
In short, on S10+ with mdb, you no longer need your "environment set".
All you need already is in the coredump by default, the library text as
well as all of the symbol tables and CTF data.
I'm not sure if DBX uses this. Have also grown too fond of mdb in the last
years... I only want a DDD interface for it :)
Have a nice weekend,
FrankH.
(and CTF) is that the core dump itself should carry the required
symbolic debug information, so that there's no question about what
exact objects made up the process in the first place. In the cases
where the core file doesn't have this information (as in old
releases), you just don't have symbols.
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
[email protected]
_______________________________________________
opensolaris-discuss mailing list
[email protected]
