From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22622 invoked by alias); 15 Apr 2002 19:06:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 22601 invoked by uid 71); 15 Apr 2002 19:06:01 -0000 Date: Mon, 15 Apr 2002 12:06:00 -0000 Message-ID: <20020415190601.22600.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: 'Neil Booth' Subject: Re: preprocessor/6084: cpp Segmentation Fault Reply-To: 'Neil Booth' X-SW-Source: 2002-04/txt/msg00786.txt.bz2 List-Id: The following reply was made to PR preprocessor/6084; it has been noted by GNATS. From: 'Neil Booth' To: "Gerwin, Joshua A" , gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Cc: Subject: Re: preprocessor/6084: cpp Segmentation Fault Date: Mon, 15 Apr 2002 19:56:55 +0100 Gerwin, Joshua A wrote:- > I would if I could, but the debugger often reports back that it can't get at > the variables in question. > > (gdb) info mem > Num Enb Low Addr High Addr Attrs > 2 y 0x000000010000349c 0x0000000100012344 rw nocache > 1 y 0x000000000011b018 0x0000000000120000 rw nocache > (gdb) break maybe_print_line > Cannot access memory at address 0x3c28 > > for instance. This prohibition is applied to display, print, and trace as > well. I've had some success in getting DDD to sneak in there, and I'll see > if I can convince it can put a display on the print structure. Does it occur if you compile cpp0 without optimization? Neil.