Re: [fpc-devel] FPC 2.0.0 vs FPC 2.0.2 (div by zero)

2006-03-11 Thread Michalis Kamburelis
Den Jean wrote: Hi, I have a strange problem. My Qt4 demo program worked fine with FPC 2.0.0, but crashes (div by zero) with FPC 2.0.2. Debugging shows that indeed a div by zero is done within the Qt4 lib. However with FPC 2.0.0 or using C++ code the library isn't bothered with the div by

Re: [fpc-devel] Dump_Stack broken in fpc 2.1.1

2006-03-11 Thread Vincent Snijders
Vincent Snijders wrote: Hi, Line info is broken in fpc 2.1.1 on win32. I have created the attached test program. Running the program gives: C:\lazarus\bugs\fpc\lineinfoproject1.exe In test opening the program in gdb gives. (no debugging symbols found)... Running the program compiled with

Re: [fpc-devel] Problems with fixes_2_0 rev. 2824

2006-03-11 Thread Martin Schreiber
On Friday 10 March 2006 13.06, Peter Vreman wrote: Hi, Are there any known problems with FPC fixes_2_0 rev. 2824? I get many AV's, error 204's and other strange things. There are no regressions in the building and in the testsuite. The problem is probably in rtl/i386/i386.inc: Procedure

Re: [fpc-devel] add external links to fpdoc generated documents

2006-03-11 Thread Tomas Hajny
On 10 Mar 06, at 15:48, Marco van de Voort wrote: On Fri, 10 Mar 2006, Vincent Snijders wrote: Hi, I would like to add a link to external documentation in a fpdoc generated document file. Is this possible. For example: On

Re: [fpc-devel] add external links to fpdoc generated documents

2006-03-11 Thread Marco van de Voort
document that contain more explanation, images and has a place for user comments. It is currently not possible. The reason is that fpdoc can also be used to generate PDF or Latex or plain text or RTF docs, and these don't support links. Actually, PDF (and latex package

Re: [fpc-devel] OS aware RTL proposal

2006-03-11 Thread Daniƫl Mantione
Op Fri, 10 Mar 2006, schreef Ales Katona: http://www.freepascal.org/wiki/index.php/OS_aware_RTL Tell me what you think I don't like to do the abstraction at the syscall level, but one level higher, i.e. the Tstream implementation. The reason is that the operating system abstraction