Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stefan Bylund <steby@enea.se>
To: gdb@sourceware.org
Subject: Re: Does GDB 6.7.1 for PowerPC require the framepointer register  for backtracing?
Date: Tue, 12 Feb 2008 15:21:00 -0000	[thread overview]
Message-ID: <47B1B96C.5080402@enea.se> (raw)
In-Reply-To: <20080212133039.GA5173@caradoc.them.org>

You're not being dense. You really helped me. Thanks again.

/Stefan


Daniel Jacobowitz wrote:

>On Tue, Feb 12, 2008 at 11:23:47AM +0100, Stefan Bylund wrote:
>  
>
>>Hi Daniel,
>>
>>Thanks for all your valuable answers! We will use -fomit-frame-pointer as 
>>a workaround for now. Later on we will add support for handling the frame 
>>pointer register in our OS kernel. That seems to be the future-proof 
>>solution.
>>    
>>
>
>Oh, I see what you mean now.  You really have only access to those two
>registers.  Sorry for being dense.
>
>I recommend you allow GDB to access the full register set.  Future
>versions of GDB may use any register at all in the unwind information.
>
>  
>


-- 
---------------------------------
Stefan Bylund
Senior Software Engineer
Enea
Skalholtsgatan 9,
Box 1033, SE-164 21 Kista, Sweden
Direct: +46 8 50 71 43 25
Mobile: +46 709 71 43 25
stefan.bylund@enea.com
www.enea.com
---------------------------------
Enea - Embedded for Leaders
---------------------------------


      reply	other threads:[~2008-02-12 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 11:03 Stefan Bylund
2008-02-11 13:08 ` Daniel Jacobowitz
2008-02-11 17:29   ` Stefan Bylund
2008-02-11 17:33     ` Daniel Jacobowitz
2008-02-12 10:24       ` Stefan Bylund
2008-02-12 13:31         ` Daniel Jacobowitz
2008-02-12 15:21           ` Stefan Bylund [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=47B1B96C.5080402@enea.se \
    --to=steby@enea.se \
    --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