public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug compile/29484] gdb 12.1 fails to build on xtensa: undefined reference to `xtensa_tdep'
Date: Sun, 14 Aug 2022 01:55:22 +0000 [thread overview]
Message-ID: <bug-29484-4717-q0wl48QRRs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29484-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29484
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
I tried to reproduce (using the xtensa-lx60--uclibc--bleeding-edge-2021.11-1
toolchain), but I get these errors:
dwarf2/index-write.o: in function `std::vector<unsigned char,
gdb::default_init_allocator<unsigned char, std::allocator<unsigned char> >
>::resize(unsigned int)':
/home/simark/Downloads/xtensa-lx60--uclibc--bleeding-edge-2021.11-1/xtensa-buildroot-linux-uclibc/include/c++/11.2.0/bits/stl_vector.h:940:(.text+0x405):
dangerous relocation: call8: call target
out of range:
_ZNSt6vectorIhN3gdb22default_init_allocatorIhSaIhEEEE17_M_default_appendEj
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-14 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 20:13 [Bug compile/29484] New: " thomas.petazzoni at bootlin dot com
2022-08-13 20:15 ` [Bug compile/29484] " thomas.petazzoni at bootlin dot com
2022-08-14 1:55 ` simark at simark dot ca [this message]
2022-08-14 7:50 ` thomas.petazzoni at bootlin dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29484-4717-q0wl48QRRs@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).