From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10579 invoked by alias); 27 Sep 2007 01:58:47 -0000 Received: (qmail 10528 invoked by uid 22791); 27 Sep 2007 01:58:45 -0000 X-Spam-Check-By: sourceware.org Received: from hera.math.uni.wroc.pl (HELO hera.math.uni.wroc.pl) (156.17.86.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 27 Sep 2007 01:58:41 +0000 Received: from hebisch by hera.math.uni.wroc.pl with local (Exim 3.36 #1 (Debian)) id 1Iaie4-0004Wd-00; Thu, 27 Sep 2007 03:58:28 +0200 Subject: Re: [RFC] Handle GPC specific name for main function In-Reply-To: <003901c8004b$2f9a55d0$8ecf0170$@u-strasbg.fr> To: Pierre Muller Date: Thu, 27 Sep 2007 01:58:00 -0000 CC: gdb-patches@sourceware.org, gpc@gnu.de X-Mailer: ELM [version 2.4ME+ PL100 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: From: Waldek Hebisch Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-09/txt/msg00395.txt.bz2 Pierre Muller wrote: > This patch looks up for > GPC specific minimal symbols > and assumes that if they are present, > the executable was compiled by GPC. > GPC used 'pascal_main_program' and now > uses '_p__M0_main_program'. > > Is there some other way to check that the > program was really compiled by GPC? > (Any C compiled program could have a > 'pascal_main_program' function...) > > Maybe by looking up some other symbol? > I found 'GPC_init' as a possible candidate, > but I am not sure that this symbol is > defined for all versions of GPC, so I did not > include it in the present RFC. > I doubt that any simple method will work for "all versions of GPC". According to change log 'pascal_main_program' was introduced 24 Jun 2000, earler GPC used 'program_Foo' where 'Foo' is program name. '_p__M0_main_program' appeared in gpc-20050217 (however, there for a few month the change was available as a patch, so '_p__M0_main_program' may appear also in earlier versions). I would say that the most reliable indication that the program is GPC compiled is if debug info indicate that language is Pascal and there are signs that the file is gcc compiled (otherwise the file is compiled by some other Pascal compiler). If debug info indicate other language file is not GPC compiled. Concerning 'GPC_init': it is probably present in all currently used versions. It is absent in ancient versions like gpc-1.2-2.7.2. 'GPC_init' may vanish from future versions -- it is one of few names in GPC runtime which do not use '_p_' prefix. Also, while I know of no way to omit 'GPC_init' when using standard runtime it is possible to use alternative runtime which does not contain 'GPC_init. When checking if program is GPC compiled one may look at '_p_initialize' -- it is present at least from 1993 up to now. Also current GPC versions use a special symbol to check for matched runtiome. This symbol looks like '_p_GPC_RTS_VERSION_20060215' (where to last part encodes version of the runtime). Versions before 2004-02-04 used GPC_RTS_VERSION_YYYYMMDD. I do not know when this symbol was introduced -- it is absent in gpc-1.2-2.7.2 but present in gpc-20020510. Both '_p_initialize' and '_p_GPC_RTS_VERSION_20060215' are referenced from 'main', so they must appear even if alternate runtime is in use. GPC emits '_p__M0_main_program' (or 'pascal_main_program') in the same file as 'main', and '_p__M0_main_program' is called from 'main' -- I am not sure if gdb can check this. Let me remark that it is possible to have '_p__M0_main_program' without having 'main'. Namely, GPC allows to compile Pascal source like normal program, but replacing main by a differently named function. One use of such possibility is when making shared libraries. Another is when the main program is not a Pascal program. -- Waldek Hebisch hebisch@math.uni.wroc.pl