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: Heads Up: Apple Notarized Nightly Builds
I've updated our "Debugging on Mac OS X" MDN page with some information about debugging Mac builds with Notarization and Hardened Runtime restrictions. https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_on_Mac_OS_X#Debugging_Firefox_on_macOS_10.14 Let me know if you have any questions. Thanks, Haik On Wed, Jun 26, 2019 at 1:27 PM Haik Aftandilian wrote: > Release Engineering will soon be turning on Apple Notarization and > Hardened Runtime[1] for Nightly channel builds. See previous discussion[2] > on dev-platform for more information. > > First, I want to recognize that this required a very significant amount of > work from the Release Engineering team to adapt our release pipeline to > support Notarization, especially from Aki Sasaki and Nick Thomas. > > What you need to know as a Firefox Mac developer: > > I) Hardened Runtime and Notarization are not enabled for local builds so > there is no impact to debugging of local builds. We have a bug filed[2] to > enable Hardened Runtime on local builds, but this should not affect > debugging because the debugging restriction only applies to Notarized > applications. > > II) Debugging a Nightly channel build will require disabling Mac System > Integrity Protection[3] (SIP). Nightly channel builds will be signed with > the Hardened Runtime entitlements from the production.entitlements.xml file > from the tree. > > III) try push builds will be signed with Hardened Runtime enabled using > the entitlements from the developer.entitlements.xml file from the tree and > should be debuggable as before. > > For bugs found that appear to be caused by this change, please file under > Core/Widget: Cocoa. > > Haik > > 1. > https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution > 2. > https://groups.google.com/d/msg/mozilla.dev.platform/4VvbvY1Brnw/DWYlj8rhDAAJ > 3. https://bugzilla.mozilla.org/show_bug.cgi?id=1522409 > 4. https://support.apple.com/en-us/HT204899 > ___ 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
Intent to change: dominant-baseline to inherit
In SVG 1.1 dominant-baseline is a reset property. In SVG 2 dominant-baseline's definition changes to inherited. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1353164 Standard: https://www.w3.org/TR/css-inline-3/#propdef-dominant-baseline and https://www.w3.org/TR/SVG2/text.html#DominantBaselineProperty Platform coverage: All platforms using the Gecko rendering engine Target release: Firefox 70 Is this feature enabled by default in sandboxed iframes? Yes Do other browser engines implement this? Chrome has made this change already. web-platform tests: https://searchfox.org/mozilla-central/source/testing/web-platform/tests/css/css-inline Is this feature restricted to secure contexts? No, it's a change to a property we already support in all contexts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
New coverage frontend and zero coverage checker
Hello everyone, We are switching from relying on codecov.io and coveralls.io to our own backend/frontend to handle coverage data. This will allow us to build more features such as filtering coverage results by OS, filtering by test suite, etc.. Moreover, codecov.io and coveralls.io were not able to handle the load of our large repositories. With a custom backend, we now have consistent performance. The code coverage reports now live at https://mozilla.github.io/code-coverage-reports/ (the URL might change, but we will setup a redirect if it does). You can see a graph of the coverage over time (clicking on one of the points of the graph will bring you to that revision), see coverage summaries by directory, see source code with coverage highlight (green for covered, red for uncovered). In a few days, we will stop uploading coverage data to codecov.io and coveralls.io. On a related note, we have recently enabled a new checker in our Review Bot which will warn you if one of the files in your patch is completely uncovered by tests (which might mean that the file should be tested, https://bugzilla.mozilla.org/show_bug.cgi?id=untestedcode-codecoverage, or that the file is dead code, https://bugzilla.mozilla.org/show_bug.cgi?id=deadcode-codecoverage, or that it is tested in a configuration which is not yet supported by code coverage). As usual, you can also browse our full zero coverage report at https://mozilla.github.io/code-coverage-reports/zero_coverage_report.html. - Marco, on behalf of the team (special thanks to Bastien who has been doing most of the work on the new backend/frontend). ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
[desktop] Bugs logged by Desktop Release QA in the last 7 days
Hello, Here's the list of new issues found and filed by the Desktop Release QA team in the last 7 days. Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://tinyurl.com/y39rumr3. Bugs logged by Desktop Release QA in the last 7 days: Core: Audio/Video NEW - https://bugzil.la/1565493 - Jumpy seekbar on http://play.dogmazic.net Toolkit: Downloads API NEW - https://bugzil.la/1564092 - Download - Pause option disabled after Cancel/Retry DevTools: Inspector NEW - https://bugzil.la/1565523 - DevTools inspectors flash on fast scroll DevTools: Inspector: Rules NEW - https://bugzil.la/1564084 - Inactive CSS - tooltips jump around on section zoom This is available as a Bugzilla bug list as well: https://tinyurl.com/y4yjuam3. Regards, Mihai Boldan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
