This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

binutils bug-tracker [was Re: coff-h8300 ld segfault]

From: Alan Modra <amodra at bigpond dot net dot au>
To: Max Bowsher <maxb at ukf dot net>
Cc: binutils at sources dot redhat dot com, gcc at gcc dot gnu dot org
Date: Wed, 4 Dec 2002 11:11:10 +1030
Subject: binutils bug-tracker [was Re: coff-h8300 ld segfault]
References: <003d01c29a3f$5ee72920$78d96f83@pomello> <20021202222817.GJ27956@bubble.sa.bigpond.net.au> <023901c29b0d$811ac2d0$78d96f83@pomello> <20021203231634.GY27956@bubble.sa.bigpond.net.au> <003601c29b28$fc3b5860$78d96f83@pomello>

On Wed, Dec 04, 2002 at 12:06:25AM -0000, Max Bowsher wrote:
> I'm happy with the workaround, but is there anything I should do to prevent
> this bug from being forgotten?

Agitate for a binutils bug-tracking system, perhaps.  :)

It would be really, really, nice if someone with the requisite skills
could set one up.  Hmm, perhaps binutils could even use gcc's existing
bug-tracker.  About all you'd need to do is add a "binutils" category.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

Follow-Ups:
- Re: binutils bug-tracker [was Re: coff-h8300 ld segfault]
  - From: Daniel Jacobowitz

References:
- coff-h8300 ld segfault
  - From: Max Bowsher
- Re: coff-h8300 ld segfault
  - From: Alan Modra
- Re: coff-h8300 ld segfault
  - From: Max Bowsher
- Re: coff-h8300 ld segfault
  - From: Alan Modra
- Re: coff-h8300 ld segfault
  - From: Max Bowsher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]