gcc-{ar,nm,ranlib} segfault when run with full path (confirmed)

[Pierre Labastie]

See ​http://lists.linuxfromscratch.org/pipermail/lfs-dev/2018-January/072002.html, and ​https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81829. But nobody has confirmed yet for BLFS...

[Pierre Labastie]

confirmed in chroot on a Sys V system built in November.

[bdubbs@…]

On a relatively recent build, (started Jan 6), I cannot confirm. I ran gdb --args /usr/bin/gcc-ar with no problem.

I do not think we should be concerned with the problem in chroot. That is, by definition, a limited environment.

In addition, I expect a new release of gcc soon:

​https://gcc.gnu.org/ml/gcc/2018-01/msg00115.html

Let's wait and if that does happen, this will be marked over come by events.

[Pierre Labastie]

So I booted the same system as in comment:1. Here are the outputs of two commands:

pierre [ ~ ]$ gcc-ar
Usage: /usr/bin/ar [emulation options] [-]{dmpqrstx}[abcDfilMNoPsSTuvV] [--plugin <name>] [member-name] [count] archive-file file...
       /usr/bin/ar -M [<mri-script]
 commands:
  d            - delete file(s) from the archive
[...]
pierre [ ~ ]$ /usr/bin/gcc-ar
Segmentation fault

I agree it can wait for a new version of gcc. But I am amazed you do not see the segfault. BTW, I have not tried:

pierre [ ~ ]$ /usr/bin/ar

or

pierre [ ~ ]$ ar

Maybe I should

[bdubbs@…]

I have a test LFS build using gcc-7.3.0. I cannot duplicate the problem with any of gcc-{ar,nm,ranlib}.

Marking overcomebyevents in favor of ticket #10305.