From: Stan Shebs <shebs@apple.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Unfinished projects
Date: Thu, 14 Apr 2005 22:03:00 -0000 [thread overview]
Message-ID: <425EE89D.2020601@apple.com> (raw)
In-Reply-To: <20050414190123.GA18019@nevyn.them.org>
Daniel Jacobowitz wrote:
>On Thu, Apr 14, 2005 at 11:55:11AM -0700, Stan Shebs wrote:
>
>>Andrew's sudden departure from GDB maintenance seems to left a
>>large number of projects in mid-process; as I'm picking through
>>the latest sources trying to figure out how to merge with Apple's
>>bits, it's very confusing as to how the new way is supposed to
>>work when it's not documented anywhere and there's maybe only
>>one example of a configuration using it.
>>
>>So my question is - what should we do about all these? Are
>>some of these intrinsically impossible to complete without
>>the right collection of hardware? If so, then maybe we need
>>to get tougher about dropping support for some targets, or
>>else abandon the projected change. I'd like to work on updating
>>the GDB internals manual too, for my own understanding if
>>nothing else; should I describe old ways, new ways, or both?
>>
>
>Could you give some specific examples that you're looking at? I've got
>no way to answer your questions without more details. For each one,
>there's probably someone on the list who knows how it's supposed to
>work.
>
I was being purposefully vague because I wanted to think about
general strategy, and because I don't even know how many there
are. Specific things I've noticed include async for native, the
infptrace vs inf-ptrace situation, and then there's everything
with "deprecated" somewhere in the name.
So that would be a start - what are all the main incomplete
transitions in the code right now?
Stan
next prev parent reply other threads:[~2005-04-14 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 18:55 Stan Shebs
2005-04-14 19:01 ` Daniel Jacobowitz
2005-04-14 22:03 ` Stan Shebs [this message]
2005-04-14 21:49 ` Mark Kettenis
2005-04-15 1:48 ` Russell Shaw
2005-04-15 9:04 ` Eli Zaretskii
2005-04-15 8:50 ` Eli Zaretskii
2005-04-15 17:47 ` Andrew Cagney
2005-04-15 18:37 ` Stan Shebs
2005-04-15 18:52 ` Alain Magloire
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=425EE89D.2020601@apple.com \
--to=shebs@apple.com \
--cc=drow@false.org \
--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