[Bug binutils/22609] Segmentation Fault

[nickc at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=22609

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |nickc at redhat dot com
         Resolution|---                         |MOVED

--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Hi Google-Autofuzz Team,

  Thank you for reporting this problem.  Unfortunately the problem you
  found is in the libiberty library which is officially part of the GCC
  project and not the binutils project.  (The binutils project makes use 
  of the libiberty library, but it does not own it).  Therefore, please
  could you report this problem on the GCC bugzilla system here:

https://gcc.gnu.org/bugzilla/enter_bug.cgi?product=gcc

  I should note however that the GCC team may report that the bug has
  already been fixed.  If this does happen then the problem is that the
  binutils libiberty sources are out of sync with the gcc libiberty 
  sources.  This does happen occasionally, and if this is the case, 
  please let me know and I will take care of it immediately.

Cheers
  Nick Clifton

PS.  I tried to reproduce the problem using the steps that you outlined,
  but the process failed here:

docker build --no-cache /path/to/project`

  This reported the error message:

unable to prepare context: unable to evaluate symlinks in Dockerfile path:
lstat /home/nickc/Downloads/project/Dockerfile: no such file or directory

  I found that it was necessary to rename the dockerfile image from
  Dockerfile.binutils to Dockerfile in order to continue.

  The build still failed but this time with:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the
docker daemon running?

  I assume that this is because I am not set up properly to run docker
  builds...

-- 
You are receiving this mail because:
You are on the CC list for the bug.