Wolfgang J�hrling <[EMAIL PROTECTED]> wrote: > Looking at what glibc/hurd/fd-read.c does, it seems to be a leak to not > check for equality and freeing the buffer. Does anyone agree/disagree?
Well, I think I have to disagree with me here. :*) Looking at hurd/hurd/io.defs, this parameter is specified as out data: data_t, dealloc; Maybe I'm just understanding the MiG documentation wrong, but I thought the "dealloc" would take care of exactly this case. (Which was probably the reason I originaly wrote the code the way I did). But then I don't understand why the glibc code copies the data back from the newly allocated space to the old one (provided by the client). Cheers, GNU/Wolfgang -- Wolfgang J�hrling <[EMAIL PROTECTED]> \\ http://stdio.cjb.net/ Debian GNU/Hurd user && Debian GNU/Linux user \\ http://www.gnu.org/ The Hurd Hacking Guide: http://www.gnu.org/software/hurd/hacking-guide/ ["We're way ahead of you here. The Hurd has always been on the ] [ cutting edge of not being good for anything." -- Roland McGrath ] _______________________________________________ Help-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/help-hurd
