From: Steve Ellcey <sje@cup.hp.com>
To: gdb-patches@sourceware.org
Subject: Patch for HPPA HP-UX build failure
Date: Wed, 10 May 2006 18:46:00 -0000 [thread overview]
Message-ID: <200605101846.LAA20443@hpsje.cup.hp.com> (raw)
I noticed that gdb on HPPA HP-UX was not building unless I use
--disable-nls, this is because of a problem with using the _() macro in
an intialization. GCC 4.0.2 would error on the initiazation of message.
I noticed that there were no other initializations like this so I
removed it and used the macro/string directly in the call to
catch_error. This patch allowed me to build gdb on
hppa1.1.-hp-hpux11.11.
OK to checkin?
2006-05-10 Steve Ellcey <sje@cup.hp.com>
* hppa-hpux-tdep.c (initialize_hp_cxx_exception_support): Remove
message.
*** hppa-hpux-tdep.c.orig Wed May 10 10:22:09 2006
--- hppa-hpux-tdep.c Wed May 10 11:33:08 2006
*************** GDB will be unable to intercept exceptio
*** 865,878 ****
does the equivalent of shl_findsym()) to find the plabel. */
args_for_find_stub args;
- static char message[] = _("Error while finding exception callback hook:\n");
args.solib_handle = gdbarch_tdep (current_gdbarch)->solib_get_solib_by_pc (eh_notify_callback_addr);
args.msym = msym;
args.return_val = 0;
recurse++;
! catch_errors (cover_find_stub_with_shl_get, &args, message,
RETURN_MASK_ALL);
eh_notify_callback_addr = args.return_val;
recurse--;
--- 865,878 ----
does the equivalent of shl_findsym()) to find the plabel. */
args_for_find_stub args;
args.solib_handle = gdbarch_tdep (current_gdbarch)->solib_get_solib_by_pc (eh_notify_callback_addr);
args.msym = msym;
args.return_val = 0;
recurse++;
! catch_errors (cover_find_stub_with_shl_get, &args,
! _("Error while finding exception callback hook:\n"),
RETURN_MASK_ALL);
eh_notify_callback_addr = args.return_val;
recurse--;
next reply other threads:[~2006-05-10 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 18:46 Steve Ellcey [this message]
2006-05-10 18:50 ` Daniel Jacobowitz
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=200605101846.LAA20443@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=gdb-patches@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