From: Mark Kettenis <kettenis@chello.nl>
To: m.mueller99@kay-mueller.de
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb for Sun compiled target programs
Date: Wed, 16 Jun 2004 07:09:00 -0000 [thread overview]
Message-ID: <200406160709.i5G79Efn000675@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <40CFE463.4010000@kay-mueller.de> (message from Michael Mueller on Wed, 16 Jun 2004 08:10:43 +0200)
Date: Wed, 16 Jun 2004 08:10:43 +0200
From: Michael Mueller <m.mueller99@kay-mueller.de>
I found that gdb 6.1 is almost unusable for Sun Solaris SPARC 32/64 bit
if the target program is compiled using a Sun C compiler. ( gdb/1669:
"64-bit Solaris does not work" is just one of the problems).
It should be usable for 32-bit. 64-bit has a problem. The Sun C
compiler generates stabs debugging info by default. GDB doesn't
handle 64-bit stabs correctly. Fixing that is non-trivial. I believe
recent versions of the Sun C compiler can also generate DWARF2. That
should work better.
Can someone tell me what the status and planned future of this platform
is? (gdb/MAINTAINERS calls it "(devolved)")
It's meant to be fully supported.
I have put in some effort and fixed the most urgent problems so that
it's usable for me now. My knowledge of gdb source code is quite limited
however (just 2 weeks old) and some of the fixes definitely will need
some more work, which I would be willing to do with some help.
Does it make sense that I send my changes to gdb-patches?
Sure. If it's a substantial contribution you'd need to assign
copyright to the FSF.
next prev parent reply other threads:[~2004-06-16 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 6:11 Michael Mueller
2004-06-16 7:09 ` Mark Kettenis [this message]
2004-06-16 17:12 ` Michael Mueller
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=200406160709.i5G79Efn000675@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=m.mueller99@kay-mueller.de \
/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