Re: A problem internal to GDB has been detected

2005-08-11 Thread Reitenbach Sebastian
Hi Arnaud, > > > > $ ulimit -m 708879 > > sh: ulimit: exceeds allowable limit > > > > is there a way to exceed the allowable limit? how is the maximum > > determined? > > The maximum limit is determined by your login class and how it is > configured in /etc/login.conf. > > look at login.conf(5) fo

Re: A problem internal to GDB has been detected

2005-08-10 Thread Arnaud Bergeron
On 8/10/05, Reitenbach Sebastian <[EMAIL PROTECTED]> wrote: > Hi, > > I think you adressed the problem. but after setting ulimit -d a bit higher I > get > a bit more ahead, so the memory is later exhausted. This does not helped that > much. > > ulimit -m was alrady at the maximum. > > $ ulimit

Re: A problem internal to GDB has been detected

2005-08-09 Thread Reitenbach Sebastian
Hi, I think you adressed the problem. but after setting ulimit -d a bit higher I get a bit more ahead, so the memory is later exhausted. This does not helped that much. ulimit -m was alrady at the maximum. $ ulimit -m 708879 sh: ulimit: exceeds allowable limit is there a way to exceed the allo

A problem internal to GDB has been detected

2005-08-09 Thread Mark Kettenis
> (gdb) run -WOUseWatchDog NO > Starting program: /usr/local/sbin/ogo-webui-1.1 -WOUseWatchDog NO > /usr/src/gnu/usr.bin/binutils/gdb/utils.c:1007: internal-error: virtual > memory exhausted: can't allocate 1073960 bytes. > A problem internal to GDB has been detected, >

A problem internal to GDB has been detected

2005-08-08 Thread Reitenbach Sebastian
/usr/local/sbin/ogo-webui-1.1 -WOUseWatchDog NO /usr/src/gnu/usr.bin/binutils/gdb/utils.c:1007: internal-error: virtual memory exhausted: can't allocate 1073960 bytes. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n)