From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: Use DWARF CFI frame unwinder on powerpc
Date: Tue, 09 May 2006 17:17:00 -0000 [thread overview]
Message-ID: <1147195124.16180.44.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <jehd3z1dy7.fsf@sykes.suse.de>
On Tue, 2006-05-09 at 16:16 +0200, Andreas Schwab wrote:
> Together with the previous patch this enables the use of the DWARF CFI
> frame unwinder on powerpc.
I applied your patches and gave them a spin and had a slight problem...
Here is the source for the target program:
#include <stdio.h>
void hello ()
{
printf ("Hello, world!\n");
}
int main()
{
hello();
return 0;
}
Here is a transcript:
[pgilliam@dufur gdb]$ ./gdb ../../hello32
GNU gdb 6.4.50.20060509-cvs
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License,
and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty"
for details.
This GDB was configured as "powerpc64-unknown-linux-gnu"...Using
host libthread_db library "/lib/libthread_db.so.1".
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Function "info_command" not defined.
/home/pgilliam/gdb/tree-head/build32/gdb/.gdbinit:8: Error in
sourced command file:
No breakpoint number 0.
(gdb) b hello
Breakpoint 1 at 0x10000464: file hello.c, line 5.
(gdb) r
Starting program: /home/pgilliam/gdb/tree-head/hello32
Breakpoint 1, hello () at hello.c:5
5 printf ("Hello, world!\n");
(gdb) n
>>>>During symbol reading, incomplete CFI data; unspecified registers
>>>>(e.g., r0) at 0x10000464.
Hello, world!
6 }
(gdb) q
The program is running. Exit anyway? (y or n) y
Do I need a flag other then -g when compiling to get CFI data?
This was on a ppc64 system, 32-bit GDB, 32-bit target program.
I got the same results with 64-bit GDB, 32 and 64-bit target programs.
-=# Paul #=-
next prev parent reply other threads:[~2006-05-09 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 14:16 Andreas Schwab
2006-05-09 17:17 ` PAUL GILLIAM [this message]
2006-05-09 17:23 ` Daniel Jacobowitz
2006-05-09 22:26 ` PAUL GILLIAM
2006-05-09 17:46 ` Andreas Schwab
2006-05-09 18:01 ` David S. Miller
2006-05-09 18:39 ` Daniel Jacobowitz
2006-05-09 21:07 ` David S. Miller
2006-05-15 16:46 ` Daniel Jacobowitz
2006-05-15 19:10 ` Mark Kettenis
2006-05-15 20:43 ` Daniel Jacobowitz
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=1147195124.16180.44.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.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