preprocessor/6084: cpp Segmentation Fault

[Gerwin, Joshua A]

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

From: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com>
To: "'Richard Henderson'" <rth@redhat.com>
Cc: "'Neil Booth'" <neil@daikokuya.demon.co.uk>,
   "'Phil Edwards'"<phil@jaj.com>, joshg@hf.intel.com, gcc-gnats@gcc.gnu.org,
   rnesius@ichips.intel.com, "Nguyen, Tuan" <tuan.nguyen@intel.com>,
   gcc-bugs@gcc.gnu.org
Subject: RE: preprocessor/6084: cpp Segmentation Fault
Date: Mon, 15 Apr 2002 19:38:17 -0700

 > -----Original Message-----
 > From: Richard Henderson [mailto:rth@redhat.com]
 > Sent: Monday, April 15, 2002 6:06 PM
 > To: Gerwin, Joshua A
 > Cc: 'Neil Booth'; 'Phil Edwards'; joshg@hf.intel.com;
 > gcc-gnats@gcc.gnu.org; rnesius@ichips.intel.com; Nguyen, Tuan;
 > gcc-bugs@gcc.gnu.org
 > Subject: Re: preprocessor/6084: cpp Segmentation Fault
 > 
 > 
 > On Mon, Apr 15, 2002 at 11:25:25AM -0700, Gerwin, Joshua A wrote:
 > > (gdb) break maybe_print_line
 > > Cannot access memory at address 0x3c28
 > 
 > You built the compiler as a 64-bit binary didn't you?
 
 Clearly this is something not to be taken on lightly...Actually, a co-worker
 built the compiler, it is 64-bit. I did build the debugger as 64-bit,
 though.  
 
 > 
 > (1) 64-bit sparc code isn't stable in gcc 3.0,
 
 Oops... 
 
 > (2) Use -mcmodel=medlow to link the application below 4GB so
 >     that stabs debugging can function properly.
 > 
 
 Thanks.  This could help quite a bit.  
 
 > 
 > r~
 > 
 
 Josh Gerwin, System Programmer/Analyst
 joshua.a.gerwin@intel.com
 Intel Corp.
 NorthWest Engineering Computing