This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB 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: gdb/842: gdb gets in infinit loop in finish_cv_type


The following reply was made to PR gdb/842; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: aysuov@hotmail.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/842: gdb gets in infinit loop in finish_cv_type
Date: Wed, 20 Nov 2002 17:35:49 -0500

 On Wed, Nov 20, 2002 at 10:11:09PM -0000, aysuov@hotmail.com wrote:
 > 
 > >Number:         842
 > >Category:       gdb
 > >Synopsis:       gdb gets in infinit loop in finish_cv_type
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Wed Nov 20 14:18:01 PST 2002
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     aysuov@hotmail.com
 > >Release:        5.2.1
 > >Organization:
 > >Environment:
 > Linux 2.4.18 i686
 > >Description:
 > gdb gets in infinit loop in finish_cv_type. 
 > >How-To-Repeat:
 > 
 > >Fix:
 > The simple fix that I did seems to eliminate the problem but I am not sure if that's the right fix. If the line 493 of gdbtypes.c looks like this:
 >   while ( (ntype != TYPE_CV_TYPE (ntype)) && (ntype = TYPE_CV_TYPE (ntype)) != type)
 > then it works. See the attached file with the fix.
 
 That means the chain got corrupted.  But the entire problem is gone in
 the current release; please get a 5.2.90 (pre-5.3) snapshot from
 ftp://sources.redhat.com/pub/gdb/snapshots/
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


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