From: Michael Snyder <msnyder@redhat.com>
To: Adam Fedor <fedor@doc.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] Trivialize objc-lang.c FETCH_ARGUMENT
Date: Wed, 23 Apr 2003 01:41:00 -0000 [thread overview]
Message-ID: <3EA5EF33.5EC2F8CE@redhat.com> (raw)
In-Reply-To: <3EA55625.4020107@doc.com>
Adam Fedor wrote:
>
> Well, I thought I'd at least try to see if this patch would be ok. Here
> I replace the arcitecture dependant FETCH_ARGUMENT with a trivial
> implementation that does nothing. This would allow objc-lang.o to be
> linked into gdb and I commit most or all of the remaining Objective-C
> patches. Then I could work on fixing FETCH_ARGUMENT at my leasure...
That seems reasonable. By the way, if there's been an ongoing discussion,
I haven't followed it. Why is it that you need to do this in an
architecture-dependent way? GDB should have enough debug info to
do this cleanly, shouldn't it?
next prev parent reply other threads:[~2003-04-23 1:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 14:48 Adam Fedor
2003-04-23 1:41 ` Michael Snyder [this message]
2003-04-23 2:09 ` Adam Fedor
2003-04-23 2:00 ` Adam Fedor
2003-04-23 2:06 ` Michael Snyder
2003-04-23 14:08 ` Daniel Jacobowitz
2003-04-23 3:07 ` Adam Fedor
2003-04-23 8:32 ` Adam Fedor
2003-04-25 3:21 ` Andrew Cagney
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=3EA5EF33.5EC2F8CE@redhat.com \
--to=msnyder@redhat.com \
--cc=fedor@doc.com \
--cc=gdb-patches@sources.redhat.com \
/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