From: Andrew Cagney <ac131313@redhat.com>
To: Mikhail Teterin <mi+kde@aldan.algebra.com>
Cc: gdb@sources.redhat.com
Subject: Re: More on the Solaris 64 bit troubles
Date: Mon, 31 Mar 2003 05:46:00 -0000 [thread overview]
Message-ID: <3E87D610.6010403@redhat.com> (raw)
In-Reply-To: <200303121027.01420@aldan>
> On Wednesday 12 March 2003 10:21 am, Andrew Cagney wrote:
> = > It happens when I try to use the 64-bit compiled gdb executable to debug
> = > a 32-bit executable. I don't see why this should not work...
> = >
> = > It dies, because when the second gdbarch structure is initialized
> = > (don't why it does it twice) the set_gdbarch_num_regs is not called and
> = > num_regs fields stays at the unitialized -1 :-(
> =
> = At present, on Solaris, the only way to debug a 32 bit executable is to
> = build a 32 bit GDB. GDB needs something (thread library?) and that only
> = works when built/linked 32 bit on a 32 bit executable.
>
> Thanks! I'll try that. Too bad, because all my Tcl (itcl, tix, etc.)
> are built for 64-bit, so I'll have to build a standalone insight-only
> distributions instead of sharing them.
>
> However, it seems to be dying long before getting to the thread library.
>
> While trying to use the second `struct gdbarch' -- why does it need more
> than one anyway?
>
> Also I have a bunch of patches for 5.3, which remove warnings raised by
> the Solaris' compiler (and a couple of bugs uncovered through them).
> Should I post them here, or send to someone directly?
Hmm, an update. I've been corrected. Apparently 64 bit GDB:
CFLAGS='-g -m64 -O' .../configure
is ment to be able to debug either a 32 or 64 bit binary, so there has
been bit rot :-(
Andrew
prev parent reply other threads:[~2003-03-31 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 2:54 Mikhail Teterin
2003-03-12 15:21 ` Andrew Cagney
2003-03-12 15:27 ` Mikhail Teterin
2003-03-31 5:46 ` Andrew Cagney [this message]
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=3E87D610.6010403@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mi+kde@aldan.algebra.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