Re: TP_NUM_C_BUFS too small

2015-11-03 Thread Corinna Vinschen
On Nov 3 00:07, Helmut Karlowski wrote: > Am 02.11.2015, 12:15 Uhr, schrieb Corinna Vinschen: > > >>Glad it's fixed! For the record, could you say what sort of bug would > >>cause > >>a fatal internal error like that? > >>Just curious, > > > >Me too. Sounds like some kind of recursion. > > It

Re: TP_NUM_C_BUFS too small

2015-11-02 Thread Helmut Karlowski
Am 02.11.2015, 12:15 Uhr, schrieb Corinna Vinschen: Glad it's fixed! For the record, could you say what sort of bug would cause a fatal internal error like that? Just curious, Me too. Sounds like some kind of recursion. It all happened after I had replaced all strcpy/strcat by strlcpy li

Re: TP_NUM_C_BUFS too small

2015-11-02 Thread Corinna Vinschen
On Nov 2 02:32, Mark Geisert wrote: > Helmut Karlowski writes: > > Am 01.11.2015, 18:46 Uhr, schrieb Helmut Karlowski: > > > Hello > > > > > > just had a program crashing with this error: > > > > > > 2 [main] ue 3180 C:\bin\ue.exe: *** f

Re: TP_NUM_C_BUFS too small

2015-11-01 Thread Mark Geisert
Helmut Karlowski writes: > Am 01.11.2015, 18:46 Uhr, schrieb Helmut Karlowski: > > Hello > > > > just had a program crashing with this error: > > > > 2 [main] ue 3180 C:\bin\ue.exe: *** fatal error - Internal error: > > TP_NUM_C_BUFS too small: 50 > &g

Re: TP_NUM_C_BUFS too small

2015-11-01 Thread Helmut Karlowski
Am 01.11.2015, 18:46 Uhr, schrieb Helmut Karlowski: Hello just had a program crashing with this error: 2 [main] ue 3180 C:\bin\ue.exe: *** fatal error - Internal error: TP_NUM_C_BUFS too small: 50 What could that mean? It means my program had a bug - fixed now. -Helmut -- Problem

TP_NUM_C_BUFS too small

2015-11-01 Thread Helmut Karlowski
Hello just had a program crashing with this error: 2 [main] ue 3180 C:\bin\ue.exe: *** fatal error - Internal error: TP_NUM_C_BUFS too small: 50 What could that mean? #uname -srvmo CYGWIN_NT-10.0-WOW 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin -Helmut -- -- Problem reports

Re: TP_NUM_C_BUFS too small

2011-02-08 Thread Corinna Vinschen
On Feb 8 13:14, marco atzeri wrote: > On Tue, Feb 8, 2011 at 12:59 PM, Corinna Vinschen wrote: > > On Feb  7 22:38, marco atzeri wrote: > >> Suggestion for debugging ? > > > > Build the Cygwin DLL for debugging (just -g, no -O2), build octave for > > debugging, and try to find the problem. > > >

Re: TP_NUM_C_BUFS too small

2011-02-08 Thread marco atzeri
4236 E:\cygwin2\bin\octave-3.3.92.exe: *** fatal error - >> Internal error: TP_NUM_C_BUFS too small: 79987540 > 10 > > This message points to a stack corruption.  There's a thread-local > storage in the highest area of the thread local stack.  In this TLS area > are a couple

Re: TP_NUM_C_BUFS too small

2011-02-08 Thread Corinna Vinschen
On Feb 7 22:38, marco atzeri wrote: > I am testing latest release candidate for octave, and only on cygwin using > the fltk graphics interface when we try to print through ghostscript we have: > > octave 4236 E:\cygwin2\bin\octave-3.3.92.exe: *** fatal error - > Internal error: TP

TP_NUM_C_BUFS too small

2011-02-07 Thread marco atzeri
I am testing latest release candidate for octave, and only on cygwin using the fltk graphics interface when we try to print through ghostscript we have: octave 4236 E:\cygwin2\bin\octave-3.3.92.exe: *** fatal error - Internal error: TP_NUM_C_BUFS too small: 79987540 > 10 Stack trace: Fr