process: expose enhanced stack trace to uncaughtException handlers

[santusht06]

Summary

Fixes #55838.

When an EventEmitter emits an unhandled 'error' event, V8 appends an
Emitted 'error' event at: frame to the stack trace via the inspector stack
trace enhancer. However, this enhancement was applied only during the default
fatal-exception path (inside fatalException()), after the
uncaughtException and uncaughtExceptionMonitor handlers had already been
invoked, so user-registered handlers never saw the enriched stack.

Root Cause

fatalExceptionStackEnhancers.beforeInspector() was called inside
fatalException() — the final, process-exiting path — but not inside
createOnGlobalUncaughtException() which fires the user handlers first.

Fix

Call fatalExceptionStackEnhancers.beforeInspector(er) inside
createOnGlobalUncaughtException() before emitting to
uncaughtExceptionMonitor and uncaughtException. The guard
er != null && typeof er === 'object' safely handles primitive throws.

Testing

Added test/parallel/test-process-uncaught-exception-enhanced-stack.js which
verifies both a plain EventEmitter and a subclass expose the Emitted 'error' event at:
frame to both handlers.

$ ./out/Release/node test/parallel/test-process-uncaught-exception-enhanced-stack.js
# exit 0 ✅

Signed-off-by: santusht06 115890693+santusht06@users.noreply.github.com
Assisted-by: Antigravity

[nodejs-github-bot]

Review requested:

• @nodejs/loaders
• @nodejs/performance

[github-actions]

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

• the guide for first-time contributors
• the contribution and automation policies
• the pull request guide
• the AI use policy
• the Code of Conduct

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

Caution

AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context.

[santusht06]

I used AI assistance to help prepare this PR, personally verified and tested all changes locally, and take full responsibility for this submission.

[MikeMcC399]

The recommendations in:

• Guides and FAQs for first-time contributors

advise you should tackle only one issue at a time and that you should not open any new PRs until your first PR has been approved.

You already have other unapproved PRs open:

• worker: define Symbol.toStringTag on messaging prototypes #65531
• module: forward execArgv to ESM loader hook worker #65543
• process: expose enhanced stack trace to uncaughtException handlers #65580

[santusht06]

Apologies for the noise and duplicate PR! Closing this as it is an accidental duplicate of #65580. Thank you for pointing that out, @MikeMcC399.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.17%. Comparing base (7991140) to head (2fcd2bd).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #65849      +/-   ##
==========================================
- Coverage   90.19%   90.17%   -0.02%     
==========================================
  Files         771      771              
  Lines      264622   264627       +5     
  Branches    50223    50225       +2     
==========================================
- Hits       238663   238634      -29     
- Misses      16965    16974       +9     
- Partials     8994     9019      +25     

Files with missing lines	Coverage Δ
lib/internal/process/execution.js	99.23% <100.00%> (-0.77%)	⬇️

... and 33 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.