Re: [fpc-pascal]FPC Version 1.9.4 released.

IoDream wrote: Hi, May I assume MultiThreading issues are gone. Multithreading is improved. However, "advanced" multithreading technologies like recursice mutexes aren't available in a platform independend way yet. And PIC (Position Independant Code) generation is working too ? It was the bigges

[fpc-pascal]profiling sampling rate

Hi, If I compile a program with -pg I can get profiling information with gprof. The sampling rate is 100 Hz, which means that the profiler looks 100 times each second in which procedure the progam is (if I describe it correctly). Is there a way to make the sampling rate higher, because on compu

[fpc-pascal]urgent: fdOpen etc on FreeBSD

Hi! I'm using the syscalls fdOpen, fdClose, etc on FreeBSD. Since swapping from compiler 1.0.10 to 1.9.2 and exchanging the 'uses Linux' statement to 'uses unix', these calls together with FD_SET and FD_Zero makros are missing. How can I handle that? Where have they gone? TIA, Marc _

[fpc-pascal]internal error

Hi again, what can I do, if my program exits with an Exeption 217 - internal error? What's the problem here? Bye, Marc ___ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal]urgent: fdOpen etc on FreeBSD

> I'm using the syscalls fdOpen, fdClose, etc on FreeBSD. > > Since swapping from compiler 1.0.10 to 1.9.2 and exchanging the 'uses > Linux' statement to 'uses unix', these calls together with FD_SET and > FD_Zero makros are missing. > > How can I handle that? Where have they gone? fpopen now. M

Re: [fpc-pascal]urgent: fdOpen etc on FreeBSD

Am Do, den 03.06.2004 schrieb Marco van de Voort um 19:47: > > I'm using the syscalls fdOpen, fdClose, etc on FreeBSD. > > > > Since swapping from compiler 1.0.10 to 1.9.2 and exchanging the 'uses > > Linux' statement to 'uses unix', these calls together with FD_SET and > > FD_Zero makros are miss

Re: [fpc-pascal]internal error

On Thu, 3 Jun 2004, Marc Santhoff wrote: > Hi again, > > what can I do, if my program exits with an Exeption 217 - internal > error? > > What's the problem here? Normally 217 is an abstract error, I think ? Michael. ___ fpc-pascal maillist - [EMAI

Re: [fpc-pascal]internal error

Am Do, den 03.06.2004 schrieb Michael Van Canneyt um 22:30: > On Thu, 3 Jun 2004, Marc Santhoff wrote: > > > Hi again, > > > > what can I do, if my program exits with an Exeption 217 - internal > > error? > > > > What's the problem here? > > Normally 217 is an abstract error, I think ? Maybe I'v

[fpc-pascal]parameter is 0x0 on callback

Hello, I've used the stuff following with fpc 1.0.10 and it worked fine, now with 1.9.2 the argument is set to zero: - a GTK+ 1.2 program) - a dialog has a pointer to a 'cdecl'ed callback procedure: ... src := TCustomer(datasrc.Items[selCursor]); {$ifdef debug} writeln(src.asCSV); {$endif} { p

[fpc-pascal]parameter is 0x0 on callback

Hi again, the problem seems to occur any time I try to access (unit global) variables in a cdecl-ed procedure or function, too. They are simply invisible in the debugger. What am I doing wrong here? Marc ___ fpc-pascal maillist - [EMAIL PROTECTED

Re: [fpc-pascal]parameter is 0x0 on callback

> Hi again, > > the problem seems to occur any time I try to access (unit global) > variables in a cdecl-ed procedure or function, too. They are simply > invisible in the debugger. > > What am I doing wrong here? Try the 1.9.4 release, there are fixes in the debuginfo generation __

Re: [fpc-pascal]parameter is 0x0 on callback

> Hello, > > I've used the stuff following with fpc 1.0.10 and it worked fine, now > with 1.9.2 the argument is set to zero: > > - a GTK+ 1.2 program) > - a dialog has a pointer to a 'cdecl'ed callback procedure: > > > ... > src := TCustomer(datasrc.Items[selCursor]); > {$ifdef debug} writeln(src.