You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error subclasses have no .stack — 93 extends Error in the cc bundle, stack traces missing from user-facing errors #9410
classAextendsError{}newA("x").stack// node: string perry: undefinedObject.prototype.toString.call(newA("x"))// node: "[object Error]" perry: "[object Object]"newError("x").stack// both: string <-- the BASE class is fine
Only subclasses are affected, which localises this to whatever Error construction does for a derived class.
User-visible consequence in cc
claude doctor and claude --max-budget-usd abc print, under node, ~10 real frames with source positions — 14,573 bytes of stderr. Under perry the same commands print - at <anonymous> and 120 bytes. The bundle has 93 extends Error classes and 106 .stack uses, so essentially every diagnostic cc emits loses its trace.
The toString tag divergence is likely the same root: a derived Error isn't being branded as an Error.
Found by a differential stress-test of claude-code under perry.
Activity
fix(runtime): an Error subclass has a .stack and an [object Error] ta…
proggeramlug commentedon Sep 2, 2026
Closing: fixed in #9443 (landed #9432); real frame names followed in #9521.