From: Chuck Aude <caude@legato.com>
To: gdb@sources.redhat.com
Subject: gdb & 64-bit Solaris - does it work?
Date: Fri, 18 Jul 2003 16:02:00 -0000 [thread overview]
Message-ID: <3F1819F0.2060606@legato.com> (raw)
Has anyone had any luck getting any version of gdb to work on a 64-bit
Solaris 7 binary built with gcc 3.2? I have tried both gdb-5.3 and
gdb-6.0 (last night's CVS image) and end up with the same "Cannot insert
breakpoint" error. Searching the gdb mailing list, reveals many other
people getting the same error and the gdb bug database has several bugs
related to this.
Does gdb support debugging 64-bit Solaris binaries or am I trying to
make it do something it can't do?
Here's another example of the error:
[caude@phobos]$ more hello.c
#include <stdio.h>
int
main(int argc, char **argv)
{
printf ("Hello World\n");
}
[caude@phobos]$ gcc-3.2 -m64 -g -o hello hello.c
[caude@phobos]$ gdb64-5.3 hello
GNU gdb 5.3
Copyright 2002 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 "sparc-sun-solaris2.7"...
(gdb) run
Starting program: /home/jupiter8/caude/hello
Hello World
Program exited with code 014.
(gdb) br main
Breakpoint 1 at 0x860: file hello.c, line 6.
(gdb) run
Starting program: /home/jupiter8/caude/hello
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0x860: I/O error.
The same program may be running in another process.
(gdb) q
The program is running. Exit anyway? (y or n) y
next reply other threads:[~2003-07-18 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 16:02 Chuck Aude [this message]
2003-07-18 21:50 ` Andrew Cagney
2003-07-21 16:24 ` Chuck Aude
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=3F1819F0.2060606@legato.com \
--to=caude@legato.com \
--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