public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Gerwin, Joshua A" <joshua.a.gerwin@intel.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: preprocessor/6084: cpp Segmentation Fault Date: Mon, 15 Apr 2002 19:46:00 -0000 [thread overview] Message-ID: <20020416024602.4637.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-04-16 2:46 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-15 19:46 Gerwin, Joshua A [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-21 13:34 neil 2002-05-21 13:33 neil 2002-04-17 23:52 neil 2002-04-15 18:06 Richard Henderson 2002-04-15 12:06 'Neil Booth' 2002-04-15 11:36 Gerwin, Joshua A 2002-04-15 11:16 'Neil Booth' 2002-04-15 11:06 Gerwin, Joshua A 2002-04-13 1:26 Phil Edwards 2002-04-13 1:16 Phil Edwards 2002-04-12 22:16 Neil Booth 2002-04-12 16:06 Gerwin, Joshua A 2002-04-12 13:36 Phil Edwards 2002-04-03 22:36 'Neil Booth' 2002-04-03 17:06 Gerwin, Joshua A 2002-04-02 22:36 Neil Booth 2002-03-29 12:16 Neil Booth 2002-03-29 11:36 Gerwin, Joshua A 2002-03-29 0:20 neil
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=20020416024602.4637.qmail@sources.redhat.com \ --to=joshua.a.gerwin@intel.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).