From: Tomasz Grobelny <tomasz@grobelny.oswiecenia.net>
To: <gdb@sourceware.org>
Subject: sun compiler and gdb
Date: Thu, 03 May 2012 03:23:00 -0000 [thread overview]
Message-ID: <25b0084e43f4d35410c8dff55a3be61d@192.168.5.248> (raw)
Hi all,
Should it be possible to debug C++ programs compiled using sun compiler
using GDB? If so which debug format should I use? Which versions of the
compiler/gdb support such a scenario? Currently the situation looks like
this (which does not look very promising):
> /opt/solstudio12.2/bin/CC -V
CC: Sun C++ 5.11 SunOS_i386 2010/08/13
usage: CC [ options ] files. Use 'CC -flags' for details
> /opt/solstudio12.2/bin/CC -g -xdebugformat=dwarf test.cpp
> gdb -q ./a.out
Reading symbols from /full/path/to/my/a.out...done.
(gdb) break fun
Dwarf Error: Cannot find DIE at 0x0 referenced from DIE at 0x13b33 [in
module /full/path/to/my/a.out]
(gdb) break main
Dwarf Error: Cannot find DIE at 0x0 referenced from DIE at 0x13b33 [in
module /full/path/to/my/a.out]
(gdb) run
Starting program: /full/path/to/my/a.out
[Thread debugging using libthread_db enabled]
hello world
[Inferior 1 (process 9412 ) exited normally]
(gdb) quit
> uname -a
SunOS solac1 5.10 Generic_137138-09 i86pc i386 i86pc
>
gdb version is 7.4.1
Any ideas what is wrong here?
--
Regards,
Tomasz Grobelny
next reply other threads:[~2012-05-03 3:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 3:23 Tomasz Grobelny [this message]
2012-05-03 6:50 ` Sergio Durigan Junior
2012-05-03 14:00 ` Tomasz Grobelny
2012-05-09 20:31 ` Tom Tromey
2012-05-09 22:58 ` Tomasz Grobelny
2012-05-09 23:23 ` Tomasz Grobelny
2012-05-10 13:34 ` Tom Tromey
2012-05-10 16:38 ` Tomasz Grobelny
2012-05-10 17:38 ` Tomasz Grobelny
2012-05-10 20:34 ` Tom Tromey
2012-05-10 20:39 ` Tom Tromey
2012-05-10 22:08 ` Tomasz Grobelny
2012-05-11 16:21 ` Tom Tromey
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=25b0084e43f4d35410c8dff55a3be61d@192.168.5.248 \
--to=tomasz@grobelny.oswiecenia.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).