At Fri, 15 Jul 2005 11:18:26 -0500,
Manoj Srivastava wrote:
> This does not seem to be something that changes in make are
> going to fix. make essentially makes a glob (3) call; and that
> library call is where the segmentation violation occurs. Considering
> that the number of entries i
On Fri, 29 Jul 2005, GOTO Masanori wrote:
>Manoj Srivastava wrote:
>> could be something that libc was not prepared for (memory
>> exhausted?).
Now that you mentioned it, some memory information:
> free
total used free sharedbuffers cached
Mem:516
At Fri, 29 Jul 2005 19:51:34 +0300 (EEST),
Tuukka Toivonen wrote:
> > ulimit -a
> core file size(blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> file size (blocks, -f) unlimited
> max locked memory (kbytes, -l) unlimited
> max memory size (kbytes, -m) un
reassign 318244 libc6
thanks
Hi,
This does not seem to be something that changes in make are
going to fix. make essentially makes a glob (3) call; and that
library call is where the segmentation violation occurs. Considering
that the number of entries in the directory are insanely high
Processing commands for [EMAIL PROTECTED]:
> reassign 318244 libc6
Bug#318244: segmentation fault with many files
Bug reassigned from package `make' to `libc6'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrato
5 matches
Mail list logo