From: David Edelsohn <dje.gcc@gmail.com>
To: Pedro Alves <palves@redhat.com>,
Nitish Kumar Mishra <mishra.nitish.88@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>, Yao Qi <qiyaoltc@gmail.com>
Subject: Re: Issue with Latest GDB on AIX with GCC-6.12
Date: Sat, 28 Jan 2017 23:56:00 -0000 [thread overview]
Message-ID: <CAGWvnyn0dfXfP8z+G0DFf4JWBZMXreetzg3+xX8_+7LYTmgw6Q@mail.gmail.com> (raw)
>>>>> Pedro Alves writes:
> Sounds like a manifestation of:
>
> Bug 60939 - AIX: exceptions not caught when calling function via pointer
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60939
>
> since ui->input_handler is a function pointer here:
>
> static void
> gdb_rl_callback_handler (char *rl) noexcept
> {
> struct gdb_exception gdb_rl_expt = exception_none;
> struct ui *ui = current_ui;
>
> TRY
> {
> ui->input_handler (rl);
> }
> CATCH (ex, RETURN_MASK_ALL)
> {
> gdb_rl_expt = ex;
> }
> END_CATCH
If the problem is throwing an exception through a function called via
pointer, then the solution should be to follow the suggestion in
comment #8 and add an appropriate incantation of
-Wl,-bkeepfile:
to the link step for GDB, something like
gdb/config/powerpc/aix.mh
MH_LDFLAGS = -Wl,-bkeepfile:event-top.o
Thanks, David
next reply other threads:[~2017-01-28 23:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 23:56 David Edelsohn [this message]
2017-01-29 1:11 ` David Edelsohn
2017-01-31 13:09 ` Pedro Alves
2017-02-07 8:05 ` Nitish Kumar Mishra
2017-02-07 10:30 ` Pedro Alves
2017-02-07 13:44 ` David Edelsohn
2017-02-07 13:57 ` Pedro Alves
2017-02-07 14:16 ` David Edelsohn
2017-02-08 6:16 ` Nitish Kumar Mishra
2017-02-08 7:04 ` Nitish Kumar Mishra
2017-02-08 12:06 ` Pedro Alves
2017-02-08 13:32 ` David Edelsohn
2017-02-09 4:51 ` Nitish Kumar Mishra
2017-02-09 12:05 ` Nitish Kumar Mishra
2017-02-09 12:15 ` Nitish Kumar Mishra
2017-02-09 15:50 ` David Edelsohn
2017-02-10 7:22 ` Nitish Kumar Mishra
2017-02-10 15:52 ` David Edelsohn
2017-02-12 21:05 ` David Edelsohn
2017-02-12 23:52 ` Pedro Alves
2017-02-13 15:02 ` David Edelsohn
2017-02-13 15:19 ` Eli Zaretskii
2017-02-13 15:38 ` Nitish Kumar Mishra
2017-02-20 11:22 ` Nitish Kumar Mishra
2017-02-20 11:25 ` Nitish Kumar Mishra
2017-02-20 11:37 ` Nitish Kumar Mishra
2017-02-21 8:01 ` Nitish Kumar Mishra
2017-02-21 14:47 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2017-01-25 10:54 Nitish Kumar Mishra
2017-01-25 11:12 ` Pedro Alves
2017-01-25 13:52 ` Pedro Alves
2017-01-25 14:01 ` Pedro Alves
2017-01-25 14:38 ` Yao Qi
2017-01-25 14:44 ` 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=CAGWvnyn0dfXfP8z+G0DFf4JWBZMXreetzg3+xX8_+7LYTmgw6Q@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gdb@sourceware.org \
--cc=mishra.nitish.88@gmail.com \
--cc=palves@redhat.com \
--cc=qiyaoltc@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