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: Tue, 22 Jun 2010 22:16:00 -0000 [thread overview]
Message-ID: <4C213637.7000500@electric-cloud.com> (raw)
In-Reply-To: <4C2109B4.8070708@electric-cloud.com>
Even dbx has trouble with it; this may be more of a Solaris issue than a
gdb one. This is running the debugger on the same machine as the core
dump, and it still has issues:
solx2-ea2% /net/tools/solstudio/12.2/i686_SunOS.5.10/bin/dbx
/net/chronic2nas/emake-slothman-main/out/i686_SunOS_64.5.10/ecloud/agent/ecagent
/net/chronic2nas/emake-slothman-main/logs-201006211902-solx2-ea2/core
Reading ecagent
dbx: internal warning: writable memory segment 0x597000[28672] of size 0
in core
dbx: internal warning: writable memory segment 0x59e000[3600384] of size
0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffd405000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffd602000[12288]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffd801000[12288]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffda00000[12288]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffdbff000[12288]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffde00000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffdfff000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe1f8000[28672]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe431000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe450000[65536]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe470000[65536]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe490000[65536]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe4b0000[65536]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe4f1000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe500000[65536]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe58a000[16384]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe58e000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe5a3000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe5e3000[24576]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe5e9000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe7e2000[49152]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe7ee000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe803000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe830000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe835000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe850000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe857000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe870000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe879000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe890000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe892000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe8c0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe8c9000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe8e0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe8e4000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe950000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe95e000[12288]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe961000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe970000[65536]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe9ac000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe9c0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe9c8000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe9c9000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffe9e1000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffea40000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffea43000[16384]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffeb90000[24576]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffeb9a000[36864]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffeba3000[16384]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffebc0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffebcd000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffec30000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffec36000[24576]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffed51000[40960]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffed5b000[77824]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffee60000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffee6b000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffee80000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffee88000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffef40000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffef46000[16384]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffef4a000[36864]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffef70000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffef7f000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffefb0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7ffefb4000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff100000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff10c000[57344]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff11a000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff290000[4096]
of size 0 in core
dbx: internal warning: writable memory segment
0xfffffd7fff29a000[151552] of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff2bf000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff320000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff329000[28672]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff390000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff39c000[12288]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff3b0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff3ed000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff3f0000[4096]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff3fb000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fff3fd000[8192]
of size 0 in core
dbx: internal warning: writable memory segment 0xfffffd7fffdfa000[24576]
of size 0 in core
core file header read successfully
Reading ld.so.1
dbx: core file read error: address 0xfffffd7fff3fb000 not available
dbx: core file read error: address 0xfffffd7fff3fbae0 not available
dbx: core file read error: address 0x598ff0 not available
dbx: warning: Dbx could not initialize rtld_db
Make sure this is the same version of Solaris where the core dump
originated.
Use `help core mismatch' for more info.
(l@1) terminated by signal SEGV (no mapping at the fault address)
0xffffffffffffffff: <bad address 0xffffffffffffffff>
(dbx) where
[1] 0xfffffd7ffeac431c(0x0, 0x0, 0x784120, 0x170, 0x7, 0xffffffff),
at 0xfffffd7ffeac431c
(dbx) threads
dbx: thread related commands not available
next prev parent reply other threads:[~2010-06-22 22:16 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 [this message]
2010-06-25 17:03 ` Max Kaehn
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=4C213637.7000500@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