[Bug 2084460] Re: [SRU] Please enable frame-pointer on Noble

[Andreas Hasenack]

Please make the following clarifications in the test plan and SRU "where
problems could occur":

a) Use the scripts as planned in the original test plan, but extend them
to all architectures, because we don't want frame pointers in s390x and
ppc64el, only arm64 and amd64 if I'm not mistaken (not on 32bits).

b) We need some form of smoke test to make sure the package still runs.
Here it's a library, so it will have to be done with its reverse
dependencies. Perhaps enough reverse dep8 tests are triggered?

c) If (a) cannot be done for some reason, or perhaps as an improvement
on (a), check the build logs for each architecture and look for the
frame pointer flags being present and absent where required.

d) Please verify the diff in the compiler flags. I'm not sure if my
comment #3 was exhaustive, please verify. If it's correct, then that
diff from comment #3 suffices.

e) In particular, we are looking for "problematic" flags now being
enabled. For example, and I didn't spot it in this build (but I could be
wrong, as I just did a quick check), the "-Wl,-Bsymbolic-functions"
linker flag is known to have caused problems with libraries and plugins
in the past (like in autofs[1][2]). That's the kind of regression we
really have to be careful to avoid, and detect early.


1. https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1470687
2. https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115

-- 
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to nspr in Ubuntu.
https://bugs.launchpad.net/bugs/2084460

Title:
  [SRU] Please enable frame-pointer on Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2084460/+subscriptions