Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: krokus <nomadbyte@gmail.com>
To: gdb@sourceware.org
Subject: Re: Building gdb-9.1 on OSX: gdb's exceptions are not getting caught
Date: Tue, 14 Apr 2020 20:48:35 -0500	[thread overview]
Message-ID: <CAMCMYR6EaY2JWR0bA5k7GMXYtoq28m02YeCvB4Wn1-wG4qxDKA@mail.gmail.com> (raw)
In-Reply-To: <05B3AEF0-54D0-408F-97A4-19B2F3918611@comcast.net>

Paul,
I tried to build with your configure flags; So far the same result, it does
not catch the exceptions. I'm puzzled.

Could you please run the test below to see which compiler and link flags
are being active during clang complie and link?
It should run clang in verbose mode and will show the flags and include/lib
paths
I will try to match your compile/link flags with my clang-8.0.

TEST:
```
echo "int main() {return 0;}" > /tmp/x.cc  && clang++ -v -Wl,-v /tmp/x.cc
-o /dev/null && rm /tmp/x.cc
```
Thanks!


      parent reply	other threads:[~2020-04-15  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 20:23 krokus
2020-04-14 20:27 ` Paul Koning
2020-04-14 21:59   ` krokus
     [not found]     ` <05B3AEF0-54D0-408F-97A4-19B2F3918611@comcast.net>
2020-04-15  1:48       ` krokus [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=CAMCMYR6EaY2JWR0bA5k7GMXYtoq28m02YeCvB4Wn1-wG4qxDKA@mail.gmail.com \
    --to=nomadbyte@gmail.com \
    --cc=gdb@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