FramePointerStackWalk shouldn't take aFirstFramePC
Categories
(Core :: mozglue, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | --- | fixed |
firefox90 | --- | fixed |
People
(Reporter: mozbugz, Assigned: mozbugz)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
In bug 1515229, aFirstFramePC
was added to MozStackWalk()
.
But not to FramePointerStackWalk()
, because it's already given a start frame through aBp
.
However, bug 1515229 mistakenly added aFirstFramePC
to the empty definition of FramePointerStackWalk
(only used on unsupported platforms.)
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Set release status flags based on info from the regressing bug 1515229
Comment 4•4 years ago
|
||
bugherder |
Comment 5•4 years ago
|
||
The patch landed in nightly and beta is affected.
:gerald, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 6•4 years ago
|
||
I don't think it's that important, it's only fixing potential build issues on unsupported platforms. Trivial for anyone to backport if they need it.
Comment 7•4 years ago
|
||
not(Tier 1) != unsupported
Assignee | ||
Comment 8•4 years ago
|
||
I don't know (enough) about tiers.
To clarify: That function is on the #else
branch of #if defined(XP_WIN) || defined(XP_MACOSX) || defined(XP_LINUX)
.
Are there other systems that we should support? Reading https://firefox-source-docs.mozilla.org/build/buildsystem/supported-configurations.html , I guess this would be tier-3?
Anyway, it's a one-liner build fix, I'd be happy to uplift it if you think it should be in Firefox 89 to help tier>=3 friends.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 10•4 years ago
|
||
Comment on attachment 9217322 [details]
Bug 1706554 - Remove aFirstFramePC from no-op FramePointerStackWalk definition - r?glandium
Beta/Release Uplift Approval Request
- User impact if declined: Tier-3 platforms build failures.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): It's only removing an argument in the function definition, to match the declaration. The function itself is empty in that configuration.
- String changes made/needed:
Comment 11•4 years ago
|
||
Comment on attachment 9217322 [details]
Bug 1706554 - Remove aFirstFramePC from no-op FramePointerStackWalk definition - r?glandium
No risk for tier 1 platforms, approved for beta, thanks.
Comment 12•4 years ago
|
||
bugherder uplift |
Updated•4 years ago
|
Description
•