Re: [fpc-pascal]sockets (a beginer's question) (client-server)

2003-06-10 Thread Michael Van Canneyt
On Mon, 9 Jun 2003, Ivan Petrov wrote: > Hello! > > At first I have to send my thanks to Rainer Hantsch > for my first question! > And then I beg your pardon for my bad english! I hope you'll understand me. > so...oCrt is a very good unit !!!...and so easy to use! > > But after a couple of days

[fpc-pascal]Internal Error

2003-06-10 Thread Adam Naumowicz
Hi, Trying to use a Delphi-style initialized var with a procedural variable I get the following error message: Free Pascal Compiler version 1.0.6 [2002/05/23] for i386 Copyright (c) 1993-2002 by Florian Klaempfl Target OS: Linux for i386 Compiling tester.pas Panic : Internal compiler error (SIGSEG

Re: [fpc-pascal]sockets (a beginer's question) (client-server)

2003-06-10 Thread Ivan Petrov
On Tuesday 10 June 2003 10:44, Michael Van Canneyt wrote: --- snip --- > > The question: > > Can I check if there is data pending in "sin" after I accept a connection > > and sin and sout streams are up. > > You should use the select() call from the linux unit. > This will check if data is availa

[fpc-pascal]GetMem crazy problem

2003-06-10 Thread Eduardo Morras
Hello: I've got a weird problem with getmem. I have check everything (i think) but i can't get it work. Heaptrc says it's all ok, but when i de-comment the next three lines ( the freemem also ), all fails GetMem(sDicc,sizeof(rtBusqBidimen)); GetMem(ppmv,sizeof(rtMotionVector))

Re: [fpc-pascal]GetMem crazy problem

2003-06-10 Thread Alan Mead
Eduardo, I did not follow your example, but are you aware of the "growing heap" behavior of FreePascal and the ReturnNilGrowHeapFails variable? http://www.freepascal.org/docs-html/prog/progsu113.html#x163-1680008.4 Also, I think this ReturnNilGrowHeapFails behavior is broken in 1.0.6 and fixed i

Re: [fpc-pascal]GetMem crazy problem

2003-06-10 Thread Alan Mead
I just looked at this again. If you are really getting RTE 201 then it (probably) has nothing to do with the GetMem's. It means you are over-indexing your arrays or seomthing similar. Good luck. -Alan --- Alan Mead <[EMAIL PROTECTED]> wrote: > Eduardo, > > I did not follow your example, but ar

Re: [fpc-pascal]sockets (a beginer's question) (client-server)

2003-06-10 Thread Ivan Petrov
Sorry for the spam! Thank you! I found it. But afterthe "Accept(S, FromName, Sin, Sout);" how to tell to Select that I mean Sin as a parameter (file descriptor?) ? There are a LongInt and pointers in Select's definition... On Tuesday 10 June 2003 10:44, Michael Van Canneyt wrote: > > You should

Re: [fpc-pascal]sockets (a beginer's question) (client-server)

2003-06-10 Thread Michael . VanCanneyt
On Tue, 10 Jun 2003, Ivan Petrov wrote: > Sorry for the spam! > Thank you! I found it. > > But afterthe "Accept(S, FromName, Sin, Sout);" > how to tell to Select that I mean Sin as a parameter (file descriptor?) ? > There are a LongInt and pointers in Select's definition... ? Select works on a

Re: [fpc-pascal]GetMem crazy problem

2003-06-10 Thread Eduardo Morras
At 12:46 10/06/2003 -0700, you wrote: I just looked at this again. If you are really getting RTE 201 then it (probably) has nothing to do with the GetMem's. It means you are over-indexing your arrays or seomthing similar. Good luck. -Alan That's what surprise me, so rechecked and yes, the rte

Re: [fpc-pascal]GetMem crazy problem

2003-06-10 Thread Alan Mead
--- Eduardo Morras <[EMAIL PROTECTED]> wrote: > At 12:46 10/06/2003 -0700, you wrote: > >I just looked at this again. If you are really getting RTE 201 > then > >it (probably) has nothing to do with the GetMem's. It means you > are > >over-indexing your arrays or seomthing similar. Good luck. >

Re: [fpc-pascal]GetMem crazy problem

2003-06-10 Thread Eduardo Morras
At 14:22 10/06/2003 -0700, you wrote: Is 1.0.8 available? I just checked www.freepascal.org and it seems like 1.06 is the current release. You might try that version and see if the problem goes away. -Alan 1.07 and 1.08 are updates to 1.06. You must download them and install by hand. In a few