This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: wrong-code regressions review

From: Daniel Jacobowitz <drow at false dot org>
To: Bradley Lucier <lucier at math dot purdue dot edu>
Cc: Giovanni Bajo <rasky at develer dot com>, gcc at gcc dot gnu dot org
Date: Wed, 15 Dec 2004 16:29:35 -0500
Subject: Re: wrong-code regressions review
References: <95C1438C-4E38-11D9-A170-003065BA681E@math.purdue.edu> <056701c4e2a7$bf87a450$f503030a@mimas> <71B2E864-4EAB-11D9-A170-003065BA681E@math.purdue.edu> <063601c4e2b8$d52d1d60$f503030a@mimas> <96631328-4EDF-11D9-B977-000A958F150A@math.purdue.edu>

On Wed, Dec 15, 2004 at 04:23:39PM -0500, Bradley Lucier wrote:
> (gdb) info locals
> ___pc = dwarf2_read_address: Corrupted DWARF expression.

This is some new bug in GDB I haven't seen before.

> Program received signal SIGSEGV, Segmentation fault.
> 0x081541ae in ___H__20___front (___ps=0x8481ea0) at _front.c:7075
> 7075       ___SET_R2(___FIXMAX(___R3,___R2))
> (gdb) info locals
> ___pc = 137816529
> ___start = 137799889
> ___temp = Variable "___temp" is not available.

This means GDB thinks it is in a call clobbered register.  It shouldn't
happen in the topmost frame, so I don't know what's wrong.  I'd have to
see the debug info.

-- 
Daniel Jacobowitz

Follow-Ups:
- Re: wrong-code regressions review
  - From: Bradley Lucier

References:
- Re: wrong-code regressions review
  - From: Bradley Lucier
- Re: wrong-code regressions review
  - From: Giovanni Bajo
- Re: wrong-code regressions review
  - From: Bradley Lucier
- Re: wrong-code regressions review
  - From: Giovanni Bajo
- Re: wrong-code regressions review
  - From: Bradley Lucier

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]