From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-46800-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 17668 invoked by alias); 9 Feb 2019 01:28:31 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 17655 invoked by uid 89); 9 Feb 2019 01:28:30 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=recall, H*c:alternative, offer
X-HELO: mail-it1-f179.google.com
Received: from mail-it1-f179.google.com (HELO mail-it1-f179.google.com) (209.85.166.179) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 09 Feb 2019 01:28:27 +0000
Received: by mail-it1-f179.google.com with SMTP id a6so13722165itl.4        for <gdb@sourceware.org>; Fri, 08 Feb 2019 17:28:27 -0800 (PST)
MIME-Version: 1.0
From: Brian Vandenberg <phantall@gmail.com>
Date: Sat, 09 Feb 2019 01:28:00 -0000
Message-ID: <CAEJ-0i_OV1nFpd7wFxKr0bo5Whc_kJO9AKXiXvPog9j8nPKm_Q@mail.gmail.com>
Subject: Re: GDB is broken on systems with readline built without -fexceptions
To: gdb@sourceware.org, Pedro Alves <palves@redhat.com>
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2019-02/txt/msg00008.txt.bz2

>
> 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