From: Brian Vandenberg <phantall@gmail.com>
To: gdb@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Re: GDB is broken on systems with readline built without -fexceptions
Date: Sat, 09 Feb 2019 01:28:00 -0000 [thread overview]
Message-ID: <CAEJ-0i_OV1nFpd7wFxKr0bo5Whc_kJO9AKXiXvPog9j8nPKm_Q@mail.gmail.com> (raw)
>
> On 04/21/2016 03:31 PM, Pedro Alves wrote:
> > Forgot to qualify "broken". The symptom is:
> >
> > (gdb) whatever-command-that-causes-an-error
> > terminate called after throwing an instance of
> 'gdb_exception_RETURN_MASK_ERROR'
> > Aborted
> > $
> >
> A proper fix is turning out to be more complicated than I'd hope,
> so in the mean time, to get things working again, I flipped gdb's
> TRY/CATCH mechanism back to setjmp/longjmp instead of C++ try/catch,
> again.
> You should no longer need the --enable-build-with-cxx=no workaround.
> Thanks,
> Pedro Alves
I'm still waiting for IT to get me the 8.2 source so I can try that
version, but in the meantime: I'm seeing this error in Solaris 10 (sparc)
with 8.1.1. I built gdb configured like this:
/path/to/src/configure \
--prefix=/install/path \
--enable-plugins \
--enable-tui \
--with-python=yes \
--disable-largefile \
--without-system-readline \
--enable-64-bit-bfd \
--with-expat \
--with-libexpat-prefix=/opt/csw \
--with-x \
LDFLAGS="$(echo -n -Wl,-{L,R}/opt/csw/lib)" \
{CFLAGS,CPPFLAGS,CXXFLAGS}=-isystem/opt/csw/include
I don't recall the rationale behind all of the above options. Some of them
came from how the folks at opencsw.org build GDB, others were me just
banging on it until it compiled successfully (perhaps to my own detriment).
If you can offer any suggestions I would appreciate it.
-brian
next reply other threads:[~2019-02-09 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 1:28 Brian Vandenberg [this message]
2019-02-12 19:35 ` Pedro Alves
2019-02-13 3:01 ` Joel Brobecker
-- 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=CAEJ-0i_OV1nFpd7wFxKr0bo5Whc_kJO9AKXiXvPog9j8nPKm_Q@mail.gmail.com \
--to=phantall@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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