🚀 go-pugleaf

I'm going a bit nuts here trying to get 'bbfig' really debugged and
working, and the current anomaly is driving me nuts.  Simply put: is it
possible to get a limitcheck on an already flattened 'flattenpath'?
I'm chasing a problem where the apparent flow of things is:

       strokepath
       flattenpath
       ...lots of irrelevant stuff
       flattenpath

and the second flattenpath fails [I don't actually know why, because it
is in a 'stopped' protected region [in both cases, it turns out], and
what I know is that the stopped is failing, and limitcheck is the only
listed error for flattenpath.  I'd have thought that doing a second
flattenpath would be a no-op... is there something obvious I'm missing
or might this be some kind of obscure bug (horrors!) in the PS
interpreter I'm using [UltraScript on an Imagen printer].

Thanks...
  /Bernie\

ps, this is kind of irrelevant to this posting, but.... if you cared
about the 'tracing' package I posted yesterday, I've upgraded it some
and so give me a shout if you'd like the improved version.  The
improvement is that the tracedump stuff now 'showpage's on its own, so
you can see all of your cached stuff, instead of having it go off the
bottom of the page after 60-odd lines.  Stuff added in desperation in
trying to puzzle out a MacDraw mess that spawned eight pages of tracing
diagnostic info.... /b\