From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Björn Schäpers" <gcc@hazardy.de>
Cc: libstdc++@gcc.gnu.org
Subject: Re: <stacktrace> on windows
Date: Thu, 24 Nov 2022 21:52:10 +0000 [thread overview]
Message-ID: <CAH6eHdQXWq+LG5gxvS+D689VxibVHAgCEcvAAECk=Qg=7kc9cg@mail.gmail.com> (raw)
In-Reply-To: <d8403b14-1d36-c71b-ba48-b1f68590a11a@hazardy.de>
On Thu, 24 Nov 2022 at 21:28, Björn Schäpers wrote:
>
> Hi there,
>
> I want to use C++23's <stacktrace> on windows (in particular msys2 MinGW), but
> had to realize that _GLIBCXX_HAVE_STACKTRACE is not defined.
>
> That I got quite easily fixed, and have my copy of libstdc++_libbacktrace.a, but
> using that segfaults immediately. There is no filename inserted into
> __glibcxx_backtrace_create_state and itself does not find one on windows, than
> the error callback is called, which is not provided (nullptr).
>
> When looking at the libbacktrace issues on github [1] I see some more possible
> problems on windows.
>
> I'm willing to work on that,
Great!
> my question is if that repository on github is
> linked in any way to the libbacktrace in gcc? Are changes from there ported to
> the gcc code? Are changes from the gcc code ported to libbacktrace on github?
> Where should I start to work?
it's the same code, and it looks like Ian keeps them synced.
prev parent reply other threads:[~2022-11-24 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 21:28 Björn Schäpers
2022-11-24 21:52 ` Jonathan Wakely [this message]
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='CAH6eHdQXWq+LG5gxvS+D689VxibVHAgCEcvAAECk=Qg=7kc9cg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@hazardy.de \
--cc=libstdc++@gcc.gnu.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).