Re: [patch] Fix DW_OP_call2 and DW_OP_call4 for max-cache-age 0

[Tom Tromey <tromey at redhat dot com>]

>>>>> "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