Re: RFC: change debug pseudo-type for vectors

[Geoff Keating <geoffk at geoffk dot org>]

> Date: Thu, 6 Sep 2001 08:01:19 -0400
> From: DJ Delorie <dj@redhat.com>
> CC: geoffk@geoffk.org, gcc-patches@gcc.gnu.org
> X-OriginalArrivalTime: 06 Sep 2001 12:01:21.0796 (UTC) FILETIME=[A505B440:01C136CB]
> 
> 
> > Errr, GDB will run into the same exact problem, when passing it as
> > an argument to functions you calll.
> 
> So the basic answer is "sorry, you're screwed" ?  I really don't want
> to tell a customer that when the information gdb is printing is so
> obviously wrong.

The right thing is to change GDB so that it recognises this particular
type and prints out more specialised information, like

<type> = vector int 4

or something.  

There's nothing obviously wrong about representing the type as a
structure containing an array containing four ints---after all, that
correctly describes both its layout and the way it is treated---it's
just not what the customer was expecting.  GDB often sees fortran
types, particularly common blocks, in weird ways too.

-- 
- Geoffrey Keating <geoffk@geoffk.org>