From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Adriaan van Os'" <gpc@microbizz.nl>, <gpc@gnu.de>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC-3] Handle GPC specific name for main function
Date: Thu, 27 Sep 2007 07:57:00 -0000 [thread overview]
Message-ID: <000001c800dc$14b0df00$3e129d00$@u-strasbg.fr> (raw)
In-Reply-To: <46FB5F76.9050501@microbizz.nl>
> -----Original Message-----
> From: gpc-owner@gnu.de [mailto:gpc-owner@gnu.de] On Behalf Of Adriaan
> van Os
> Sent: Thursday, September 27, 2007 9:45 AM
> To: gpc@gnu.de
> Subject: Re: [RFC-3] Handle GPC specific name for main function
>
> > Pierre Muller wrote:
> >> Based on comments from Waldek and concerns from Joel,
> >> I propose that we first check for the presence of the
> >> '_p_initialize' minimal symbol, and only look for
> >> '_p_M0_main_program' and 'pascal_main_program'
> >> if the '_p_initialize' was found.
> >
> > The check should certainly not be for _p_M0_main_program or
> > pascal_main_program'. Waldek rightly remarked that e.g. shared
> libraries
> > won't have these symbols. Better is to look for _p_initialize and/or
> > GPC_RTS_VERSION_YYYYMMDD.
>
> On second thought - are these symbols present when linking to a dynamic
> libgpc ?
Does this matter anyhow?
We are just trying to get the
gdb command 'start' to end up at the right location,
i.e. for a pascal program, at the start of
the main procedure of the main source.
This is of no meaning for a library,
unless I am missing something...
I doubt that you can use 'start' for a library.
Pierre
next prev parent reply other threads:[~2007-09-27 7:57 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 [this message]
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
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='000001c800dc$14b0df00$3e129d00$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=gpc@gnu.de \
--cc=gpc@microbizz.nl \
/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