From: Max Kaehn <slothman@electric-cloud.com>
To: <gdb@sourceware.org>
Subject: Re: Problem debugging core dump in gdb 7.1 on Solaris x86_64
Date: Fri, 25 Jun 2010 17:03:00 -0000 [thread overview]
Message-ID: <4C24E156.8050405@electric-cloud.com> (raw)
In-Reply-To: <4C2109B4.8070708@electric-cloud.com>
It turns out that the problem was that the default Solaris setting for
core dumps wasn't giving all information. Running "coreadm -G all -I
all" caused the system to start generating core dumps with readable call
stacks.
prev parent reply other threads:[~2010-06-25 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 19:06 Max Kaehn
2010-06-22 19:21 ` Michael Snyder
2010-06-22 22:59 ` Max Kaehn
2010-06-22 23:18 ` Michael Snyder
2010-06-22 23:56 ` Max Kaehn
2010-06-22 22:16 ` Max Kaehn
2010-06-25 17:03 ` Max Kaehn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C24E156.8050405@electric-cloud.com \
--to=slothman@electric-cloud.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox