Hello,
I am back developing for Mac!
My compiled application with symbold is 93.5 MB in size and gdb cannot
load it, so the debugger in Lazarus fails too.
This happens on both Leopard and Snow with FPC 2.2.x and 2.4.0 and
Lazarus 0.9.28 and 0.9.29.
Only the 2 year old installation on Tiger stil
On 10 Jul 2010, at 13:21, Tobias Giesen wrote:
> My compiled application with symbold is 93.5 MB in size and gdb cannot
> load it, so the debugger in Lazarus fails too.
Stabs or DWARF (-g or -gw)? I've seen this in the past with DWARF and
Lazarus-compiled applications, but never with Stabs.
>
> Stabs or DWARF (-g or -gw)?
I think Stabs, but apparently it worked with Dwarf in one particular
installation. I will need to look into it more. Lazarus still says
"Oops, debugger error" so I need to find out how to look at the
communication between Lazarus and gbd to see the actual error.
Wit
On 10 Jul 2010, at 19:58, Tobias Giesen wrote:
> With FPC 2.4.0 I get Fatal: Compilation aborted: Unhandled exception
> at ... on line 1 of some units.
Does it still happen after cleaning the project and then rebuilding it?
Jonas
___
fpc-pascal mai
> > With FPC 2.4.0 I get Fatal: Compilation aborted: Unhandled exception
> > at ... on line 1 of some units.
>
> Does it still happen after cleaning the project and then rebuilding it?
I manually deleted all .ppu, .o, and .rst files and it happens on a
fresh build.
By the way could -Cs2000
On 10 Jul 2010, at 20:23, Tobias Giesen wrote:
> I manually deleted all .ppu, .o, and .rst files and it happens on a
> fresh build.
Then please file a bug report with source code to reproduce the crash.
> By the way could -Cs2000 do any harm? Maybe one 0 too many?
The stack size only affec
> Then please file a bug report with source code to reproduce the crash.
I'd love to but probably it only happens in my project with close to 500
units, it can be really hard to strip such things down. There is
unfortunately a lot of closed source code in it.
I will try installing FPC 2.5. Prob
Hi,
I have the sources from SVN now, do I just cd into the folder and
type make?
I couldn't find any documentation on making FPC anywhere on
freepascal.org. Maybe I missed something?
Cheers,
Tobias
___
fpc-pascal maillist - fpc-pascal@lists.freepasc
On 10 July 2010 21:21, Tobias Giesen wrote:
>
> I couldn't find any documentation on making FPC anywhere on
> freepascal.org. Maybe I missed something?
On the website on the right is a link "Documentation".
http://freepascal.org/docs.var
--
Regards,
- Graeme -
___
> On the website on the right is a link "Documentation".
>
> http://freepascal.org/docs.var
OK after some more searching I found the Building faq (PDF) on
http://freepascal.org/moreinfo.var
Cheers,
Tobias
___
fpc-pascal maillist - fpc-pascal@list
Hello,
I've got 2.5.1 now. I have a string constant like this:
const Vec:AnsiString=#$094#$06D;
This should just be 8-bit data with no conversion.
But I get
"Error: Unicodechar/string constants cannot be converted to
ansi/shortstring at compile-time."
Can I tell the compiler to interpret al
On Sun, Jul 11, 2010 at 12:14 AM, Tobias Giesen
wrote:
> I've got 2.5.1 now. I have a string constant like this:
>
> const Vec:AnsiString=#$094#$06D;
>
> This should just be 8-bit data with no conversion.
try const Vec:AnsiString=#$94#$6D;
thanks,
dmitry
_
On 10 Jul 2010, at 22:32, dmitry boyarintsev wrote:
> On Sun, Jul 11, 2010 at 12:14 AM, Tobias Giesen
> wrote:
>> I've got 2.5.1 now. I have a string constant like this:
>>
>> const Vec:AnsiString=#$094#$06D;
>>
>> This should just be 8-bit data with no conversion.
>
> try const Vec:AnsiStrin
> > const Vec:AnsiString=#$094#$06D;
> > This should just be 8-bit data with no conversion.
>
> try const Vec:AnsiString=#$94#$6D;
Works! Thanks Dmitry!
Cheers,
Tobias
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepasca
On 10/07/2010 22:01, Jonas Maebe wrote:
const Vec:AnsiString=#$094#$06D;
This should just be 8-bit data with no conversion.
try const Vec:AnsiString=#$94#$6D;
I've now documented this change at
http://wiki.freepascal.org/User_Changes_Trunk#Short.2FAnsistring_typed_constants_conta
On 10 Jul 2010, at 23:13, Martin wrote:
> It would be nice if there was(maybe there is) some way, of telling the
> compiler that the string is to be treaded as binary-data. Maybe like:
>
> {$codepage utf8}
> const
> {$codepage binary} // temporary change
> s1: shortstring = 'éà';
> {$codepage
16 matches
Mail list logo