public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: "Günter Knauf" <eflash@gmx.net>
Cc: gdb@sources.redhat.com
Subject: Re: Deprecate dwarf and mdebug support, delete nlm?
Date: Fri, 09 May 2003 00:02:00 -0000	[thread overview]
Message-ID: <16058.61783.466409.578135@localhost.redhat.com> (raw)
In-Reply-To: <200305082242.h48MgQH06975@mx1.redhat.com>

=?ISO-8859-1?Q?G=FCnter_Knauf?= writes:
 > Hi Elena,
 > > nlm... you mean nlmread.c or nlm/* ?
 > > google threw up a few things:
 > > http://home.arcor.de/armin.diehl/fpcnw/gdbnw.html (seems active, uses 5.3).
 > > http://www.herdsoft.com/ti/netware/cross/4_Debugging.html
 > > There is a gdb wrapper program now that translated netware remote
 > > protocol into gdb remote protocol and vice versa. So they are not
 > > using NLM gdbserver anymore because that supports older versins of
 > > netware only.
 > 
 > > elena
 > 
 > please dont do that!! We still need the NLM gdbserver; 
 > a few NetWare developers (including me) started about 4 years ago with 
 > developing NLMs with gcc/nlmconv, and also we use the gdbserver. I know
 > both of the above mentioned developers and I'm in contact with them;
 > and if we really dont need the gdbserver anymore we will post here...
 > but until then please dont drop the NLM support!
 > thanks, Guenter.
 > 

Ah, there is life out there, then! :-) This is good news. Let me
explain: the problem we are facing is that gdb is moving forward,
while a few pieces, like nlm, mdebug support, etc, seem to languish
behind, and don't get modernized as the rest of gdb.  It is becoming
harder and harder to keep them integrated with the rest of the
debugger, mostly because people don't have a way to even test them.

Given that there is active development in this area, I strongly
encourage you and the other Netware developers to become an active
part of the gdb community, and bring the parts you work on more in
tune with the rest of the debugger. We will all benefit from such an
approach.

Are you guys willing to do that? If so, please, make sure you have
copyright assignments in place ahead of time.

TIA
Elena

       reply	other threads:[~2003-05-09  0:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200305082242.h48MgQH06975@mx1.redhat.com>
2003-05-09  0:02 ` Elena Zannoni [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 15:22 Michael Elizabeth Chastain
2003-05-09 15:34 ` Kean Johnston
2003-05-09  8:10 Armin Diehl
     [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=16058.61783.466409.578135@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=eflash@gmx.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).