Running JimDB with MOZ_LINKER_ONDEMAND=0 www.google.ca hangs

RESOLVED INVALID

Status

()

RESOLVED INVALID
5 years ago
5 years ago

People

(Reporter: kats, Assigned: jchen)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

STR:
1. Run bin/gdb
2. Hit option "2" (to provide args/environment)
3. Enter "MOZ_LINKER_ONDEMAND=0 www.google.ca"

Expected results:
JimDB starts Fennec with on-demand decompression disabled and loads google

Actual results:
Fennec starts, crashes, starts again, JimDB hangs
(Assignee)

Updated

5 years ago
Assignee: nobody → nchen
(Assignee)

Comment 1

5 years ago
Were you using your N10? On my N4 it seems to work (both root and non-root). Also MOZ_LINKER_ONDEMAND shouldn't be needed in most cases with recent versions of JimDB.
This was on my N4. If I run without MOZ_LINKERD_ONDEMAND I still get SIGSEGVs everywhere and have to do the "handle sigsegv nostop noprint" thing to make it usable. It might be that I just need to rebuild jimdb from the latest source again. I'll kick that off and let you know.
Hm. I rebuilt gdb and updated my utils folder and still get the same behaviour. I also see the behaviour if I just try to run bin/gdb and choose option 1, which is weird. Maybe this is wonkiness with android 4.3. I don't remember if I updated to 4.3 before or after I filed this bug.
After some debugging over IRC it turns out this is because I wasn't properly rooted. Using TWRP and SuperSU 1.65 got me a good root shell and this problem went away.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.