Re: Firefox command seems to be a wrapper
On 7/20/19 9:04 AM, Mahmood Naderan wrote:
However, I am not sure if the tracer logs *the process that fetches data
from web* or not.
Using the definite article ("the") there, is fundamentally wrong.
When you load a web page in Firefox, there are at least 2 processes
involved in "fetching data from web", possibly more, depending on the
exact configuration. At the very least there is the process where the
actual socket access happens (which is probably the "parent" Firefox
process, which is the first one that starts, in your case), but which
data should be fetched and what's done with it is largely determined in
a different ("child") process.
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Re: Firefox command seems to be a wrapper
Mike, I even tried that. The command /usr/lib64/firefox/firefox www.google.com will spawn multiple processes. As I tried with my tracer, I see that the above process executes instructions even after the firefox window is opened and google page is fetched. However, I am not sure if the tracer logs *the process that fetches data from web* or not. Hope that I stated the problem clearly. Regards, Mahmood On Wed, Jul 17, 2019 at 2:12 AM Mike Hommey wrote: > > I'm not sure how you jumped from my response to building from source, but > what I'm saying is that you probably can run /usr/lib64/firefox/firefox. > > Mike > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Firefox command seems to be a wrapper
On Tue, Jul 16, 2019 at 06:44:36AM +0430, Mahmood Naderan wrote: > OK I will try the source compilation. Please let me know if I have use > specific options for my purpose or not. I'm not sure how you jumped from my response to building from source, but what I'm saying is that you probably can run /usr/lib64/firefox/firefox. Mike ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Firefox command seems to be a wrapper
OK I will try the source compilation. Please let me know if I have use specific options for my purpose or not. On Tue, Jul 16, 2019, 02:20 Mike Hommey wrote: > > 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
Re: Firefox command seems to be a wrapper
>Is just "the main firefox" enough for the tracing you want to do? I am looking for way to run "firefox www.google.com" and then see firefox opens that shows google web page. >Note >that all the website rendering happens in separate processes, not the >Firefox UI process. Maybe that is true for web pages with multitype contents, e.g. text, flash, video, ... So, if it is possible to launch a firefox command to fetch the text of websites, e.g. amazon, then that will be good (not the best I want). Regards, Mahmood ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Firefox command seems to be a wrapper
OK I will try the source compilation. Please let me know if I have use specific options for my purpose or not. If I build from source, can I do what I want? > 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
Re: Firefox command seems to be a wrapper
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/2S+ 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
Re: Firefox command seems to be a wrapper
On 7/15/19 11:51 AM, Mahmood Naderan wrote: Overall, firefox command is a wrapper and I am seeking for a way to access the main firefox. Is just "the main firefox" enough for the tracing you want to do? Note that all the website rendering happens in separate processes, not the Firefox UI process. So chances are you want to be able to follow subprocess executions in your tracing tool anyway... -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
