2010/10/2 Juha Manninen (gmail) :
> The last 3 lines practically say Lazarus has a memory corruption or leak or
> something, while it does not have. It is OK not that I know it.
True heap size : 1048576
True free heap : 1924768
Should be : 1048576
It just says that heaptr didn't calculate the Tru
2010/10/2 Jonas Maebe :
> Because of "-gh" I am getting the following output always when closing
> Lazarus. Only the numbers change with Lazarus versions and compile options.
>
> Likely it is not a "real" error. Vincent Snijders suspected it is a bug in
> the
> way heaptrc does its counting in a 64
On 02/10/2010, Jonas Maebe wrote:
>> Debug and Line Info information is missing in FPC under 64-bit Linux,
>> even with -gl parameter enabled.
>
> That's incorrect.
I only have a 64-bit system at work. I'll post a sample program and
output to show the issue on Monday. The issue appears in fpcunit
On 02 Oct 2010, at 16:43, Graeme Geldenhuys wrote:
> On 02/10/2010, Juha Manninen (gmail) wrote:
>> Anyway, I made a clean build wirh -gl and still had the problem. I will do
>> some more experiments...
>
> Debug and Line Info information is missing in FPC under 64-bit Linux,
> even with -gl pa
Hello FPC-Pascal,
Saturday, October 2, 2010, 3:07:36 PM, you wrote:
JMg> Forgot to tell, I compiled with "-gw -gh".
JMg> "-gw" should be as good as "-gl".
JMg> Now I tried with -gl but no luck. I get an Assembly window:
JMg> http://koti.phnet.fi/juhamann/Lazarus/AssemblyRangeCheck.jpg
JMg> but
On 02 Oct 2010, at 16:35, Juha Manninen (gmail) wrote:
> On Saturday 02 October 2010 16:45:51 Jonas Maebe wrote:
>>> Forgot to tell, I compiled with "-gw -gh".
>>> "-gw" should be as good as "-gl".
>>
>> It has nothing to do with being "as good as", they do different things
>> (just like "-gw" a
On 02/10/2010, Juha Manninen (gmail) wrote:
> Anyway, I made a clean build wirh -gl and still had the problem. I will do
> some more experiments...
Debug and Line Info information is missing in FPC under 64-bit Linux,
even with -gl parameter enabled. This is clearly noticeable if you use
the 'fpp
On Saturday 02 October 2010 16:45:51 Jonas Maebe wrote:
> > Forgot to tell, I compiled with "-gw -gh".
> > "-gw" should be as good as "-gl".
>
> It has nothing to do with being "as good as", they do different things
> (just like "-gw" and "-gh" do different things).
I have used only -gw and debug
On Saturday 02 October 2010 16:22:02 Honza wrote:
> I just tried and can confirm that a LCL app running inside Lazarus
> (r27491), having turned on range checks is able to perfectly catch and
> show the place of an range check error (Ubuntu 10.04/AMD64). What I've
> not tried, but suggest to try, i
On 02 Oct 2010, at 15:07, Juha Manninen (gmail) wrote:
> On Saturday 02 October 2010 12:21:20 Jonas Maebe wrote:
>> Compile with -gl, or set a breakpoint on FPC_RANGEERROR
>
> Forgot to tell, I compiled with "-gw -gh".
> "-gw" should be as good as "-gl".
It has nothing to do with being "as good
On 02/10/2010, Michael Van Canneyt wrote:
>
> None exist, but I'm interested in having it in the FCL.
OK, thanks. I'll continue the implementation then. I'm planing on
making it flexible, so the backend can be swapped out with other
implementations - similar to what one can do with fpTimer. I'll
2010/10/2 Juha Manninen (gmail) :
Hi Juha,
I just tried and can confirm that a LCL app running inside Lazarus
(r27491), having turned on range checks is able to perfectly catch and
show the place of an range check error (Ubuntu 10.04/AMD64). What I've
not tried, but suggest to try, is to open the
On Sat, 2 Oct 2010, Graeme Geldenhuys wrote:
Hi,
Does the RTL or FCL have a file or directory change notification
component. I'm about to write one, but if one already exists, it could
save me some time. I looked through the FCL directory but couldn't
find anything obvious.
None exist, but
On Saturday 02 October 2010 12:21:20 Jonas Maebe wrote:
> Compile with -gl, or set a breakpoint on FPC_RANGEERROR
Forgot to tell, I compiled with "-gw -gh".
"-gw" should be as good as "-gl".
Now I tried with -gl but no luck. I get an Assembly window:
http://koti.phnet.fi/juhamann/Lazarus/Assembl
Hello, Graeme!
> Does the RTL or FCL have a file or directory change notification component.
> I'm about to write one, but if one already exists, it could save me some time.
> I looked through the FCL directory but couldn't find anything obvious.
AFAIK, there are no components like the one you me
Hi,
Does the RTL or FCL have a file or directory change notification
component. I'm about to write one, but if one already exists, it could
save me some time. I looked through the FCL directory but couldn't
find anything obvious.
--
Regards,
- Graeme -
___
On 02 Oct 2010, at 11:15, Juha Manninen (gmail) wrote:
> I asked this on Lazarus list but it belongs better here.
> So, how to get to the source line that gives a range check error?
Compile with -gl, or set a breakpoint on FPC_RANGEERROR
Jonas
___
fp
Hi
I asked this on Lazarus list but it belongs better here.
So, how to get to the source line that gives a range check error?
I built the whole Lazarus with -Cr and debug it. When the range error happens,
it only shows a RunError or similar and doesn't show me the faulty source
line.
When closi
18 matches
Mail list logo
