This is the mail archive of the gdb-patches@sourceware.org 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: MI: frozen variable objects

From: Greg Watson <g dot watson at computer dot org>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Vladimir Prus <ghost at cs dot msu dot su>, gdb-patches at sources dot redhat dot com
Date: Fri, 17 Nov 2006 08:26:01 -0700
Subject: Re: MI: frozen variable objects
References: <200611161547.46997.vladimir@codesourcery.com> <AA29CD66-FC7C-4C4E-B36A-7945B03AC283@computer.org> <ejibjq$lu6$1@sea.gmane.org> <37D0E16F-2E33-47F4-9121-FC9125174F20@computer.org> <20061117151519.GA31319@nevyn.them.org>

On Nov 17, 2006, at 8:15 AM, Daniel Jacobowitz wrote:

Incidentally, we moved away from the '-var-update *' approach because
it causes gdb 6.5 to crash in certain situations under Linux.


I hope you'll forgive me for saying that that's infuriating behavior.
The CDT developers seem to do it too.  I don't believe you've reported
this bug; therefore it will never be fixed, and folklore will
propogate that -var-update * is unusable.

Bug #'s 2188 and 2190.

Greg

Follow-Ups:
- Re: MI: frozen variable objects
  - From: Daniel Jacobowitz

References:
- MI: frozen variable objects
  - From: Vladimir Prus
- Re: MI: frozen variable objects
  - From: Greg Watson
- Re: MI: frozen variable objects
  - From: Vladimir Prus
- Re: MI: frozen variable objects
  - From: Greg Watson
- Re: MI: frozen variable objects
  - From: Daniel Jacobowitz

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