Antonio Terceiro escreveu isso aí: > Hm, not so fast. When building ruby1.8 on amd64, I also get a segfault very > early in the test suite (although the build succeeds). At least your test case > does not segfault for me with the built binaries.
Look at what I just got with the new ruby1.8 I built installed on my system: > $ LANG=C sudo apt-get install mysql-server > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following extra packages will be installed: > libdbd-mysql-perl mysql-client-5.5 mysql-server-5.5 mysql-server-core-5.5 > Suggested packages: > tinyca > The following NEW packages will be installed: > libdbd-mysql-perl mysql-client-5.5 mysql-server mysql-server-5.5 > mysql-server-core-5.5 > 0 upgraded, 5 newly installed, 0 to remove and 472 not upgraded. > Need to get 0 B/23.8 MB of archives. > After this operation, 86.6 MB of additional disk space will be used. > Do you want to continue [Y/n]? > Retrieving bug reports... > 0%/usr/lib/ruby/vendor_ruby/httpclient/session.rb:775: [BUG] Segmentation > fault > ruby 1.8.7 (2012-02-08 patchlevel 358) [x86_64-linux] > > Aborted > E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code > (10) > E: Failure running script /usr/sbin/apt-listbugs apt || exit 10 After I downgraded to the ruby1.8 packages from the archive, that segfault went away. Then only difference I can see between that packages, built ~1 month ago, and this one I just built is the gcc version: the version in the archive was buit with gcc 4.6 and the built I did today used gcc 4.7. Is it possible that the new gcc generates code that segfaults while the older gcc would generate code that wouldn't? -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
