bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/20321] Segmentation fault with plugin


From: wdijkstr at arm dot com
Subject: [Bug ld/20321] Segmentation fault with plugin
Date: Tue, 05 Jul 2016 11:26:43 +0000

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

Wilco <wdijkstr at arm dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wdijkstr at arm dot com

--- Comment #4 from Wilco <wdijkstr at arm dot com> ---
(In reply to address@hidden from comment #2)
> The master branch has been updated by H.J. Lu <address@hidden>:
> 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=c3e1c28ebfdb20ff4498bcc792228283b903d393
> 
> commit c3e1c28ebfdb20ff4498bcc792228283b903d393
> Author: H.J. Lu <address@hidden>
> Date:   Mon Jul 4 08:55:04 2016 -0700
> 
>     Warn and return for duplicated plugin
>     
>     If a plugin has been loaded already, we should warn and return, instead
>     of adding it on the plugin list.
>     
>       PR ld/20321
>       * plugin.c (plugin_opt_plugin): Warn and return if plugin has
>       been loaded already.
>       * testsuite/ld-plugin/lto.exp: Run PR ld/20321 test.
>       * testsuite/ld-plugin/pr20321.c: New file.

This new test fails on AArch64 with an assertion:

collect2: error: ld terminated with signal 6 [Aborted]
collect-ld: ../../src/lto-plugin/lto-plugin.c:621: all_symbols_read_handler:
Assertion `lto_wrapper_argv' failed.
collect2: error: ld terminated with signal 6 [Aborted]
collect-ld: ../../src/lto-plugin/lto-plugin.c:621: all_symbols_read_handler:
Assertion `lto_wrapper_argv' failed.
returned with: <collect2: error: ld terminated with signal 6 [Aborted]
collect-ld: ../../src/lto-plugin/lto-plugin.c:621: all_symbols_read_handler:
Assertion `lto_wrapper_argv' failed.>, expected: <.*: duplicated plugin>

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]