From: Jim Ingham <jingham@apple.com>
To: gdb@sources.redhat.com
Subject: Re: filtering of commands during async operation
Date: Thu, 06 Nov 2003 21:16:00 -0000 [thread overview]
Message-ID: <705570EE-109E-11D8-ABD7-000A277A8808@apple.com> (raw)
In-Reply-To: <16298.41984.648877.777117@localhost.redhat.com>
Elena,
On Nov 6, 2003, at 11:41 AM, Elena Zannoni wrote:
> Jim Ingham writes:
>> The all the targets we support in Apple's version of gdb are async -
>> including the Mach-O native target. It took a bunch of mucking around
>> to get it working (and to get things like commands that run the target
>> working). And I am pretty sure that I broke the remote async in the
>> process, however, there were a couple of hacks in there (marked as
>> such
>> in the code) that messed us up and I didn't have the patience at the
>> time to make both work...
>>
>> So I would need to do some clean-up before our code would be ready for
>> submission, but as a proof of concept it might be useful to folks, and
>> in our system it works pretty well.
>>
>
> It seems to have become some kind of a pattern that somebody other
> than Apple is going to merge Apple's changes with the FSF mainline. Is
> there any way to get another snapshot/tarball (like it was done in Dec
> 2001)? Maybe somebody will volunteer, even though this approach is
> suboptimal.
>
We had one brief period where we got a little time to try merging
sources, but that passed without much result, and I don't see us
getting another chance in the near future.
The last time we did a tarball drop it meant that Adam ended up wasting
time merging old ObjC code into the TOT gdb - work which we had already
done on our branch. It would be great not to do that again...
Jim
> elena
>
>
>
>> Jim
>>
>> On Nov 6, 2003, at 6:32 AM, gdb-digest-help@sources.redhat.com wrote:
>>
>>> Whoops. I agree, this is screwed up. I'll just make the fix now, no
>>> need to file a bug report. I am curious, did somebody get async
>>> native to work? So far there is only the remote async target. I do
>>> remember testing this, back 4 years ago, maybe the logic got turned
>>> around at some point.
>>>
>>>
>> _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
>> Jim Ingham
>> jingham@apple.com
>> Developer Tools - gdb
>>
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham
jingham@apple.com
Developer Tools - gdb
next prev parent reply other threads:[~2003-11-06 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1068129153.32379.ezmlm@sources.redhat.com>
2003-11-06 17:38 ` Jim Ingham
2003-11-06 19:41 ` Elena Zannoni
2003-11-06 21:16 ` Jim Ingham [this message]
2003-11-06 22:10 ` Andrew Cagney
2003-11-06 22:29 ` Elena Zannoni
2003-11-06 22:26 ` Elena Zannoni
2003-11-07 16:00 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-07 16:14 ` Daniel Jacobowitz
2003-11-07 17:03 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 14:32 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-06 16:57 ` Elena Zannoni
2003-11-05 21:11 Newman, Mark (N-Superior Technical Resource Inc)
2003-11-05 21:52 ` Doug Evans
2003-11-05 22:00 ` Grant Edwards
2003-11-05 22:10 ` Paul Koning
2003-11-05 23:11 ` Elena Zannoni
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=705570EE-109E-11D8-ABD7-000A277A8808@apple.com \
--to=jingham@apple.com \
--cc=gdb@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