after gc hooks inconsistency...

[Dirk Herrmann <dirk at ida dot ing dot tu-bs dot de>]

Hi!

While experimenting with cell access debugging, I realized the following
inconsistency between the handling of the scheme level after-gc-hook and
the C level scm_after_gc_c_hook:

The gc takes a short exit if (!scm_stack_base || scm_block_gc).  However,
even if the short exit is taken, the scheme level after-gc-hook is run, in
contrast to the C level hook, which is only run after a full gc.  (If
you'd like to verify this, you will have to know that the scheme level
hook is run indirectly via the scm_gc_async).

This seems to be a bug.

Best regards
Dirk