From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3919 invoked by alias); 28 Jul 2005 00:50:21 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3902 invoked by uid 22791); 28 Jul 2005 00:50:18 -0000 Received: from mxfep01.bredband.com (HELO mxfep01.bredband.com) (195.54.107.70) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 28 Jul 2005 00:50:18 +0000 Received: from efd.lth.se ([217.215.11.93] [217.215.11.93]) by mxfep01.bredband.com with SMTP id <20050728005016.NZZG11632.mxfep01.bredband.com@efd.lth.se> for ; Thu, 28 Jul 2005 02:50:16 +0200 From: Stefan =?ISO-8859-15?Q?Burstr=F6m?= To: gdb@sources.redhat.com Date: Thu, 28 Jul 2005 00:50:00 -0000 Message-ID: <33dbf7bc5f5.3af4bdd3@mail.m.bonet.se> Subject: PPC stack trace MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2005-07/txt/msg00258.txt.bz2 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=F6m (ps. I tried to send this email to gdb-prs but that email just bounced)