Bugs needing attention
"Wichmann, Mats D" <[email protected]>
| Newsgroups | gmane.linux.lsb.test-suite |
|---|---|
| Message-ID | <A06801158AE07847B27A52C1A074BC1D08A40BA1@fmsmsx404.amr.corp.intel.com> |
I know we've all gotten in the habit of ignoring the nag email from bugzilla. I'd like to have some further thoughts on these bugs: I think these two are the same bug. It seems to me the test strategy here is making assumptions it maybe cannot safely make, but until the DCCA problems it seemed it only happened in "odd" cases (running something which is not the native architecture, or the specific kernel architecture, such as ia32 on ia64, ppc32 on a ppc64 kernel, etc.). Now it's been seen on a straight ia32 as well. http://bugs.linuxbase.org/show_bug.cgi?id=1068 http://bugs.linuxbase.org/show_bug.cgi?id=684 For this one, http://bugs.linuxbase.org/show_bug.cgi?id=1079 it's a known issue (see Marvin's nightly-build pages at http://www.linuxbase.org/~heffler/libchk/ for ppc64) but for the first time there's some analysis of what's going on. What I don't see is how we would code the test, if the analysis is correct and dladdr is not useful since that's what the test expects to do. It's also not clear when this supposed ABI change took place (the LSB never listed the .foo symbols as part of the ABI, by the way). -- mats