From: Michael Mueller <michael.mueller@kay-mueller.de>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb for Sun compiled target programs
Date: Wed, 16 Jun 2004 17:12:00 -0000 [thread overview]
Message-ID: <40D07F5D.6080202@kay-mueller.de> (raw)
In-Reply-To: <200406160709.i5G79Efn000675@elgar.kettenis.dyndns.org>
> 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'm surprised. I have a 64-bit gdb that seems to work with Sun C 5.4. It
only has a couple of minor patches. I will send them one after the
other. I have been debugging my 64-bit gdb with itself.
> 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.
Just done.
--
=== Michael Mueller ==================
Tel. + 49 8171 63600
Fax. + 49 8171 63615
Web: http://www.mm.kay-mueller.de
http://www.planets.kay-mueller.de
======================================
prev parent reply other threads:[~2004-06-16 17:12 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
2004-06-16 17:12 ` Michael Mueller [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=40D07F5D.6080202@kay-mueller.de \
--to=michael.mueller@kay-mueller.de \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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