From: Elena Zannoni <ezannoni@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [rfa/sym*] Look at N_MAIN
Date: Sun, 01 Apr 2001 17:11:00 -0000 [thread overview]
Message-ID: <15047.50070.204436.871382@kwikemart.cygnus.com> (raw)
In-Reply-To: <3AB23416.EF23DDB2@cygnus.com>
Andrew Cagney writes:
> (resolving this is part of the 5.1 release criteria)
>
> The attatched patch gets GDB to make use of N_MAIN when available. The
> original, submitted by Anthony Green, needed some improvements (see
> attatched e-mails).
>
> I've addressed just the memory leak problem.
>
> Andrew2001-03-16 Andrew Cagney <ac131313@redhat.com>
>
> * symtab.c (main_name): New function.
> (set_main_name): New function.
> * symtab.h: Declare.
>
> From 2000-03-05 Anthony Green <green@redhat.com>:
> * dbxread.c (process_one_symbol): Handle the N_MAIN stab by
> setting main_name.
> * blockframe.c (inside_main_func): Use main_name instead of
> "main".
> * symtab.c (find_main_psymtab): Ditto.
> * source.c (select_source_symtab): Ditto.
> * nlmread.c (nlm_symfile_read): Ditto.
> * rs6000-tdep.c (skip_prologue): Ditto.
BTW, while grepping for 'main', 'MAIN', etc. I found some interesting
things in f-lang.h. Does anybody know what's up with these?
I coundn't see any uses or ChangeLog entries related to them.
extern char *real_main_name; /* Name of main function */
extern int real_main_c_value; /* C_value field of main function */
#define DEFAULT_DOTMAIN_NAME_IN_MF77 ".MAIN_"
#define DEFAULT_MAIN_NAME_IN_MF77 "MAIN_"
#define DEFAULT_DOTMAIN_NAME_IN_XLF_BUGGY ".main "
#define DEFAULT_DOTMAIN_NAME_IN_XLF ".main"
Also there is a "main" hack in hp-psymtab-read.c and hp-symtab-read.c
But that's local.
Elena
prev parent reply other threads:[~2001-04-01 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 7:41 Andrew Cagney
2001-04-01 17:06 ` Elena Zannoni
2001-04-01 17:11 ` Elena Zannoni [this message]
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=15047.50070.204436.871382@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
/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