From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [4/5] Types reference counting [varobj-validation]
Date: Sat, 11 Apr 2009 11:28:00 -0000 [thread overview]
Message-ID: <837i1r2zwg.fsf@gnu.org> (raw)
In-Reply-To: <20090411102215.GE32624@host0.dyn.jankratochvil.net>
> Date: Sat, 11 Apr 2009 12:22:15 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> currently GDB was sometimes keeping varobjs with stale references to objfiles.
> With the changes GDB started crashing on this problem.
>
> +/* Invalidate the varobjs that are tied to the specified OBJFILE. Call this
> + function before you start removing OBJFILE.
> +
> + Call varobj_revalidate after the OBJFILEs updates get finished.
Thanks.
Should this be added to gdbint.texinfo?
next prev parent reply other threads:[~2009-04-11 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 10:22 Jan Kratochvil
2009-04-11 11:28 ` Eli Zaretskii [this message]
2009-04-11 18:20 ` Jan Kratochvil
2009-04-16 21:54 ` Tom Tromey
2009-04-22 20:14 ` Jan Kratochvil
2009-05-25 8:18 ` obsolete: " 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=837i1r2zwg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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