Closed
Bug 1055242
Opened 11 years ago
Closed 8 years ago
[DeviceStorage] Add some logging
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dhylands, Unassigned)
Details
Device Storage currently has almost no logging.
I'd really like to see the ability to have some runtime logging turned on/off.
The types of logging I'd like to see:
1 - API - For each API function, be able to see that the function was called, and the important arguments (i.e. filename). It should also log the success/failure of each API.
2 - IPC - Since device storage is split between child/process, it would also be useful to be able to trace the child/parent interactions
3 - Detailed - For some APIs, like Enumerate, which can produce copious amounts of output, having a separate control to be able to see inidividual files which are processed.
I know on several occaisons, I've had to work with bugs where being able to turn on some logging would have dramatically sped up the bug discovery, and it seems like every time I invetigate, I need to add a bunch of printfs and rebuild rather than just turning something on.
This would also be extremely useful for JS developers (gaia app developers) who are exploring the device storage API and being able to turn on some logging withoug having to rebuild gecko.
Comment 1•8 years ago
|
||
Cleaning up Device Interfaces component, and mass-marking old FxOS bugs as incomplete.
If any of these bugs are still valid, please let me know.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•