From: Waldek Hebisch <hebisch@math.uni.wroc.pl>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: "'Adriaan van Os'" <gpc@microbizz.nl>,
gpc@gnu.de, gdb-patches@sourceware.org
Subject: Re: [RFC-3] Handle GPC specific name for main function
Date: Thu, 27 Sep 2007 13:01:00 -0000 [thread overview]
Message-ID: <E1Iasyr-0005T1-00@hera.math.uni.wroc.pl> (raw)
In-Reply-To: <000101c800dc$ab0648a0$0112d9e0$@u-strasbg.fr>
Pierre Muller wrote:
> As stated in my other email,
> the whole purpose of this patch is not to
> determine if the source was compiled by GPC,
> but to get the command 'start' to end up at the right
> location.
> This right location is either '_p_M0_main_program' or
> 'pascal_main_program'
> (or 'program_Foo' for very old version, that my patch will not support.)
>
Assuming that the main program is compiled by GPC looking for
'_p_M0_main_program' or 'pascal_main_program' should work fine.
However, if the main program was compiled by some other compiler
the program in principle may still contain such magic symbol
-- using it as start location would be wrong.
In the 'demos' subdirectory of gpc tarball one can find files
'gpc_c_pas.pas', 'gpc_c_unit.pas' and 'gpc_c_c.c' -- this
is a demo program showing how to make main program in C but use
from it Pascal routines. In this example '_p_M0_main_program' is
never called and the right location for 'start' command is
C main. It is easy to create mixed mode program without
fake '_p_M0_main_program', but unfortunately the demo creates
fake '_p_M0_main_program'.
Another possibility is program in other language (or compiled
by some other Pascal compiler) which happens to contain
'pascal_main_program'. I hope that '_p_M0_main_program' is
very unlikely to appear in non-GPC program, but 'pascal_main_program'
is a reasonable name so it makes sense to look for confirmation
that the program is GPC compiled.
'_p_initialize' indicates presence of GPC runtime (so it really
does not help in case of mixed mode programs). I should also
mention that there was a report that 'libplot' library also
contains '_p_initialize' function...
I also mentioned shared libraries. Now I think that they pose
no extra problem -- presumably 'start' command will go to
a symbol in main executable and just ignore shared libraries.
--
Waldek Hebisch
hebisch@math.uni.wroc.pl
next prev parent reply other threads:[~2007-09-27 13:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 14:40 [RFC] " Pierre Muller
2007-09-26 15:03 ` Eli Zaretskii
2007-09-26 15:32 ` Pierre Muller
2007-09-26 17:48 ` Eli Zaretskii
2007-09-26 17:58 ` Joel Brobecker
2007-09-26 19:39 ` Pierre Muller
2007-09-26 19:50 ` Joel Brobecker
2007-09-26 22:06 ` Pierre Muller
2007-09-26 22:39 ` [RFC-2] " Pierre Muller
2007-09-27 6:03 ` Joel Brobecker
2007-09-27 7:29 ` [RFC-3] " Pierre Muller
[not found] ` <46FB5E2C.6080606@microbizz.nl>
[not found] ` <46FB5F76.9050501@microbizz.nl>
2007-09-27 7:57 ` Pierre Muller
2007-09-27 12:11 ` Daniel Jacobowitz
2007-09-27 12:35 ` Pierre Muller
2007-09-27 12:40 ` 'Daniel Jacobowitz'
2007-09-27 16:20 ` Joel Brobecker
2007-09-27 16:32 ` Joel Brobecker
2007-09-27 21:36 ` Pierre Muller
2007-09-28 18:31 ` Joel Brobecker
2007-09-27 8:02 ` Pierre Muller
2007-09-27 13:01 ` Waldek Hebisch [this message]
2007-09-27 7:20 ` [RFC-2] " Eli Zaretskii
2007-09-27 1:58 ` [RFC] " Waldek Hebisch
2007-09-27 5:52 ` Joel Brobecker
2007-09-27 17:17 ` Thiago Jung Bauermann
2007-09-27 19:50 ` Jim Blandy
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=E1Iasyr-0005T1-00@hera.math.uni.wroc.pl \
--to=hebisch@math.uni.wroc.pl \
--cc=gdb-patches@sourceware.org \
--cc=gpc@gnu.de \
--cc=gpc@microbizz.nl \
--cc=muller@ics.u-strasbg.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