Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Wed, 18 Dec 2013 15:02:00 -0000	[thread overview]
Message-ID: <87vbymmcck.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5512.41819416663$1387235536@news.gmane.org> (Pierre Muller's	message of "Tue, 17 Dec 2013 00:11:48 +0100")

>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:

Pierre>   I suspect that it would at least require some init_abi function
Pierre> to set this... But then the question is, how do we recognize 
Pierre> such executables...

You'll at least need different code to extract the target PC from the
jump buffer.

Tom> What about PC mangling? 

Pierre>   I am not sure what you mean here...
Pierre> There is no operation on pc value.

On some platforms glibc mangles the PC value that is saved in the
buffer.

Tom> and why is it not just
Tom> a simple wrapper for the C library longjmp?

Pierre> Because, by default, Free Pascal compiler generates code that is
Pierre> independent of any library (static code on Linux for instance)
Pierre> with only direct calls to System Calls.

Makes sense.  I guess some deeper change is needed, not just adding
fpc_longjmp to the list.

Tom


  parent reply	other threads:[~2013-12-18 15:02 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
2013-12-16 23:12   ` Pierre Muller
     [not found]   ` <5512.41819416663$1387235536@news.gmane.org>
2013-12-18 15:02     ` Tom Tromey [this message]
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=87vbymmcck.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