Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Erland Lewin <erl@voxi.com>
Cc: gdb@sources.redhat.com
Subject: Re: Difficulty for community involvment in gdb
Date: Wed, 01 Aug 2001 13:10:00 -0000	[thread overview]
Message-ID: <3B686235.30809@cygnus.com> (raw)
In-Reply-To: <3B684397.40704@voxi.com>

Just FYI,


When I went to close your two bug reports the first thing I did was try 
to find the SID bug-tracking system so that I could point you at it. 
Unfortunatly that doesn't exist.  Looking at the e-mail exchange it 
would appear you were unfortunatly given the impression that this was a 
GDB problem which it isn't, sigh.

>    It is now possible to automatically configure and build a variety of
>   tools with one command.  To build all of the tools contained herein,
>   run the ``configure'' script here, e.g.:

I'll try to clarify the comment in that file.


One thing that would help though.  What lead you to check out both SID 
and GDB in a single source tree?  I'm guessing that this is documented 
somewhere and hence, would like to locate that documentation so that 
those responsible can be informed of the problems you encountered.

> So to a newcomer to this stuff, it would seem that bdf, sid etc are
>    "part of gdb". It's quite difficult to get started with the cvs.
>     Additionally, the gnats interface is IMHO not as good as bugzilla.
>    The only thing I can do, not being a developer, seems to be to
>    create bug reports; I can't add comments to them.
>     I think little problems like the ones I'm having inhibit the
>    advantage that gdb could get from greater community involvment. What
>    I'm really trying to do is to get gdb to work better with threads
>    under Linux. This has been a problem for several years (I
>    contributed a patch for this about two years ago). I think the time
>    it takes for these things to get fixed will be longer if it is more
>    difficult for people to get involved.


Regarding Linux threads, you may want to just download/build a current 
GDB.  More bugs then are worth mentioning have been fixed.

With PRMS vs Bugzilla, it is a decision we live with.  I think the time 
to review it is when GDB+BINUITLS get merged with GCC.  If you would 
like a gnats account that can be arranged.

	Andrew





	Andrew




  reply	other threads:[~2001-08-01 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 11:00 Erland Lewin
2001-08-01 13:10 ` Andrew Cagney [this message]
2001-08-02  4:36   ` Erland Lewin
2001-08-02  8:05     ` Keith Seitz
2001-08-02  9:16     ` DJ Delorie

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=3B686235.30809@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=erl@voxi.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