[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    Re: More on the Solaris 64 bit troubles
From:       Andrew Cagney <ac131313 () redhat ! com>
Date:       2003-03-31 5:45:52
Message-ID: 3E87D610.6010403 () redhat ! com
[Download RAW message or body]

> 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 in list] [next in list] [prev in thread] [next in thread]