Open Bug 1863492 Opened 5 months ago Updated 23 hours ago

Add nsAutoTraceFailure stack class for exact tracing of failures

Categories

(Core :: XPCOM, task, P2)

task

Tracking

()

ASSIGNED

People

(Reporter: janv, Assigned: janv)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Attachments

(3 files, 2 obsolete files)

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

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 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.

Attachment #9369469 - Attachment is obsolete: true
Attachment #9369251 - Attachment is obsolete: true
Blocks: 1891020
No longer blocks: 1741408
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: