Re: gnu ld 2.12 segmentation fault on Solaris 2.8

[Nick Clifton]

Hi Miles,

> >    To enable us to fix the bug, you should include all these things:
> ...
> >      Making them available for anonymous FTP is not as good, but may
> >      be the only reasonable choice for large object files.
> 
> I wonder if this sort of advice (that `anonymous FTP is not as good') is
> outdated -- I think it's very rare for a developer to have email, but not
> some sort of net-connectivity (at least http access).
> 
> I suppose it's often rather inconvenient to arrange for a file to be
> accessible from the outside world, if you're behind a firewall or something,
> but it's also quite simple to just say `I have the file, and can send it to
> anyone who asks.'
> 
> Perhaps it should also be a bit more explicit about how big is too big to
> send directly.
> 
> > I did not realize, because the info file did not say, that the files
> > would be going to a mailing list.
> 
> Maybe the info file should explicitly mention the possibility that it is so.
> [actually, bug-binutils is forwarded to the general GNU bug list,
> bug-gnu-utils, which is quite widely read, I believe.]
> 
> Does anyone have any thoughts about this (am I the only one using a slow
> modem link)?

Your suggestions seem reasonable to me. What do you think of this
rewording ?  (10K was an arbitrary guess for a reasonably small size for
object files).

Cheers
        Nick


Index: ld/ld.texinfo
===================================================================
RCS file: /cvs/src/src/ld/ld.texinfo,v
retrieving revision 1.69
diff -c -3 -p -w -r1.69 ld.texinfo
*** ld/ld.texinfo       22 May 2002 18:03:07 -0000      1.69
--- ld/ld.texinfo       14 Jun 2002 11:40:08 -0000
*************** and then we might not encounter the bug.
*** 4732,4741 ****
  
  @item
  A complete input file, or set of input files, that will reproduce the
! bug.  It is generally most helpful to send the actual object files,
! uuencoded if necessary to get them through the mail system.  Making them
! available for anonymous FTP is not as good, but may be the only
! reasonable choice for large object files.
  
  If the source files were assembled using @code{gas} or compiled using
  @code{gcc}, then it may be OK to send the source files rather than the
--- 4733,4745 ----
  
  @item
  A complete input file, or set of input files, that will reproduce the
! bug.  It is generally most helpful to send the actual object files
! provided that they are reasonably small.  Say no more than 10K.  For
! bigger files you can either make them available by FTP or HTTP or else
! state that you are willing to send the object file(s) to whomever
! requests them.  (Note - your email will be going to a mailing list, so
! we do not want to clog it up with large attachments).  But small
! attachments are best.
  
  If the source files were assembled using @code{gas} or compiled using
  @code{gcc}, then it may be OK to send the source files rather than the