Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com
Subject: [CRIS] Backtrace past clone
Date: Mon, 30 Aug 2004 15:07:00 -0000	[thread overview]
Message-ID: <41334294.9010906@axis.com> (raw)

I'm having trouble with backtrace not stopping at clone (in the child). 
  Normally I rely on the Dwarf-2 CFI, but clone doesn't have any, so 
this falls back on the manual unwinder.

I understand that using frame pointer register != 0 is dubious (since 
the code we may end up analyzing in the manual unwinder could be 
compiled without a frame pointer), although the glibc clone function for 
CRIS does set the frame pointer to 0.  Other than that, I can't see how 
to detect that the call stack ends for the child.

I see this has been discussed for MIPS in the thread starting at 
http://sources.redhat.com/ml/gdb-patches/2004-03/msg00128.html, which 
also references missing Dwarf-2 information.  Besides this, "grep clone" 
in src/gdb gave surprisingly few hits, as did searching for "clone 
backtrace" in the gdb-patches archive.  The lack of architecture 
-specific search results me wonder if this is something that should be 
handled by the Dwarf-2 unwinder (and that what needs to be fixed is the 
missing Dwarf-2 CFI for clone).

Any suggestions?

-- 
Orjan Friberg
Axis Communications


             reply	other threads:[~2004-08-30 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 15:07 Orjan Friberg [this message]
2004-08-30 20:10 ` Andrew Cagney
2004-08-31 12:39   ` Orjan Friberg

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=41334294.9010906@axis.com \
    --to=orjan.friberg@axis.com \
    --cc=gdb-patches@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