From: Armin Diehl <diehl@nordrhein.de>
To: gdb@sources.redhat.com
Cc: "Günter Knauf" <eflash@gmx.net>,
info@herdsoft.com, RBATEMAN@novell.com, U_Neumann@gne.de
Subject: Re: Deprecate dwarf and mdebug support, delete nlm?
Date: Fri, 09 May 2003 08:10:00 -0000 [thread overview]
Message-ID: <3EBB62D0.2040607@nordrhein.de> (raw)
I think the gdbserve is a candidate for deletion. It is only needed for
netware 3.11 and prevents building gdb with netware support. I always
have to remove that dir in the configure targets file.
My gdb2ndi works with netware 4.11 also (load rdebug.nlm). If someone
needs the gdbserve for 3.11, it can be used from older versions of gdb.
(It is only a simple support for the gdb remote protocol)
But please please *do not remove* the netware support from gdb. It is
the only way to debug FreePascal nlm's.
It is further needed for debugging nlms generated by gcc. Bernd Herd has
done a great job in porting gcc with c++ support to netware and it would
be bad if we loose the debugging support as we now have a great
alternative c/c++ compiler for netware.
Günter Knauf wrote:
> Hi Andrew,
>
>>Ok, so nlm/ is a candidate (but it isn't hurting anyone, and
>
> I cant believe that you all here are talking about a ./nlm subdir of 86.3kB while the whole gdb source is more than 14MB !! And that all at times where download bandwidth isnt an issue anymore!
>
>
>>the alternative is written in FreePascal :-).
>
> that's only true for NetWare 5.1 and 6, but with previous versions we still need the gdbserver!
>
>
>>Andrew
>
>
> removing 86.3kB isnt worth to talk about! Just my 2 ct.
>
> but if you are searching for the last few bytes for deleting, just take 10,9kB and remove ./nlm/ppc.h and ./nlm/ppc.c because I dont know of any NetWare version which runs on PPC; all versions for which gdbserver is of interest run on i386!
>
> thanks, Guenter.
>
next reply other threads:[~2003-05-09 8:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 8:10 Armin Diehl [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 15:47 Michael Elizabeth Chastain
2003-05-09 16:37 ` Kean Johnston
2003-05-09 17:03 ` Andrew Cagney
2003-05-09 16:48 ` Andrew Cagney
2003-05-10 9:25 ` Eli Zaretskii
2003-05-09 15:22 Michael Elizabeth Chastain
2003-05-09 15:34 ` Kean Johnston
[not found] <200305082242.h48MgQH06975@mx1.redhat.com>
2003-05-09 0:02 ` Elena Zannoni
[not found] <E19Duaa-0005kw-00@monty-python.gnu.org>
2003-05-08 23:42 ` Andrew Cagney
2003-05-09 15:12 ` Kean Johnston
2003-05-08 23:14 Günter Knauf
2003-05-08 22:52 Ulrich Neumann
2003-05-09 0:09 ` Elena Zannoni
2003-05-08 22:42 Günter Knauf
2003-05-04 16:08 Michael Elizabeth Chastain
2003-05-05 15:23 ` Tim Combs
2003-05-05 17:30 ` Andrew Cagney
2003-05-05 17:49 ` Daniel Berlin
2003-05-04 6:10 Michael Elizabeth Chastain
2003-05-04 6:43 ` Daniel Berlin
2003-05-04 4:41 Andrew Cagney
2003-05-04 15:41 ` Daniel Jacobowitz
2003-05-04 19:52 ` Elena Zannoni
2003-05-05 17:37 ` Andrew Cagney
2003-05-05 0:14 ` Andrew Cagney
2003-05-05 3:58 ` Joel Brobecker
2003-05-05 17:24 ` Jim Blandy
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=3EBB62D0.2040607@nordrhein.de \
--to=diehl@nordrhein.de \
--cc=RBATEMAN@novell.com \
--cc=U_Neumann@gne.de \
--cc=eflash@gmx.net \
--cc=gdb@sources.redhat.com \
--cc=info@herdsoft.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).