From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Berlin <dan@www.cgsoftware.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Berlin <dberlin@redhat.com>, <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] Add support for tracking/evaluating dwarf2 location  expressions
Date: Fri, 06 Apr 2001 12:10:00 -0000
Message-id: <Pine.LNX.4.33.0104061508410.1542-100000@www.cgsoftware.com>
References: <3ACE108C.725903B7@cygnus.com>
X-SW-Source: 2001-04/msg00075.html

On Fri, 6 Apr 2001, Andrew Cagney wrote:

>
> > >   value_ptr stack[64];
> > > Is there a constant for this?  A quick glance at decode_locdesc() and it
> > > has the same hardwired constant.
> > Nobody has ever produced location expressions that need more.
>
> The problem typically isn't with what people are doing intentionally but
> rather unintentionally.  The code opens the way for an input file to
> cause gdb to overflow a buffer and trash its stack.

Well, as I said, it will trash  GCC as well, since they do no range
checking, and have the exact same limit.
But i'll range check it, just the same.

>
> Since we're trying to lessen the likelyhood of GDB corrupting its stack
> and dumping core, I think the code should include some sort of stack
> range check.

As you wish, done in the latest version.
I moved it all into dwarf2eval.c as well.

>
> 	Andrew
>