Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Brian Vandenberg <phantall@gmail.com>, gdb@sourceware.org
Subject: Re: GDB is broken on systems with readline built without -fexceptions
Date: Wed, 13 Feb 2019 03:01:00 -0000	[thread overview]
Message-ID: <20190213030055.GH17730@adacore.com> (raw)
In-Reply-To: <d7bd4451-d708-e851-6117-42d185fc3613@redhat.com>

> I'd suspect that this happens because GDB is built/linked with
> "-static-libstdc++ -static-libgcc", and that doesn't work
> correctly on Solaris.  ISTR that we observed that on other
> ports as well.

Indeed. It was on AIX, I believe.

-- 
Joel


  reply	other threads:[~2019-02-13  3:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09  1:28 Brian Vandenberg
2019-02-12 19:35 ` Pedro Alves
2019-02-13  3:01   ` Joel Brobecker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-21 14:28 Pedro Alves
2016-04-21 14:31 ` Pedro Alves
2016-04-21 16:32   ` Pedro Alves

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=20190213030055.GH17730@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=phantall@gmail.com \
    /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