public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/9568] Backtracing recursive main function call
Date: Sat, 06 Jan 2024 19:14:32 +0000	[thread overview]
Message-ID: <bug-9568-4717-WWAgqNJMXy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9568-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=9568

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |NOTABUG
                 CC|                            |ssbssa at sourceware dot org

--- Comment #2 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to drow@false.org from comment #1)
> From: Daniel Jacobowitz <drow@false.org>
> To: orium69@gmail.com
> Cc: gdb-gnats@sourceware.org
> Subject: Re: backtrace/2463: Backtracing recursive main function call
> Date: Thu, 5 Jun 2008 07:33:44 -0400
> 
>  On Thu, Jun 05, 2008 at 10:08:09AM -0000, orium69@gmail.com wrote:
>  > The gdb fails to print a correct backtrace of a program which segfaults
> with stack overflow in function main().
>  
>  Take a look at the GDB command "set backtrace past-main".
>  
>  -- 
>  Daniel Jacobowitz
>  CodeSourcery

I'm closing this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

           reply	other threads:[~2024-01-06 19:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-9568-4717@http.sourceware.org/bugzilla/>]

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=bug-9568-4717-WWAgqNJMXy@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).