2011/11/8 Svante Signell <svante.signell / telia.com>:
> I'm working on porting packages having PATH_MAX issues and ruby1.9.1 is
> one of them. PATH_MAX is not defined for GNU/Hurd. The code analysis
> below shows that it would be possible to use dynamic allocation of the
> buffer binary_filename using malloc and free.
>
> However, Samuel Thibault, a large contributor to GNU/Hurd and a Debiab
> Developer, advised me to ask here is it is possible or if a
> fixed-length buffer should be used? Especially if it is safe to call
> rb_dump_backtrace_with_lines from a *Unix* signal handler.
>
> So if dynamic allocation is not possible, can you in the next release
> provide a conditional definition of PATH_MAX?
>
> #ifndef PATH_MAX
> #define PATH_MAX 4096
> #endif

I committed in r33675.

>> > Below is a patch attempt to solve the PATH_MAX issue on the latest
>> > ruby1.9.1.

This means trunk branch of ruby repo?

> Code analysis follows below:

You may already noticed, following codes are run when the program is
crashed like segv.
On such situation, it hardly use malloc.

--=20
NARUSE, Yui =A0<naruse / airemix.jp>