On Tuesday, July 16, 2019 at 12:51:28 AM UTC+9, Mahmood Naderan wrote: > > Hi, > > I want to analyze firefox by tracing instruction footprints as I am > working with that. Problem is that when I pass /usr/bin/firefox (or simply > firefox) to the tracer, it stops logging as soon as the main window opens. > > As I looked further, I have noticed that another process is launched and > that is what I have to analyze. I also have noticed that /usr/bin/firefox > isn't present in the output of ps command. > > # ps aux | grep firefox > mahmood 8358 61.8 0.3 2679204 201348 pts/1 Sl+ 12:58 0:03 > /usr/lib64/firefox/firefox > mahmood 8494 20.0 0.1 2351288 69648 pts/1 Sl+ 12:58 0:00 > /usr/lib64/firefox/plugin-container -greomni /usr/lib64/firefox/omni.ja > -appomni /usr/lib64/firefox/browser/omni.ja -appdir > /usr/lib64/firefox/browser 8358 tab > root 8633 0.0 0.0 112664 972 pts/2 S+ 12:58 0:00 grep > --color=auto firefox > > Ignoring the absence of /usr/bin/firefox, when I run > /usr/lib64/firefox/plugin-container -greomni /usr/lib64/firefox/omni.ja > -appomni /usr/lib64/firefox/browser/omni.ja -appdir > /usr/lib64/firefox/browser 8358 tab in the terminal, I get shared library > access error. > > Overall, firefox command is a wrapper and I am seeking for a way to access > the main firefox. I also tried > > export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/firefox > > but wasn't successful. Any idea?
It looks like your Linux distro has set their own wrapper for Firefox. That's not something that comes from Firefox itself. So looking at your paths, this would suggest /usr/lib64/firefox/firefox is the real, non-wrapped, Firefox binary. As for whether you'd be losing anything by not using the wrapper, that's a question for your distro. Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
