ldconfig freaks out with bus error [was: lh_build woes]
-----BEGIN PGP SIGNED MESSAGE-----
On Sat, Mar 29, 2008 at 12:19:56PM -0400, Justin Pryzby wrote:
> So it opens and mmaps each lib (or, only libs with updated timestamps
> in glibc 2.7), then reads the NEEDED or SONAME information. Your bad
> disk causes the memory read to fail and so the proc is sent SIGBUS. Is
> that the correct behavior, or could ldconfig do something better? I
> suspect that's essentially as good as it could be.
Yeah (see my other post, confirming the disk problem). The behaviour of
ldconfig makes sense to me.
- -- tom?s
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
-----END PGP SIGNATURE-----