1863492 - Add nsAutoTraceFailure stack class for exact tracing of failures

Status: RESOLVED WONTFIX

(Core :: XPCOM, task, P3)

Description

[Jan Varga [:janv]]

nsAutoTraceFailure should serve as a concrete helper for tracing nsresult errors.

Comment 1

[Jan Varga [:janv]]

Attachment: Bug 1863492 - Add nsAutoTraceFailure stack class for exact tracing of failures; r=#xpcom-reviewers

Depends on D192937

Comment 2

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1863492 - Made trace results testable r=xpcom-reviewers

Comment 3

[Michael van Straten [:michael]]

Attachment: Bug 1863492 - Refactor error mapping for Windows `ERROR_FILE_CORRUPT` r=#dom-storage,jstutte

Currently, Windows ERROR_FILE_CORRUPT is mapped to NS_ERROR_FILE_FS_CORRUPTED in our codebase. This mapping is utilized in various checks, including directory entry iteration. This commit refactors the error mapping to distinguish between NS_ERROR_FILE_FS_CORRUPTED and NS_ERROR_FILE_CORRUPTED specifically for cases such as iterating over directory entries. This change is aimed at providing more precise handling of file system corruption issues, improving the accuracy of error reactions during directory operations.

Comment 4

[Phabricator Automation]

Comment on attachment 9369469 [details]
Bug 1863492 - Refactor error mapping for Windows ERROR_FILE_CORRUPT r=#dom-storage,jstutte

Revision D196869 was moved to bug 1870868. Setting attachment 9369469 [details] to obsolete.

Comment 5

[Michael van Straten [:michael]]

Attachment: WIP: Bug 1863492 - Add more tests for AutoTraceFailure stack class r=jari

Comment 6

[Jan Varga [:janv]]

Attachment: Bug 1863492 - Potential cross thread tracing (async propagation); r=#dom-storage

Comment 7

[Jan Varga [:janv]]

This was just an experiment