From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC] pascal: also handle Free Pascal longjump function.
Date: Mon, 16 Dec 2013 21:48:00 -0000 [thread overview]
Message-ID: <87mwk0pix6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <37888.8297280811$1386971648@news.gmane.org> (Pierre Muller's message of "Fri, 13 Dec 2013 22:52:52 +0100")
>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:
Pierre> - Where is this internal long jump breakpoint really used in the code?
Search infrun.c for BPSTAT_WHAT_SET_LONGJMP_RESUME.
Pierre> - Is this kind of patch likely to be accepted?
Sure.
Pierre> I would perfectly understand that it would be not acceptable as is,
Pierre> but maybe some language specific version of the
Pierre> longjmp name would be useful, no?
I don't think it makes sense to be language-dependent here, because
then this makes mixed-language debugging harder.
I do wonder whether gdb will really be able to understand this function.
Does it make jmp_bufs compatible with the arch support already in gdb?
What about PC mangling? What defines fpc_longjmp and why is it not just
a simple wrapper for the C library longjmp?
Tom
next parent reply other threads:[~2013-12-16 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37888.8297280811$1386971648@news.gmane.org>
2013-12-16 21:48 ` Tom Tromey [this message]
2013-12-16 23:12 ` Pierre Muller
[not found] ` <5512.41819416663$1387235536@news.gmane.org>
2013-12-18 15:02 ` Tom Tromey
2013-12-13 21:53 Pierre Muller
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=87mwk0pix6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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