From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [rfc] LINUX/sparc64 configury
Date: Fri, 23 Feb 2001 18:15:00 -0000 [thread overview]
Message-ID: <3A9718CF.B6151E58@cygnus.com> (raw)
Hello,
The attatched adds sufficient configury to GDB for it to build a very
basic GNU/Linux/sparc64 GDB. It doesn't work:
$ ./gdb gdb
GNU gdb 5.0
Copyright 2001 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 "sparc64-unknown-linux-gnu"...
Setting up the environment for debugging gdb.
Breakpoint 1 at 0x83a54: file /home/cagney/GDB/src/gdb/utils.c, line
741.
Breakpoint 2 at 0xee600: file /home/cagney/GDB/src/gdb/cli/cli-cmds.c,
line 186.
(top-gdb) b main
Breakpoint 3 at 0x13554: file /home/cagney/GDB/src/gdb/main.c, line 763.
(top-gdb) run
Starting program: /home/cagney/GDB/native/gdb/gdb
During symbol reading...inner block (0x0-0x70000000) not inside outer
block (0x0-0x70000054)...
warning: Internal error, changing continue to step.
Aborted (core dumped)
I'm really only interested in comments on my choice of file names. I
think they are even 8.3 safe! :-)
More patching/merging will obviously need to follow. If anyone wants to
help, see Jakub's ``[PATCH] Sparc Linux stuff'' posting for my source of
patches.
Andrew
PS: So Kevin, how soon can we get the abort() patch in :-)
next reply other threads:[~2001-02-23 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 18:15 Andrew Cagney [this message]
2001-02-24 0:51 ` Eli Zaretskii
2001-02-26 11:26 ` Andrew Cagney
2001-02-27 9:07 ` Andrew Cagney
2001-02-27 10:21 ` Eli Zaretskii
2001-02-24 20:49 ` Kevin Buettner
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=3A9718CF.B6151E58@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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