From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0
Date: Wed, 08 Sep 2010 12:26:00 -0000 [thread overview]
Message-ID: <m3vd6hwfbk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100906094821.GA20484@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Mon, 6 Sep 2010 11:48:21 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> This means only one CU is guaranteed to be read in at one time.
Jan> And when you hold that CU you must not call any GDB function as
Jan> this function can (upon a change in the future) request its own CU
Jan> and thus invalidate CU at the caller. I find it as a too fragile
Jan> policy.
Ok, I understand what you are saying.
You could also have a global to suppress aging, that is set on entry to
the DWARF module and reset on exit.
Your way is probably clearer.
Jan> Still I find it even ineffective. Regular aging means CUs get
Jan> flushed even if only a few of them is now read-in.
I agree.
Tom
prev parent reply other threads:[~2010-09-07 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 18:50 Jan Kratochvil
2010-08-23 19:30 ` Doug Evans
2010-09-02 17:13 ` Jan Kratochvil
2010-09-02 19:33 ` Doug Evans
2011-07-13 15:21 ` [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0 #2 Jan Kratochvil
2011-07-19 20:55 ` Jan Kratochvil
2010-09-03 15:42 ` [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0 Tom Tromey
2010-09-03 16:14 ` Jan Kratochvil
2010-09-03 18:06 ` Doug Evans
2010-09-06 11:29 ` Jan Kratochvil
2010-09-06 22:29 ` Doug Evans
2010-09-08 12:26 ` Tom Tromey [this message]
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=m3vd6hwfbk.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).