Op 2010-10-05 11:17, Michael Van Canneyt het geskryf:
>
> so your statement should have been 'debug and line info information is
> incomplete', instead of 'missing'
It was for "dramatic effect" :) You are right, my initial statement
was a bit wrong - I didn't have the code or output in
On Tue, 5 Oct 2010, Graeme Geldenhuys wrote:
Hi Jonas
On 2 October 2010 16:51, Jonas Maebe wrote:
Debug and Line Info information is missing in FPC under 64-bit Linux,
even with -gl parameter enabled.
That's incorrect.
See the bug report for details. Not all the information available
un
Hi Jonas
On 2 October 2010 16:51, Jonas Maebe wrote:
>
> Debug and Line Info information is missing in FPC under 64-bit Linux,
> even with -gl parameter enabled.
>
> That's incorrect.
See the bug report for details. Not all the information available
under 32-bit FPC is available under 64-bit FPC
On 03/10/2010 21:20, Juha Manninen (gmail) wrote:
On Sunday 03 October 2010 19:48:22 C Western wrote:
Please report the bug. Yes the result is integer and in 64 bits, this
looks like a problem.
I think this is an issue I reported back in March, though I can now see
I uploaded the wrong patch f
On Sunday 03 October 2010 23:20:05 Juha Manninen (gmail) wrote:
> Anyway this is a good example of a valid Lazarus patch that is ignored,
> again. :-(
Ok, sorry Lazarus guys, I must take this one back.
The valid patch was uploaded only today so it was not really ignored.
Now there are 2 valid pa
On Sunday 03 October 2010 19:48:22 C Western wrote:
> >> Please report the bug. Yes the result is integer and in 64 bits, this
> >> looks like a problem.
> >
> > I think this is an issue I reported back in March, though I can now see
> > I uploaded the wrong patch for it
>
> Sorry - meant to add:
On 10/03/2010 05:36 PM, C Western wrote:
On 10/03/2010 04:48 PM, José Mejuto wrote:
Hello FPC-Pascal,
Sunday, October 3, 2010, 9:10:34 AM, you wrote:
JMg> Lazarus Debugger code causes one range error which can be fixed
with a
JMg> typecast. FPC showed the point clearly. Issue #0017537.
JMg> TA
On 10/03/2010 04:48 PM, José Mejuto wrote:
Hello FPC-Pascal,
Sunday, October 3, 2010, 9:10:34 AM, you wrote:
JMg> Lazarus Debugger code causes one range error which can be fixed with a
JMg> typecast. FPC showed the point clearly. Issue #0017537.
JMg> TApplication.HandleException Range check
Hello FPC-Pascal,
Sunday, October 3, 2010, 11:41:00 AM, you wrote:
GG> On 02/10/2010, Vincent Snijders wrote:
>>
>> True heap size : 1048576
>> True free heap : 1924768
>> Should be : 1048576
>>
>> It just says that heaptr didn't calculate the True free heap size correctly.
GG> Either way, this
Hello FPC-Pascal,
Sunday, October 3, 2010, 9:10:34 AM, you wrote:
JMg> Lazarus Debugger code causes one range error which can be fixed with a
JMg> typecast. FPC showed the point clearly. Issue #0017537.
JMg> TApplication.HandleException Range check error
JMg> Stack trace:
JMg> $0115AA
On 02/10/2010, Vincent Snijders wrote:
>
> True heap size : 1048576
> True free heap : 1924768
> Should be : 1048576
>
> It just says that heaptr didn't calculate the True free heap size correctly.
Either way, this should then be reported as a bug - though a minor one
because unfree'ed count is c
On Saturday 02 October 2010 17:47:27 José Mejuto wrote:
> The assembly window in Lazarus is shown when no backtrace line is
> available to point the cursor in, so open callstack "View -> Debug ->
> Callstack" and you will see that there is no available backtrace,
> maybe except the fpc sources with
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
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 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
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
26 matches
Mail list logo
