Closed
Bug 1426271
Opened 8 years ago
Closed 8 years ago
ASAN_OPTIONS=log_path='<path>' does not work on Windows
Categories
(Core :: General, enhancement)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox59 | --- | affected |
People
(Reporter: tsmith, Unassigned)
References
Details
We use the log_path option in automation to help manage logs.
When setting the env var to say:
ASAN_OPTIONS=log_path='c:\\users\\user\\appdata\\local\\temp\\ffplogs_feeatz\\ffp_asan_7528.log'
I see the following error:
ERROR: Can't open file: c:\\users\\user\\appdata\\local\\temp\\ffplogs_feeatz\\ffp_asan_7528.log.1040
The directory does exist. I have tried absolute paths and relative paths no luck.
| Reporter | ||
Comment 1•8 years ago
|
||
If I don't set ASAN_OPTIONS=log_path everything works as expected but the log goes to stderr.
If I set ASAN_OPTIONS=log_path and e10s is enabled I get the error from the initial report
If I set ASAN_OPTIONS=log_path and e10s is disabled I get a log file but it is unsymbolized
| Reporter | ||
Comment 3•8 years ago
|
||
MOZ_DISABLE_CONTENT_SANDBOX seems to do what I want. Thanks!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•