Re: Infinite loop in make_cv_type

[Daniel Jacobowitz <drow@mvista.com>]

On Fri, Feb 22, 2002 at 07:44:44PM +0000, Richard Earnshaw wrote:
> 
> > Any suggestions as to how the stabs reader might be getting ahead of 
> > itself?  Is there another function that might be returning the stabs 
> > string?  I don't think dbx_next_symbol_text has ever returned this 
> > earlier...
> 
> Dead simple really.  The stabs on the ARM are broken into very short 
> strings for historical reasons (there was once an assembler that couldn't 
> cope with stabs strings of more than about 100 characters).  We are simply 
> running off the end of a stabs string without calling STABS_CONTINUE.  
> Thus we end up parsing the following string twice: once on the overrun and 
> the second when dbx_next_symbol_text returns it.
> 
> OK to apply?
> 
> R.
> 
> <date>  Richard Earnshaw  (rearnsha@arm.com)
> 
> 	* stabsread.c (read_member_functions): Call STABS_CONTINUE after 
> 	skipping a method.
> 
> 

My fault, it figures.  I've never been clear when STABS_CONTINUE is
actually necessary.  I can't approve it, but this looks good to me.

The rest of the problems you found should be fixed, but are not urgent;
I'll try to get to gdb/277 in the next few weeks...

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer