Hello, FPC developers' list.
This was reported few days ago on the Lazarus mail list and probably was
not noticed by FPC developers:
Compile any application with stabs debug info (I did not check with
dwarf), run it in gdb:
(gdb) ptype Exception
type = EXCEPTION = class : public TOBJECT
Sergei Gorelkin wrote:
Vincent Snijders wrote:
I admit these are mere hints at a possible bug, but if I were
maintainer of that code, I would take another look at it.
I will :-)
Vincent, what command(s) did you use to get that log?
What options were used when compiling the packages?
Serg
Hi all,
In fpc 2.5.1 I've introduced the global CustomApplication variable in
the custapp unit. The idea is that when this variable is set when a
application-object is initialized, this variable is set so that you can
access the CustomApplication-object without knowing in which unit it is
defined.
On 08 Oct 2009, at 16:28, Paul Ishenin wrote:
I see only 3 features:
- Multi-byte and wide character set support
GDB has a new data type or what? Will fpc use that datatype?
It does not require any changes in FPC. Afaik it means that if you
have a widechar (or an array of widechar, or a p
Hello, FPC developers' list
What of new gdb 7.0 features will be used by FPC?
I see only 3 features:
- Multi-byte and wide character set support
GDB has a new data type or what? Will fpc use that datatype?
- Inlined functions are now supported
Currently I can't enter an inlined function usin
On 08 Oct 2009, at 14:54, Henrick Hellström wrote:
When compiling the following code for Win64 using FPC 2.2.2, Intel
syntax
mov qword [rdx ],$08C9BCF367E6096A
the compiler generates a movl instruction for just the least
significant
half of the constant qword
movl 0x67e6096a,(
When compiling the following code for Win64 using FPC 2.2.2, Intel syntax
mov qword [rdx ],$08C9BCF367E6096A
the compiler generates a movl instruction for just the least significant
half of the constant qword
movl 0x67e6096a,(%rdx)
Am I missing something obvious?
smime.p7s
Descri
Vincent Snijders wrote:
I admit these are mere hints at a possible bug, but if I were maintainer
of that code, I would take another look at it.
I will :-)
Sergei
___
fpc-devel maillist - [email protected]
http://lists.freepascal.org
Marco van de Voort schreef:
In our previous episode, Vincent Snijders said:
Vincent Snijders schreef:
While running valgrind on fpcdoc, I got a warning in
Maybe you are interested in the valgind output. See attachment.
Another problem, that was also in the valgrind output (reading uninitiali
In our previous episode, Vincent Snijders said:
> > Vincent Snijders schreef:
> >> While running valgrind on fpcdoc, I got a warning in
> >
> > Maybe you are interested in the valgind output. See attachment.
> >
>
> Another problem, that was also in the valgrind output (reading uninitialized
>
Vincent Snijders schreef:
Vincent Snijders schreef:
While running valgrind on fpcdoc, I got a warning in
Maybe you are interested in the valgind output. See attachment.
Another problem, that was also in the valgrind output (reading uninitialized
memory):
EAccessViolation : Access violation
On 08 Oct 2009, at 09:32, Dimitrios Chr. Ioannidis wrote:
when i tried to bootstrap a x86_64 compiler from fixes_2_4 branch
using a stable i386 ppc386 2.2.4 i got this error:
I would recommend to not cross-bootstrap across different versions.
Jonas
_
On 07 Oct 2009, at 22:24, Vincent Snijders wrote:
Should I create a bug report or is using -gt for the compiler not
supported.
It should work.
There is one problem with compiling the RTL with -gt if you assign a
shortstring to itself (e.g., by passing a global variable variable as
var/c
Hi all,
when i tried to bootstrap a x86_64 compiler from fixes_2_4 branch
using a stable i386 ppc386 2.2.4 i got this error:
fixes_2_4 branch revision : 13817
ppc386 -i : Free Pascal Compiler version 2.2.4, Compiler Date :
2009/04/10, Compiler CPU Target: i386
make all install UPXPRO
14 matches
Mail list logo
