RE: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failu res with -m64

["Boehm, Hans" <hans_boehm@hp.com>]

The following reply was made to PR java/6092; it has been noted by GNATS.

From: "Boehm, Hans" <hans_boehm@hp.com>
To: "Boehm, Hans" <hans_boehm@hp.com>,
        "'tromey@redhat.com'"
	 <tromey@redhat.com>
Cc: "'Kaveh R. Ghazi'" <ghazi@caip.rutgers.edu>,
        "'gcc-gnats@gcc.gnu.org'"
	 <gcc-gnats@gcc.gnu.org>
Subject: RE: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failu
	 	res with -m64
Date: Mon, 15 Apr 2002 20:05:44 -0700

 I just noticed that Linux/SPARC has a similar rule for DATASTART, but it's
 lightly different in the 64 bit case.  As a wild guess, I would try using
 the Linux rule for Solaris as well.  It seems to me that they are probably
 meant to be the same?
 
 Hans
 
 > -----Original Message-----
 > From: Boehm, Hans 
 > I would guess that (b) is the problem here.  It may be that 
 > the data segment in fact starts at a higher address than what 
 > the collector is assuming.  The collector currently assumes 
 > the same spacing between etext and the start of the data 
 > segment as with the 32 bit ABI.  I think this doesn't work 
 > well if the page size exceeds 64K, which may have been 
 > perceived as a problem by the designers of the 64 bit ABI.
 > 
 > If this doesn't lead to a diganosis of the problem, it would 
 > also be very helpful to extract the fault address somehow.  
 > If you can determine the faulting instruction and the 
 > corresponding register contents, that should be fairly easy.  
 > It wasn't clear to me whather gdb is sufficiently functional 
 > to do that.
 > 
 > Hans
 >