[Python-bugs-list] [Bug #110712] MALLOC_ZERO_RETURNS_NULL problem

[Jeremy Hylton]

>>>>> "SF>" == noreply  <noreply@sourceforge.net> writes:

  SF>> Comment: I don't understand why the configure script would use
  SF>> a different malloc library for its test of malloc(0) than what
  SF>> is used later to compile Python. Could it be that simply "make
  SF>> clobber" and running configure again would solve the problem?

  SF>> I'm closing the bug report for now.  If this is still a problem
  SF>> with Python 2.0, please send email and I'll reopen it.

Guido,

Your last comment puzzles me.  How is anyone other than you and me
going to see the request to send email if it is still a problem?  The
bug is an old Jitterbug submission, which means that the original
submittor is not known by SF.

You need to send the original submittor an email yourself if you want
him to reply.  If you did send that email, the comment in the bug
report is misleading.  (It would be clearer to say: "I sent private
email to the submittor.  If he reports that it is still a problem with
2.0, I will reopen it.")

(You probably did not notice that it was a Jitterbug report.  But SF
doesn't always have an email address, even for new bugs.)

Jeremy