ulimit -c for core dumps

Hi, I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone please explain why a core file gets generated from the coretest program (source is below)? Thanks for any help or suggestions. Shell interaction % ulimit -H -c unlimited % ulimit -S -c 0 % bash --version GNU bash, v

need explanation ulimit -c for limiting core dumps

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../

Can 'read' be used with tab-completion?

I've been wondering this for a long time, but can't figure anything out from the doc... Is it possible to specify a list of possible completions for the 'read' built-in? -- Matthew "Try to bring it back in one piece this time." -- Q (MI6) ___ Bug-b

Re: ulimit -c for core dumps

Jason Roscoe <[EMAIL PROTECTED]> writes: > I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone > please explain why a core file gets generated from the coretest program > (source is below)? The creation is only suppressed when the limit is zero. Otherwise it will be truncat

Re: need explanation ulimit -c for limiting core dumps

I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone please explain why a core file gets generated from the coretest program (source is below)? Thanks for any help or suggestions. Shell interaction % ulimit -H -c unlimited % ulimit -S -c 0 % bash --version GNU bash, versio

Re: Can 'read' be used with tab-completion?

Matthew Woehlke wrote: > I've been wondering this for a long time, but can't figure anything out > from the doc... Is it possible to specify a list of possible completions > for the 'read' built-in? No. `read -e' allows the use of readline, but there is no access to anything other than the defaul

Re: need explanation ulimit -c for limiting core dumps

[EMAIL PROTECTED] wrote: > Machine Type: i386-pc-linux-gnu > > Bash Version: 2.05b > Patch Level: 0 > Release Status: release > > Description: > > Hi, > I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone > please explain why a core file gets generated from the coretest p

Re: need explanation ulimit -c for limiting core dumps

Chet Ramey wrote: [EMAIL PROTECTED] wrote: I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone please explain why a core file gets generated from the coretest program (source is below)? Thanks for any help or suggestions. % ulimit -H -c 512 % ./coretest 2048 rlim_cur,rl

Re: need explanation ulimit -c for limiting core dumps

Matthew Woehlke wrote: > Chet Ramey wrote: >> [EMAIL PROTECTED] wrote: >>> I'm trying to limit the size of coredumps using 'ulimit -c'. Can >> someone please explain why a core file gets generated from the coretest >> program (source is below)? >>> >>> Thanks for any help or suggestions. >>> >>> %

ru.po in bash 3.2 p1

Chet, I have built bash 3.2 patchlevel 1 under Mac OS X 10.4.8 (both PPC and Intel) and I get the following error while installing: make[2]: [EMAIL PROTECTED]' is up to date. rm -f ru.gmo && /usr/local/bin/msgfmt -c --statistics -o ru.gmo ru.po ru.po:21:9: invalid multibyte sequence ru.po:21:

Re: need explanation ulimit -c for limiting core dumps

Mike Stroyan wrote: I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone please explain why a core file gets generated from the coretest program (source is below)? Thanks for any help or suggestions. Shell interaction % ulimit -H -c unlimited % ulimit -S -c 0 % bash --ver

Re: need explanation ulimit -c for limiting core dumps

Chet Ramey wrote: Matthew Woehlke wrote: Chet Ramey wrote: [EMAIL PROTECTED] wrote: I'm trying to limit the size of coredumps using 'ulimit -c'. Can someone please explain why a core file gets generated from the coretest program (source is below)? Thanks for any help or suggestions. % ulim