Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Stefan Burström" <f94sbu@efd.lth.se>
To: gdb@sources.redhat.com
Subject: PPC stack trace
Date: Thu, 28 Jul 2005 00:50:00 -0000	[thread overview]
Message-ID: <33dbf7bc5f5.3af4bdd3@mail.m.bonet.se> (raw)

HHello!
I am currently porting gdb6.3 to AmigaOS4 and I am having some issues with
stack traces on PPC. If I try to trace the stack through a function that
does not include debug info, then the stack trace stops complaining that the
previous frame is identical to this frame. Is this a know problem for the
PPC version of gdb?

I can provide quite accurate logs if someone is interested...

Any ideas?

regards,
Stefan Burström

(ps. I tried to send this email to gdb-prs but that email just bounced)


             reply	other threads:[~2005-07-28  0:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28  0:50 Stefan Burström [this message]
2005-07-31  0:19 ` rs6000 / ppc backend in gdb Stefan Burström
2005-07-31  1:17   ` Daniel Jacobowitz
2005-07-31 22:15     ` Stefan Burström
2005-08-01 13:12       ` Daniel Jacobowitz
2005-08-01 20:45         ` Stefan Burström
2005-08-01 20:51           ` Daniel Jacobowitz
2005-08-01 21:08             ` Stefan Burström

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=33dbf7bc5f5.3af4bdd3@mail.m.bonet.se \
    --to=f94sbu@efd.lth.se \
    --cc=gdb@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