Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Thu, 02 Jul 2009 10:09:00 -0000	[thread overview]
Message-ID: <200907021409.39886.vladimir@codesourcery.com> (raw)
In-Reply-To: <20090702083705.GA14783@host0.dyn.jankratochvil.net>

On Thursday 02 July 2009 Jan Kratochvil wrote:

> On Tue, 09 Jun 2009 22:50:42 +0200, Tom Tromey wrote:
> > >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> > 
> > Jan> I find the callback based iterator easier to use,
> [...]
> > It seems reasonable to me, though it would be nice to have Volodya's
> > approval.
> 
> Is it OK to check it in, Vladimir?  The patch would go in unchanged:
> 	http://sourceware.org/ml/gdb-patches/2009-05/msg00547.html
> 
> Regression re-tested now on {x86_64,i686}-fedora-linux-gnu.

Is this cleanup-only patch? I am a bit concerned that it appears
to increase code size, and all it does it changes explicit iteration
to callback iteration. Can we just make varobj.c expose vector of
varobjs?

> > Jan> in fact there were bugs due to the
> > Jan> current calling semantics (`floating' lockup, memory leaks).
> > 
> > Details on the bugs that this fixes would be nice.
> > A test case would also be nice, assuming these are testable.
> 
> 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.
Am I missing something? If no, such a patch is not in any way made easier
by callback iteration.

- Volodya

Index: gdb/varobj.c
===================================================================
RCS file: /cvs/src/src/gdb/varobj.c,v
retrieving revision 1.137
diff -u -p -r1.137 varobj.c
--- gdb/varobj.c        30 Jun 2009 09:24:47 -0000      1.137
+++ gdb/varobj.c        2 Jul 2009 10:08:22 -0000
@@ -3225,8 +3225,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)


  reply	other threads:[~2009-07-02 10:09 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 [this message]
2009-07-04 21:11       ` Jan Kratochvil
2009-07-07  8:54         ` Vladimir Prus
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=200907021409.39886.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