X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs Date: Tue, 10 Jul 2001 12:51:22 +0200 (MET DST) From: Hans-Bernhard Broeker X-Sender: broeker AT acp3bf To: Eli Zaretskii cc: djgpp-workers AT delorie DOT com Subject: Re: bfdsymify In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 10 Jul 2001, Eli Zaretskii wrote: > > On Mon, 9 Jul 2001, Hans-Bernhard Broeker wrote: > > > But what about submitting it to GDB? It is a kind of debugger, after all. > > And GDB comes with bfd, too, so there'd always be one available for > > building bfdsymify. > > This approach still requires to come up with a portable program. Would it, really? > Otherwise, I find it hard to believe that GDB maintainers will accept > it. I once tried to put into the distribution a bunch of > DJGPP-specific files to make the test suite usable for the DJGPP port, > but couldn't convince the maintainers to agree to that. bsdsymify would be different, I think; it'd not be modifying existing machinery, putting an additional maintenance burden upon GDB maintainers to avoid breaking it, or other platforms, as they work on the code for unrelated reasons. I'm thinking more along the lines of having bfdsymify a largely separate program, much like the CPU simulators that are currently part of GDB already, or the 'utils/msdos' subdirectory. (bfd)symify is utterly unportable by design, AFAICS --- on just about no platform other than DOS a non-privileged user is allowed to perform direct reads of screen contents. Nor would there usually be anything interesting to read from it, to begin with. So I hardly think it makes much sense to try porting it to other platforms. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.