It looks like we have a whole collection of runtime segfaults and such.
The problem continues even in gcc-4.1.1-5. If anyone wants to take a
swing, here's a selection.
aptitude_0.4.1-1.1 check-TESTS test: Illegal Instruction
drscheme_1:301-15 ./install Segmentation fault
emacs-snapshot_1:20060623-1 ./temacs: Segmentation fault
gauche-gl_0.4.1-3 segfault (gauche from gauche)
gauche-gtk_0.4.1-5 segfault (gosh from gauche)
gmp_2:4.2.1+dfsg-1 check-TESTS: Illegal instruction
guile-1.6_1.6.8-3 Wrong type argument in position ~A: ~S
libbuffy_0.8.1-1 check-TESTS: libbuff-test terminate called after throwing an instance of 'std::runtime_error'
libgc_1:6.7-2 check-TESTS: gctest, test_cpp Segmentation fault
libgtk2-perl_1:1.121-1 327328 self-test failed: t/GdkPixbuf.t assertion `node != NULL' fail
newmat_1.10.4-2 ./example? segfault
openoffice.org_2.0.2.99.2.0.3rc6-1 update-mozilla-chrome segfault
pnet_0.7.4-1 Segmentation fault
ruby1.6_1.6.8-13 [BUG] Segmentation fault
tagcoll_1.6.3-1 failed self-test: terminate called after throwing an instance of 'std::runtime_error'
taskjuggler_2.2.0-1 350731 failed self-test
I'm keeping a running list at
<http://people.debian.org/~smarenka/m68kbugs/reports/failed-bynotes.html>.
--
Stephen R. Marenka If life's not fun, you're not doing it right!
<stephen@marenka.net>
Attachment:
signature.asc
Description: Digital signature