Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: Problems while debugging fortran
Date: Tue, 25 Sep 2007 01:29:00 -0000	[thread overview]
Message-ID: <20070924234910.GB8601@adacore.com> (raw)
In-Reply-To: <46F81E0C.7030709@linux.vnet.ibm.com>

> > I think Daniel was right on the spot. You are trying to use the
> > "current source file" concept right at the start of your session
> > assuming that it is automatically set to the source file where
> > you main is defined. Is that correct?
> Yes. And the problem is that the current file is set as "init.c".

I wonder why that is. Is this the file where function "main" is
reported to be?

> > We can certainly work on modifying GDB to be
> > better at finding the name of the main procedure in a Fortran program
> > (just like we do with Ada programs).
> Any ideas where can we start?

In terms of the GDB implementation, you can start by looking at what
we do in symtab.c:find_main_name(). What you need to do is find a way
for GDB to determine what the name of the main routine is. See the
comment I inserted that explains also that we should not have any
false positive.

In terms of the Fortran compiler, I don't know how things are setup,
so I don't know how it actually needs to be done, or if it's doable
at all, actually.  It looks like, from the patch that Daniel posted,
that this routine is always called "MAIN__". Is that the case?

-- 
Joel


  reply	other threads:[~2007-09-24 23:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 11:37 Carlos Eduardo Seo
2007-09-20 19:47 ` Joel Brobecker
2007-09-20 20:46   ` Carlos Eduardo Seo
2007-09-20 20:56     ` Joel Brobecker
2007-09-21  6:52       ` Daniel Jacobowitz
2007-09-26 21:46         ` Carlos Eduardo Seo
2007-09-26 21:51           ` Pierre Muller
2007-09-26 21:51           ` Joel Brobecker
2007-10-24 16:20             ` Carlos Eduardo Seo
2007-10-24 19:33               ` Joel Brobecker
2007-10-24 19:57                 ` Daniel Jacobowitz
2007-10-24 20:16                   ` Carlos Eduardo Seo
2007-10-24 21:56                     ` Carlos Eduardo Seo
2007-09-23  2:52       ` Carlos Eduardo Seo
2007-09-24 10:01         ` Joel Brobecker
2007-09-24 23:49           ` Carlos Eduardo Seo
2007-09-25  1:29             ` Joel Brobecker [this message]
2007-09-25 17:34               ` Carlos Eduardo Seo
2007-09-26  6:29                 ` Joel Brobecker
2007-10-25 16:07 François-Xavier Coudert
2007-10-25 17:06 ` Daniel Jacobowitz
2007-10-25 18:44   ` Jim Blandy
2007-10-25 19:01     ` Daniel Jacobowitz
2007-10-25 19:27       ` Jim Blandy
2007-10-25 20:24         ` Joel Brobecker
2007-10-25 20:36           ` Carlos Eduardo Seo
2007-10-25 20:41             ` Joel Brobecker
2007-10-25 20:55             ` Andreas Schwab

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=20070924234910.GB8601@adacore.com \
    --to=brobecker@adacore.com \
    --cc=cseo@linux.vnet.ibm.com \
    --cc=gdb@sourceware.org \
    /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