public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: sjohnson@sakuraindustries.com
Cc: drow@false.org, gdb@sources.redhat.com
Subject: Re: Unwinding stack past main() when it has another name
Date: Thu, 16 Jun 2005 23:36:00 -0000	[thread overview]
Message-ID: <200506162336.j5GNaCYD021758@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <42B322E5.4080403@sakuraindustries.com> (message from Steven Johnson on Fri, 17 Jun 2005 08:22:13 -1100)

   Date: Fri, 17 Jun 2005 08:22:13 -1100
   From: Steven Johnson <sjohnson@sakuraindustries.com>

   Daniel Jacobowitz wrote:

   >The fact that we stop at _start is a feature, so hopefully you can rely
   >on that in the future.
   >
   >For some non-C languages we get the name of the main function from
   >debug information, but for C it's always main()
   >  
   >
   This isnt always the case for embedded targets.  There is no RULE that C 
   programs must have a main() function.

Oh there is.  But of course you don't have to play by that rule.  But
if you don't play by that rule you're very likely want to see the
complete backtrace up to the entry point of your program anyway.

Mark

      parent reply	other threads:[~2005-06-16 23:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 12:46 Hamish Rodda
2005-06-15 14:16 ` Daniel Jacobowitz
2005-06-15 15:14   ` Hamish Rodda
2005-06-15 16:37     ` Daniel Jacobowitz
2005-06-16  7:42       ` Hamish Rodda
2005-06-16 13:23         ` Daniel Jacobowitz
2005-06-16 21:22           ` Steven Johnson
2005-06-16 22:05             ` Daniel Jacobowitz
2005-06-16 22:46               ` Steven Johnson
2005-06-17 11:21               ` Richard Earnshaw
2005-06-18 13:13                 ` Eli Zaretskii
2005-06-16 23:36             ` Mark Kettenis [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=200506162336.j5GNaCYD021758@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=sjohnson@sakuraindustries.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).