From: Greg Watson <g.watson@computer.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: MI: frozen variable objects
Date: Fri, 17 Nov 2006 15:41:00 -0000 [thread overview]
Message-ID: <B23223AE-822F-4C73-A3DB-F1A39EA2A2B3@computer.org> (raw)
In-Reply-To: <20061117153314.GA32128@nevyn.them.org>
On Nov 17, 2006, at 8:33 AM, Daniel Jacobowitz wrote:
> On Fri, Nov 17, 2006 at 08:26:01AM -0700, Greg Watson wrote:
>>
>> 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.
>
> Ah, I figured those weren't associated. My mistake and apologies. A
> testcase was sent to me for 2188 off-list. I can't reproduce it,
> however.
We'll try and get some better information on reproducing the problem.
Greg
next prev parent reply other threads:[~2006-11-17 15:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 12:48 Vladimir Prus
2006-11-16 13:58 ` Greg Watson
2006-11-16 15:25 ` Frederic RISS
2006-11-16 15:55 ` Daniel Jacobowitz
2006-11-16 16:26 ` Frederic RISS
2006-11-16 16:34 ` Daniel Jacobowitz
2006-11-17 15:21 ` Greg Watson
2006-11-16 18:55 ` Vladimir Prus
2006-11-16 21:36 ` Frédéric Riss
2006-11-17 6:17 ` Vladimir Prus
2006-11-17 8:54 ` Frederic RISS
2006-11-16 18:47 ` Vladimir Prus
2006-11-17 15:09 ` Greg Watson
2006-11-17 15:15 ` Daniel Jacobowitz
2006-11-17 15:26 ` Greg Watson
2006-11-17 15:33 ` Daniel Jacobowitz
2006-11-17 15:41 ` Greg Watson [this message]
2006-11-17 15:45 ` Daniel Jacobowitz
2006-11-17 18:16 ` Daniel Jacobowitz
2006-11-17 15:35 ` Greg Watson
2006-11-17 15:27 ` Vladimir Prus
2006-11-16 21:53 Nick Roberts
2006-11-16 22:00 ` Daniel Jacobowitz
2006-11-16 23:07 ` Nick Roberts
2006-11-17 15:19 ` Daniel Jacobowitz
2006-11-17 20:52 ` Nick Roberts
2006-11-17 21:05 ` Daniel Jacobowitz
2006-11-17 23:12 ` Nick Roberts
2006-11-18 11:00 ` Eli Zaretskii
2006-11-17 6:25 ` Vladimir Prus
2006-11-17 18:14 ` Daniel Jacobowitz
2006-11-18 6:59 Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B23223AE-822F-4C73-A3DB-F1A39EA2A2B3@computer.org \
--to=g.watson@computer.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox