This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/1065] Inefficient malloc / realloc behavior


------- Additional Comments From fritz at intrinsity dot com  2005-09-27 15:54 -------
(In reply to comment #1)
> Bring this up with your vendor (whoever produces "Scientific Linux").

Hey Ulrich,

I had originally contacted the Scientific Linux folks and filed it as a
bug on them.  Here's what came of that:

----------------------------------------

Fritz,

Scientific Linux is a rebuild of RedHat Enterprise Linux.  We do not
have the resources to fix problems not associated with our rebuild.

So in your case the problem is with a GNU product I would suggest you go
to GNU.

In some cases the problem should be reported to RedHat but this gets to be
sticky as RedHat has absolutely nothing to do with Scientific Linux.  So
if a bug is reported to them then it should be verified that the problem
exists on their product and the problem then should be reported against
their product.

We will add more info to the bug page to clarify these issues.

If you really need issues such as what you reported fixed then I suggest
you purchase a Linux Distribution that includes support from the vendor.

-Connie Sieh

----------------------------------------

I had also tried the GNU site.  After many bounced messages to multiple
addresses, I finally got it to stick at bug-glibc@gnu.org.  Then I got this
response:

To: Fritz Boehm <fritz@intrinsity.com>
From: Petter Reinholdtsen <pere@hungry.com>
You might want to know that the glibc developers no longer reads this
list, due to the amount of spam on it.  You will have better success
reporting your bug to <URL:http://sources.redhat.com/bugzilla/>.

----------------------------------------

I don't have the resources to obtain RedHat Enterprise.  I already spent 6 days
here at work isolating the problem.  I'm trying to do my part in feeding back
into the system the bugs I find.  I can see where things are sticky with all
these releases, but that is beyond my control.  It would be a shame if this bug
was lost, but I'm not going to push it any more.  If RedHat wants to summarily
drop this, I can't blame them or you, but this is as far as I can go with
this matter.

Fritz

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=1065

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]