From: Vladimir Prus <vladimir@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 4/8] Types GC [varobj_list to all_root_varobjs]
Date: Tue, 07 Jul 2009 08:54:00 -0000 [thread overview]
Message-ID: <200907071254.40994.vladimir@codesourcery.com> (raw)
In-Reply-To: <20090704210912.GA1600@host0.dyn.jankratochvil.net>
[-- Attachment #1: Type: Text/Plain, Size: 1626 bytes --]
On Sunday 05 July 2009 Jan Kratochvil wrote:
> On Thu, 02 Jul 2009 12:09:39 +0200, Vladimir Prus wrote:
> > On Thursday 02 July 2009 Jan Kratochvil wrote:
> > > Is it OK to check it in, Vladimir? The patch would go in unchanged:
> > > http://sourceware.org/ml/gdb-patches/2009-05/msg00547.html
> >
> > Is this cleanup-only patch?
>
> Yes.
>
> > I am a bit concerned that it appears to increase code size,
>
> all_root_varobjs fully replaced the varobj_list function which just could not
> be deleted as it was still used by varobj_invalidate. varobj_invalidate was
> rewritten in a later patch where varobj_list could be finally dropped:
> [patch 8/8] Types GC [varobj]
> http://sourceware.org/ml/gdb-patches/2009-05/msg00551.html
Is that patch awaiting review, or some newer version is forthcoming?
> > > The `floating' lockup will get fixed by a later patch using this new
> > > all_root_varobjs function. A testcase for it was in a now-obsolete patch:
> > > [patch] Fix gdb.mi hang on floating VAROBJs
> > > http://sourceware.org/ml/gdb-patches/2009-05/msg00433.html
> > > This patch itself still does not fix it.
> >
> > IIUC, the varobj_invalidate problem can be fixed with a small patch below.
>
> Yes, such patch works.
>
> Sending also a code style fixup on top of your fix to make the code more safe
> preventing such errors in the future.
>
> Please provide a ChangeLog entry to your fix, check it in
It now checked in, as attached.
> and approve the
> fixup + a testcase below.
This is OK, thanks.
> The all_root_varobjs patch / VEC rewrite I will re-send afterwards.
OK.
Thanks,
Volodya
[-- Attachment #2: hang.diff --]
[-- Type: text/x-patch, Size: 1288 bytes --]
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.10694
diff -u -p -r1.10694 ChangeLog
--- ChangeLog 7 Jul 2009 08:47:09 -0000 1.10694
+++ ChangeLog 7 Jul 2009 08:50:02 -0000
@@ -1,5 +1,12 @@
2009-07-07 Vladimir Prus <vladimir@codesourcery.com>
+ Fix hang in floating varobjs.
+
+ * varob.c (varobj_invalidate): Advance to next
+ element when processing floating varobj.
+
+2009-07-07 Vladimir Prus <vladimir@codesourcery.com>
+
* varobj.c: Remove unnecessary include.
2009-07-07 Tristan Gingold <gingold@adacore.com>
Index: varobj.c
===================================================================
RCS file: /cvs/src/src/gdb/varobj.c,v
retrieving revision 1.140
diff -u -p -r1.140 varobj.c
--- varobj.c 7 Jul 2009 08:47:10 -0000 1.140
+++ varobj.c 7 Jul 2009 08:50:02 -0000
@@ -3231,8 +3231,10 @@ varobj_invalidate (void)
/* Floating varobjs are reparsed on each stop, so we don't care if
the presently parsed expression refers to something that's gone.
*/
- if ((*varp)->root->floating)
+ if ((*varp)->root->floating) {
+ varp++;
continue;
+ }
/* global var must be re-evaluated. */
if ((*varp)->root->valid_block == NULL)
next prev parent reply other threads:[~2009-07-07 8:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 8:02 Jan Kratochvil
2009-06-09 20:50 ` Tom Tromey
2009-07-02 8:39 ` Jan Kratochvil
2009-07-02 10:09 ` Vladimir Prus
2009-07-04 21:11 ` Jan Kratochvil
2009-07-07 8:54 ` Vladimir Prus [this message]
2009-07-07 9:32 ` Jan Kratochvil
2009-07-10 20:17 ` [patch 0/4] varobj_list replacement [Re: [patch 4/8] Types GC [varobj_list to all_root_varobjs]] Jan Kratochvil
2009-07-29 21:34 ` Tom Tromey
2009-07-30 8:46 ` Vladimir Prus
2009-07-30 14:00 ` Jan Kratochvil
2009-07-30 15:13 ` Vladimir Prus
2009-07-30 15:16 ` Jan Kratochvil
2009-07-10 20:18 ` [patch 1/4] varobj_list replacement, choice 1 of 3: VEC_safe_push + VEC_unordered_remove Jan Kratochvil
2009-07-10 20:21 ` [patch 2/4] varobj_list replacement, choice 2 of 3: VEC_safe_insert + VEC_ordered_remove Jan Kratochvil
2009-07-10 21:11 ` [patch 3/4] varobj_list replacement, choice 3 of 3: Iterator Jan Kratochvil
2009-07-10 22:12 ` [patch 4/4] varobj_list replacement, choice 3 of 3: Iterator optimization Jan Kratochvil
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=200907071254.40994.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.com \
/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