On Fri, Nov 27, 2020 at 04:05:42PM +0530, Mayuresh wrote:
> On Tue, Nov 17, 2020 at 08:24:29AM +0100, tlaro...@polynum.com wrote:
> > You should first try to rebuild it with an up-to-data compiler
> > framework before one could assert if there is indeed a problem.
>
> I built firefox52 from scratch over several days. Now I still get strtab
> errors, now with libfribidi. I was getting them with libdbus earlier, but
> I disabled dbus option of firefox.
>
> Now coming to compiler, I used the base compiler which I think is 7.5. Is
> any higher compiler version needed? I think the packages would have
> complained if that was the case.
>
> Instead of arbitrarily changing the compiler, are there any specific
> investigations I can do to establish the origin of strtab errors?
The strtab errors come from the linking hence from binutils. The only
causes I can imagine is whether there is a lib used that has been
compiled with an old version of the binutils, or a component was
compiled requering an old version of the toolchain and hence bringing in
an old version of the binutils.
Concerning the core dumps, there is another thing to look at:
_FORTIFY_SOURCE. There are checks about the use of strings functions
that can cause an abort even if the actual use is probably, with
a classic C implementation, safe---I hit it with a strcpy() that was
removing a prefix simply shifting bytes left in a buffer; it didn't
cause any harm before 9.* and now aborts because src and dst overlap.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
