crash in config.guess on Power Mac G5 under Mac OS X 10.4.6

Torbjorn Granlund tege at
Fri May 19 23:16:14 CEST 2006

Vincent Lefevre <vincent at> writes:

  > That hardly means it works correctly and does what you want.
  But at least, this would fix the problem on a number of systems
  (and in particular, probably Mac OS X, well... I hope so). On the
  other systems, if a bad instruction doesn't send a signal, then
  there wouldn't be any change compared to the current behavior.
  But then, the only way to fix the problem for all possible systems
  would be not to run the code that has a bad instruction.
We cannot disable it for systems where it doesn't work, since we
don't know which systems that would be in the future.

The current configure systems tries to rely on feature tests as much
as possible, and as little as possible on hardwired "X is true for
system Y" kind of things.

  BTW, the current behavior is bad on Linux too, since a core dump may
  be generated and fill the disk space. And asking the users to disable
  core dumps is a bad idea, as they are useful for debugging and for
  bug reports.
What is bad on Linux and why?

I think you're exaggerating somewhat if you think config.guess' tiny
programs will fill any disks.  I don't know the size of your disks, of
course, but I doubt a 20 line program that doesn't allocate any memory
will result in core dumps more than a few Kibytes, even on the
weirdest of systems.


More information about the gmp-bugs mailing list