From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: i.nixman@autistici.org
Cc: Gcc Help <gcc-help@gcc.gnu.org>
Subject: Re: Extra import symbol in debug build
Date: Thu, 16 Feb 2023 15:29:55 +0000 [thread overview]
Message-ID: <CAH6eHdQOYGb-6howMCktoACsq-50Zr63pBzWx7yoUa0ngf2eaA@mail.gmail.com> (raw)
In-Reply-To: <4f36cb6cb8e444073e1a9e253e861920@autistici.org>
On Thu, 16 Feb 2023 at 15:25, i.nixman--- via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> hello,
>
>
> I can successfully build the same C++ code using GCC-8.3.1 for Debug (-g
> -O0) and Release (-g -O2) build.
> I can successfully debug the Release-executable on a remote host, but I
> can't debug the Debug-executable on a remote host, because the
> Debug-executable imports an extra symbol
> _ZNKSt9basic_iosIcSt11char_traitsIcEEcvbEv from libstdc++ which doesn't
> exist.
It should exist, it has been there since GCC 5.
>
> but I don't want to debug libstdc++, so I think I shouldn't install
> additional debug version of libstdc++.
>
> it looks like a bug, or am I wrong?
>
> another my question is, what should I do to get rid of that extra symbol
> in Debug build?
>
>
>
>
> best!
>
> ps
> I can't update GCC nor libstdc++.
next prev parent reply other threads:[~2023-02-16 15:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:23 i.nixman
2023-02-16 15:29 ` Jonathan Wakely [this message]
2023-02-16 18:39 ` i.nixman
2023-02-16 20:08 ` Jonathan Wakely
2023-02-17 8:51 ` i.nixman
2023-02-17 10:23 ` Xi Ruoyao
2023-02-17 11:31 ` i.nixman
2023-02-17 11:26 ` Jonathan Wakely
2023-02-17 11:32 ` i.nixman
2023-02-17 12:06 ` Jonathan Wakely
2023-02-17 14:59 ` i.nixman
2023-02-17 15:18 ` i.nixman
2023-02-17 15:30 ` Jonathan Wakely
2023-02-17 15:35 ` i.nixman
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=CAH6eHdQOYGb-6howMCktoACsq-50Zr63pBzWx7yoUa0ngf2eaA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=i.nixman@autistici.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).