Forum: Ruby-core [ruby-trunk - Bug #7754][Open] Backport file.c (realpath_rec) GC fix to 1.9.3

Issue #7754 has been reported by jschneiderhan (Jon-Erik Schneiderhan).

----------------------------------------
Bug #7754: Backport file.c (realpath_rec) GC fix to 1.9.3
https://bugs.ruby-lang.org/issues/7754

Author: jschneiderhan (Jon-Erik Schneiderhan)
Status: Open
Priority: Normal
Assignee:
Category: core
Target version: 1.9.3
ruby -v: ruby-1.9.3-p374


I'm hitting a problem with ruby-1.9.3-p327 and ruby-1.9.3-p374 that I 
tracked down with gdb to the realpath_rec method in file.c.  The 
behavior I am seeing is that the char array pointed at by link_names is 
written over if GC runs in subsequent calls to realpath_rec.

It turns out the issue has already been resolved in trunk:

https://bugs.ruby-lang.org/projects/ruby-trunk/rep...

I was wondering if this could be backported to 1.9.3.

Issue #7754 has been updated by luislavena (Luis Lavena).

Status changed from Open to Assigned
Assignee set to usa (Usaku NAKAMURA)


----------------------------------------
Bug #7754: Backport file.c (realpath_rec) GC fix to 1.9.3
https://bugs.ruby-lang.org/issues/7754#change-35703

Author: jschneiderhan (Jon-Erik Schneiderhan)
Status: Assigned
Priority: Normal
Assignee: usa (Usaku NAKAMURA)
Category: core
Target version: 1.9.3
ruby -v: ruby-1.9.3-p374


I'm hitting a problem with ruby-1.9.3-p327 and ruby-1.9.3-p374 that I 
tracked down with gdb to the realpath_rec method in file.c.  The 
behavior I am seeing is that the char array pointed at by link_names is 
written over if GC runs in subsequent calls to realpath_rec.

It turns out the issue has already been resolved in trunk:

https://bugs.ruby-lang.org/projects/ruby-trunk/rep...

I was wondering if this could be backported to 1.9.3.