Closed Bug 1706554 Opened 4 years ago Closed 4 years ago

FramePointerStackWalk shouldn't take aFirstFramePC

Categories

(Core :: mozglue, defect)

defect

Tracking

()

RESOLVED FIXED
90 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox88 --- unaffected
firefox89 --- fixed
firefox90 --- fixed

People

(Reporter: mozbugz, Assigned: mozbugz)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

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.)

Set release status flags based on info from the regressing bug 1515229

Pushed by gsquelart@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/885e78c7baa9 Remove aFirstFramePC from no-op FramePointerStackWalk definition - r=glandium
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch

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.

Flags: needinfo?(gsquelart)

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.

Flags: needinfo?(gsquelart)

not(Tier 1) != unsupported

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.

Flags: needinfo?(mh+mozilla)

Yes, please.

Flags: needinfo?(mh+mozilla)

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:
Attachment #9217322 - Flags: approval-mozilla-beta?

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.

Attachment #9217322 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: