Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: roland.schwingel@onevision.de, gdb@sourceware.org
Subject: Re: gdb stack trace problems (Addendum)
Date: Mon, 25 Apr 2005 19:45:00 -0000	[thread overview]
Message-ID: <20050425193423.GA23856@nevyn.them.org> (raw)
In-Reply-To: <200504251926.j3PJQWUS002190@elgar.sibelius.xs4all.nl>

On Mon, Apr 25, 2005 at 09:26:32PM +0200, Mark Kettenis wrote:
> Can you test the attached patch?  It introduces a new option named
> "trust-frame-pointer".  Whenever you encounter a problem you can:
> 
> (gdb) set trust-frame-pointer 1

"set i386 trust-frame-pointer", please?

> and try again.  You probably want to reset it to 0 before continuing
> your program since I found out that bad things happen with some of the
> tests in the gdb testsuite with this turned on.

Hmm, what sort of bad things?


-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-25 19:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 12:35 Roland Schwingel
2005-04-25  8:00 ` Roland Schwingel
2005-04-25 19:35 ` Mark Kettenis
2005-04-25 19:45   ` Daniel Jacobowitz [this message]
2005-04-25 20:37     ` Mark Kettenis
  -- strict thread matches above, loose matches on Subject: below --
2005-05-10  8:39 Roland Schwingel
2005-05-10  8:38 Roland Schwingel
2005-05-02  7:04 Roland Schwingel
2005-05-08 13:31 ` Mark Kettenis
2005-05-08 23:20   ` Christopher Faylor
2005-05-09  4:48     ` Eli Zaretskii
2005-05-09  5:26       ` Christopher Faylor
2005-05-09  5:30     ` Stan Shebs
2005-04-26 11:53 Roland Schwingel
2005-04-26  9:11 Roland Schwingel
2005-04-19  8:01 Roland Schwingel
     [not found] ` <4268B942.5080300@onevision.de>
2005-04-22 17:51   ` Mark Kettenis
2005-04-19  7:34 Roland Schwingel
2005-04-19  7:45 ` Mark Kettenis

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=20050425193423.GA23856@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=roland.schwingel@onevision.de \
    /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