[#444] io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...>

I am encountering a problem similar to the one mentioned here,

19 messages 2002/09/06
[#453] Re: io_write()/fwrite() and EINTR on Solaris — nobu.nokada@... 2002/09/08

Hi,

[#454] Re: io_write()/fwrite() and EINTR on Solaris — matz@... (Yukihiro Matsumoto) 2002/09/09

Hi

[#469] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/09

On Mon, Sep 09, 2002 at 03:55:13PM +0900, Yukihiro Matsumoto wrote:

[#479] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/10

On Tue, Sep 10, 2002 at 01:04:10AM +0900, Jos Backus wrote:

[#492] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/21

On Wed, Sep 11, 2002 at 02:23:33AM +0900, Jos Backus wrote:

Re: [MemLeak] in dln.c

From: matz@... (Yukihiro Matsumoto)
Date: 2002-09-02 15:00:42 UTC
List: ruby-core #404
Hi,

In message "Re: [MemLeak] in dln.c"
    on 02/09/02, Michal Rokos <m.rokos@sh.cvut.cz> writes:

|> >      if ((init_fct = (void(*)())GetProcAddress(handle, buf)) == NULL) {
|	Data_Wrap_Struct(rb_cData, 0, free, buf);
|> > +	rb_loaderror("%s - %s\n%s", dln_strerror(), buf, file); /* FIXME: MEMLEAK for buf */
|> >      }
|> >      free(buf);
|
|	(and on the 2nd place as well.)
|
|	I know, that it has a flaw in it, but it could be OK.

I'd use alloca.  I want dln.c to be separatable from Ruby as much as
possible.

							matz.

In This Thread