回复: [Request Suggestion] How does obstack deal with the specific valid address in obstack_free ?

Hi Bruno, Thanks for your insightful clarification! I have no further confusion now. Best regards, Haoxin 发件人: Bruno Haible 发送时间: 2022年1月11日 2:02 收件人: bug-gnulib@gnu.org 抄送: TU Haoxin 主题: Re: [Request Suggestion] How does obstack deal with the specific valid

Re: Problems with directory trees "confdir-14B---" and "confdir3"

On 1/9/22 03:10, Peter Dyballa wrote: checking whether getcwd aborts when 4k < cwd_length < 16k... yes and of course the reports about not being able to remove the "confdir-14B---" and "confdir3" directory trees, So, the problem is that the test program creates the deep directories,

[PATCH] backupfile: fix bug when renaming not from wd

* lib/backupfile.c (backupfile_internal): Fix bug when DIR_FD does not specify the working directory, and when RENAME. Without the bug fix, FILE is treated as relative to the working directory, not relative to DIR_FD, when renaming FILE. This bug was introduced when DIR_FD and RENAME were

Re: [Request Suggestion] How does obstack deal with the specific valid address in obstack_free ?

Hi, > I just have a question about the implementation intention of obstack_free (an > API in obstack, which is widely used in various gnu libraries, e.g.c Glibc, > more details in > https://gcc.gnu.org/onlinedocs/libiberty) I believe the definitive

[Request Suggestion] How does obstack deal with the specific valid address in obstack_free ?

Dear developers, I hope it's fine for me to ask you a question, please forgive me if not. I just have a question about the implementation intention of obstack_free (an API in obstack, which is widely used in various gnu libraries, e.g.c Glibc, more details in