public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFC] pascal: also handle Free Pascal longjump function.
Date: Fri, 13 Dec 2013 21:53:00 -0000	[thread overview]
Message-ID: <001b01cef84d$c5aca7c0$5105f740$@muller@ics-cnrs.unistra.fr> (raw)

  Free pascal uses fpc_longjmp internal name
for the long jump function.

  I would like to know two things:

- Where is this internal long jump breakpoint really used in the code?
- Is this kind of patch likely to be accepted?
I would perfectly understand that it would be not acceptable as is,
but maybe some language specific version of the
longjmp name would be useful, no?

  Comments most welcome.

Pierre Muller


ChangeLog entry:

2013-12-13  Pierre Muller  <muller@sourceware.org>

      Also accept Free Pascal name for longjmp function.

--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -3086,7 +3086,7 @@ create_internal_breakpoint (struct gdbarch *gdbarch,

 static const char *const longjmp_names[] =
   {
-    "longjmp", "_longjmp", "siglongjmp", "_siglongjmp"
+    "longjmp", "_longjmp", "siglongjmp", "_siglongjmp", "fpc_longjmp"
   };
 #define NUM_LONGJMP_NAMES ARRAY_SIZE(longjmp_names)

             reply	other threads:[~2013-12-13 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 21:53 Pierre Muller [this message]
     [not found] <37888.8297280811$1386971648@news.gmane.org>
2013-12-16 21:48 ` Tom Tromey
2013-12-16 23:12   ` Pierre Muller
     [not found]   ` <5512.41819416663$1387235536@news.gmane.org>
2013-12-18 15:02     ` Tom Tromey

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='001b01cef84d$c5aca7c0$5105f740$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).