From: Michael Mueller <m.mueller99@kay-mueller.de>
To: Mark Kettenis <kettenis@chello.nl>
Cc: m.mueller99@kay-mueller.de, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: patch 1 for Sun C compiled target programs
Date: Mon, 12 Jul 2004 10:25:00 -0000 [thread overview]
Message-ID: <40F266FD.2080804@kay-mueller.de> (raw)
In-Reply-To: <200407102105.i6AL5xJr013149@elgar.kettenis.dyndns.org>
Mark Kettenis wrote:
> Date: Mon, 21 Jun 2004 15:09:19 +0200
> From: Michael Mueller <m.mueller99@kay-mueller.de>
>
> >
> > I'll try to get this fixed before the 6.2 release. Thanks for giving
> > me a bit more ammunition for getting this change accepted by the rest
> > of the crowd.
>
> Sounds promising. I filed PR gdb/1682 to remind you guys :-)
>
> Can you test the attached patch for me? I don't have access to a
> machine with a Sun compiler. This patch should fix your problems
> while keeping the current behaviour with GCC.
This works fine.
Michael
prev parent reply other threads:[~2004-07-12 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 17:58 Michael Mueller
2004-06-18 21:47 ` Mark Kettenis
2004-06-18 23:27 ` Daniel Jacobowitz
2004-06-21 13:09 ` Michael Mueller
2004-07-10 21:06 ` Mark Kettenis
2004-07-12 10:25 ` 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=40F266FD.2080804@kay-mueller.de \
--to=m.mueller99@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