This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/48384] lto, linker-plugin and optimization clutter the stack trace
- From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 31 Mar 2011 11:05:53 +0000
- Subject: [Bug lto/48384] lto, linker-plugin and optimization clutter the stack trace
- Auto-submitted: auto-generated
- References: <bug-48384-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48384
--- Comment #4 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2011-03-31 11:05:47 UTC ---
its' a gold effect!
with
ld -v
GNU ld (GNU Binutils) 2.21
things are fine
(gdb) run
Starting program: /afs/cern.ch/user/i/innocent/public/ctest/lto/t_hlto
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7dfc78d in go(int, int const*) () from ./libfoo_hlto.so
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.7.el6_0.4.x86_64
(gdb) where
#0 0x00007ffff7dfc78d in go(int, int const*) () from ./libfoo_hlto.so
#1 0x000000000040050d in main ()
I will stick to " bfd ld" for the time being.
not sure on which side should be
gold + gcc-lto-plugin
debug.
gold is written in c++ which may mean that bootstrap in the installation is
needed
thanks for the fast feed back,
vincenzo
On 31 Mar, 2011, at 12:43 PM, rguenth at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48384
>
> --- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-31 10:43:49 UTC ---
> (In reply to comment #2)
>> Thanks,
>> at least on some system it seems to behave correclty.
>> I had to rebuild binutil to enable the plugin and something may have gone wrong
>> are you using standard bfd "ld" or gold?
>
> I'm using standard bfd ld, version 2.21.
>
> Richard.
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.