Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org, david@streamline-computing.com
Cc: gdb@sources.redhat.com
Subject: Re: Opteron Stack Woes
Date: Tue, 17 Aug 2004 13:48:00 -0000	[thread overview]
Message-ID: <41220C98.nailNAQ1TW4UF@mindspring.com> (raw)
In-Reply-To: <20040817131057.GA7719@nevyn.them.org>

> You might want to investigate why the backtrace didn't stop earlier, at
> main or at a fortran entry point.  GDB may be confused about
> main_name().

This hit me too when I tried to write the first fortran program for the
test suite.  I haven't filed a PR yet, but gdb is clueless about
main_name for fortran programs compiled with g77 3.4.1, both dwarf-2 and
stabs+.  When I say 'start', gdb puts the breakpoint in function 'main'
in the fortran runtime library, not at the 'program' statement.

The only call to set_main_name in gdb is in dbxread.c
and it's not getting called.  I don't see any N_MAIN stab line
in hello.s, so g77 3.4.1 isn't doing what we want.

Note that David is using a different fortran compiler.
I don't know why David's stack trace blows right through main.


  parent reply	other threads:[~2004-08-17 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 11:46 David Lecomber
2004-08-17 13:11 ` Daniel Jacobowitz
2004-08-17 13:29   ` David Lecomber
2004-08-17 14:10     ` Daniel Jacobowitz
2004-08-17 13:48   ` Michael Chastain [this message]
2004-08-17 14:47 ` H. J. Lu
2004-08-25 19:49 ` [RFC] Backtrace limit David Lecomber

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=41220C98.nailNAQ1TW4UF@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=david@streamline-computing.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.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