I updated the previously mentioned issue with information from gdb.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
I am not sure how to backtrace on mantis, but here is the bug report I
submitted. Maybe you can 1.6 RC tag it for me.
http://bugs.freepascal.org/view.php?id=29178
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freep
On 12.12.2015 18:21, Anthony Walter wrote:
I don't know if this has been reported, but on several Lazarus
installations I get a "Division by zero" exception when using the
"Manage desktops" dialog, located under the "Tools -> Desktops ..."
menu. On some systems the error is reported as a floa
I don't know if this has been reported, but on several Lazarus
installations I get a "Division by zero" exception when using the "Manage
desktops" dialog, located under the "Tools -> Desktops ..." menu. On some
systems the error is reported as a floating point exception and crashes
Lazarus badly.
On 2015-12-10 12:05, Mattias Gaertner wrote:
> I guess you mean the zip releases on sourceforge. I added a note to the
> sourceforge README.txt.
Thanks for that.
Regards,
- Graeme -
My public PGP key: http://tinyurl.com/graeme-pgp
--
___
Lazarus
On Thu, 10 Dec 2015 09:24:43 +
Graeme Geldenhuys wrote:
>[...]
> If not already, this info needs to be placed somewhere on the Wiki.
I added the release history here:
http://wiki.lazarus.freepascal.org/Version_Numbering
> Lazarus doesn't supply installers (lazarus + fpc) for all supported
>
On Thu, 10 Dec 2015 10:07:09 +
Mark Morgan Lloyd wrote:
>[...]
> >> ! /usr/local/bin/lazarus-1.4.2+3.0.0
> >
> > 1.4.2 used FPC 2.6.4.
> > 1.6 will be the first release with FPC 3.0.
>
> Those are tested combinations. 1.4.2 (which was the latest 1.4.x when I
> did the work) works reliably
Mattias Gaertner wrote:
On Wed, 09 Dec 2015 14:31:20 +
Mark Morgan Lloyd wrote:
[...]
Quite frankly I feel that the Lazarus version numbering is progressing
faster than is reasonable, and that it would be highly desirable to have
a "Long Term Support" v2.0.x or even 3.0.x which could be
On 2015-12-09 15:27, Mattias Gaertner wrote:
>> >[...]
>> > ! /usr/local/bin/lazarus-0.9.24+2.2.4
>> > ! /usr/local/bin/lazarus-0.9.26+2.2.4
>> > ! /usr/local/bin/lazarus-0.9.28+2.4.0
>> > ! /usr/local/bin/lazarus-0.9.30+2.4.4
>> > ! /usr/local/bin/lazarus-1.0.0+2.4.4
>> > ! /usr/local/bin/lazarus-
On Wed, Dec 09, 2015 at 02:31:20PM +, Mark Morgan Lloyd wrote:
> Quite frankly I feel that the Lazarus version numbering is progressing
> faster than is reasonable, and that it would be highly desirable to have
> a "Long Term Support" v2.0.x or even 3.0.x which could be presented to
> people
Juha Manninen wrote:
On Wed, Dec 9, 2015 at 6:41 PM, Mark Morgan Lloyd
make sure that this is still compatible with FPC 3.0.0. After that try to
slow down the Lazarus numerical progression a bit by using "hundredths"
more.
I think the backwards compatibility of LCL is the most important
deta
On Wed, Dec 9, 2015 at 6:41 PM, Mark Morgan Lloyd
wrote:
> In the interest of making the least amount of work for anybody, my
> suggestion would be to proceed at the current rate towards 2.0.0, but to
> make sure that this is still compatible with FPC 3.0.0. After that try to
> slow down the Lazar
On 12/9/15, Mark Morgan Lloyd wrote:
> In the interest of making the least amount of work for anybody, my
> suggestion would be to proceed at the current rate towards 2.0.0, but to
> make sure that this is still compatible with FPC 3.0.0. After that try
> to slow down the Lazarus numerical progre
Mattias Gaertner wrote:
On Wed, 09 Dec 2015 14:31:20 +
Mark Morgan Lloyd wrote:
[...]
Quite frankly I feel that the Lazarus version numbering is progressing
faster than is reasonable, and that it would be highly desirable to have
a "Long Term Support" v2.0.x or even 3.0.x which could be
El 09/12/15 a les 17:07, Bart ha escrit:
On 12/9/15, Luca Olivetti wrote:
Yes, most probably the bug is in fpc, but note that lazarus 1.4.x had
its own implementation instead of relying on sysutils.
No, it did not.
It also called SysUtils.ExpandUncFilename().
Your bugreport says that it als
On 12/9/15, Luca Olivetti wrote:
> Yes, most probably the bug is in fpc, but note that lazarus 1.4.x had
> its own implementation instead of relying on sysutils.
No, it did not.
It also called SysUtils.ExpandUncFilename().
Your bugreport says that it also translated C:\Windows\..\ into C:\.
Thi
On Wed, Dec 9, 2015 at 4:31 PM, Mark Morgan Lloyd
wrote:
> Quite frankly I feel that the Lazarus version numbering is progressing
> faster than is reasonable, and that it would be highly desirable to have a
> "Long Term Support" v2.0.x or even 3.0.x which could be presented to people
> outside the
On 09/12/2015 15:27, Mattias Gaertner wrote:
On Wed, 09 Dec 2015 14:31:20 +
Mark Morgan Lloyd wrote:
[...]
How about a stable Lazarus v2.0.x, with as many bugs and development
quirks as possible worked out of it, based on FPC 3.0.x and with a
support commitment from both teams?
...
If you
On Wed, 09 Dec 2015 14:31:20 +
Mark Morgan Lloyd wrote:
>[...]
> Quite frankly I feel that the Lazarus version numbering is progressing
> faster than is reasonable, and that it would be highly desirable to have
> a "Long Term Support" v2.0.x or even 3.0.x which could be presented to
> peop
Michael Schnell wrote:
Obviously it will not be in the first 1.6 release, but happily the
Lazarus releases are scheduled a lot more often than the fpc releases,
so I will not have to wait another three years until the code might be
published.
Quite frankly I feel that the Lazarus version num
El 09/12/15 a les 13:53, Bart ha escrit:
On 12/9/15, Luca Olivetti wrote:
this isn't a lazarus bug but most probably a problem with fpc:
ExpandUnCFileNameUTF8 (which in turns calls SystUtils.ExpandUNCFileName)
returns '\' when called with
That's odd, because this is the implementation:
func
On 12/9/15, Luca Olivetti wrote:
> this isn't a lazarus bug but most probably a problem with fpc:
> ExpandUnCFileNameUTF8 (which in turns calls SystUtils.ExpandUNCFileName)
> returns '\' when called with
That's odd, because this is the implementation:
function ExpandUNCFileNameUTF8(const FileNa
On Wed, 9 Dec 2015 15:39:54 +0300
Jamal Gabra wrote:
> >
> > About "faster": You need to give more information what and how you
> > tested.
>
>
> I just compared one project with 1.4.4/3.0.1 | 1.5/3.0.1 against 1.6/3.0.0
> and the time it took was noticeable.
> I tested by compiling same projec
El 09/12/15 a les 13:21, Mattias Gaertner ha escrit:
On Wed, 9 Dec 2015 12:33:08 +0100
Luca Olivetti wrote:
[...]
this isn't a lazarus bug but most probably a problem with fpc:
ExpandUnCFileNameUTF8 (which in turns calls SystUtils.ExpandUNCFileName)
returns '\' when called with
'D:\testfpc\15
On Wed, 09 Dec 2015 12:17:55 +0100
Michael Schnell wrote:
> On 12/09/2015 11:45 AM, Mattias Gaertner wrote:
> >> Application QueuAsyncCall is implemented using TThread.Queue.
> > What is wrong with the current implementation?
> Nothing. But it uses another Queue. Queue handling needs OS calls for
>
> About "faster": You need to give more information what and how you
> tested.
I just compared one project with 1.4.4/3.0.1 | 1.5/3.0.1 against 1.6/3.0.0
and the time it took was noticeable.
I tested by compiling same project, also by rebuilding lazarus, all under
same conditions, and it was ve
On Wed, 9 Dec 2015 15:14:23 +0300
Jamal Gabra wrote:
> >
> > Or do you mean there is a difference between 1.5 and 1.6 compiled with
> > 3.0.1?
>
>
> Exactly. I do not compare against earlier versions. Instead I compared
> Laz1.4.4&fpc3.0.1 against Laz1.5&fpc3.0.1 against Laz1.6RC1&fpc3.0.0
Wha
On Wed, 9 Dec 2015 12:33:08 +0100
Luca Olivetti wrote:
>[...]
> this isn't a lazarus bug but most probably a problem with fpc:
> ExpandUnCFileNameUTF8 (which in turns calls SystUtils.ExpandUNCFileName)
> returns '\' when called with
>
> 'D:\testfpc\15044_videowall\servidor\..\datos\'
>
> (with
>
> Or do you mean there is a difference between 1.5 and 1.6 compiled with
> 3.0.1?
Exactly. I do not compare against earlier versions. Instead I compared
Laz1.4.4&fpc3.0.1 against Laz1.5&fpc3.0.1 against Laz1.6RC1&fpc3.0.0
On Wed, Dec 9, 2015 at 2:48 PM, Mattias Gaertner
wrote:
> On Wed, 9 De
On Wed, 9 Dec 2015 14:25:32 +0300
Jamal Gabra wrote:
>[...]
> I am sorry for not been specific enough.
> I was using Laz1.4.4 (fixes) & 1.5 with fpc3.0.1
>
> I meant with the above mentioned versions, normal compile and run, would
> generate smaller exe and faster.
Do you mean apps compiled wit
El 08/12/15 a les 16:19, Mattias Gaertner ha escrit:
== Why should everybody (including you) test the release candidate? ==
In the past weeks the Lazarus team has stabilized the 1.6 fixes branch. The
resulting 1.6RC1 is now stable enough to be used by any one for test purposes.
this
>
> Do you mean LCL 1.6 applications compiled with FPC 2.6.4 are smaller
> and faster than compiled with FPC 3.0?
I am sorry for not been specific enough.
I was using Laz1.4.4 (fixes) & 1.5 with fpc3.0.1
I meant with the above mentioned versions, normal compile and run, would
generate smaller ex
On 12/09/2015 11:51 AM, Mattias Gaertner wrote:
Meaning your argument is flawed, because it can be prolonged to
infinity.
Don't wait for releases. Start coding now and tell your users
what FPC version is needed.
Coding is done. It works.
I'll Stop talking about it.
-Michael
--
_
On 12/09/2015 11:27 AM, Juha Manninen wrote:
Michael Schnell, please don't hijack this RC1 thread for your General
Ooops I did it again. :-(
You are absolutely correct (I got carried away by the answers I got, I
intended to provoke just a Yes or a No)
I'll stop answering here.
Thanks,
-Mich
On 12/09/2015 11:45 AM, Mattias Gaertner wrote:
Application QueuAsyncCall is implemented using TThread.Queue.
What is wrong with the current implementation?
Nothing. But it uses another Queue. Queue handling needs OS calls for
waiting. I want to avoid to do any OS Calls so I simply use what th
On Wed, 9 Dec 2015 06:30:02 +0300
Jamal Gabra wrote:
> Many thanks Laz Team.
>
> Keep up the good work.
>
> I do have one observation though, Laz1.4.4 (fixes) and Laz Trunk 1.5 were a
> bit faster and the generated exe was ~300kb smaller than the one from 1.6.
1.6 is the former 1.5.
Do you mea
On Wed, 09 Dec 2015 11:10:36 +0100
Michael Schnell wrote:
> On 12/08/2015 05:49 PM, Mattias Gaertner wrote:
> > As I said, that's a straw man. I bet in 3 years from now you will find
> > a distro without an official FPC 3.
>
> Meaning I should wait another three years ?
Meaning your argument i
On Wed, 09 Dec 2015 11:08:48 +0100
Michael Schnell wrote:
> On 12/08/2015 05:59 PM, Mattias Gaertner wrote:
> > For example?
>
> TTimer is implemented using the timeout in checksynchronize().
Looks perfectly fitting for the NoGUI widgetset to me.
> Application QueuAsyncCall is implemented u
On Wed, Dec 9, 2015 at 5:16 AM, Anthony Walter wrote:
> I was looking through my mail trying to find the patch Ondrej created for
> dotted namespace code completion in CodeTools but I can't find it. has that
> been accepted into this release?
No need to look for patches. Look for commit history i
Michael Schnell, please don't hijack this RC1 thread for your General
Service Application thing.
Open a new thread for it.
Juha
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
On 12/08/2015 05:49 PM, Mattias Gaertner wrote:
As I said, that's a straw man. I bet in 3 years from now you will find
a distro without an official FPC 3.
Meaning I should wait another three years ?
No real problem with me.
-Michael
--
___
Lazaru
On 12/08/2015 05:59 PM, Mattias Gaertner wrote:
For example?
TTimer is implemented using the timeout in checksynchronize().
Application QueuAsyncCall is implemented using TThread.Queue.
A new application type requires a design time package.
That means after installing the package, the appl
Many thanks Laz Team.
Keep up the good work.
I do have one observation though, Laz1.4.4 (fixes) and Laz Trunk 1.5 were a
bit faster and the generated exe was ~300kb smaller than the one from 1.6.
PS: Please do not treat this as a complain of any kind, this is just an
observation, in case it make
Mattias,
I was looking through my mail trying to find the patch Ondrej created for
dotted namespace code completion in CodeTools but I can't find it. has that
been accepted into this release?
Also, I created a fix for tray icons on Unity (TTrayIcon plain doesn't work
on it), but it would seem a r
On 08/12/2015 15:19, Mattias Gaertner wrote:
The Lazarus team is glad to announce the first release candidate of Lazarus 1.6.
This release was built with FPC 3.0.0.
The previous release Lazarus 1.4.4 was built with FPC 2.6.4.
checksums on our website
http://www.lazarus-ide.org/index.php?page
Thanks go out to everyone for their work on Lazarus. I'll test and report
back.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
On Tue, 08 Dec 2015 17:22:04 +0100
Michael Schnell wrote:
>[...]
> But it might be a lot of work just finding out what to do and it might
> be dangerous that something not obviously related is broken.
Send patches and people can help.
> > You can either extend the nogui widgetset and send u
On Tue, 08 Dec 2015 17:24:46 +0100
Michael Schnell wrote:
>[...]
> A Lazarus user who wants to use the Widget Type should not be forced to
> use a not yet released version of fpc.
As I said, that's a straw man. I bet in 3 years from now you will find
a distro without an official FPC 3.
Mattia
On 12/08/2015 05:09 PM, Mattias Gaertner wrote:
That's a straw man argument. Every single revision of FPC is
published. Many projects use and/or support FPC 2.7+ since several years.
The code relies on TThread.Queue.
The first released version of fpc that (hopefully) has TThread.Queue is
3.0.
On 12/08/2015 05:03 PM, Mattias Gaertner wrote:
On Tue, 08 Dec 2015 16:44:49 +0100
Michael Schnell wrote:
[...]
AFAIK, the existing Widget Type is selected in the IDE by setting it in
"Additions and Overrides" and/or by selecting an appropriate application
type when creating a new project.
Of
On Tue, 08 Dec 2015 16:44:49 +0100
Michael Schnell wrote:
>[...]
> Obviously it will not be in the first 1.6 release, but happily the
> Lazarus releases are scheduled a lot more often than the fpc releases,
> so I will not have to wait another three years until the code might be
> published.
On Tue, 08 Dec 2015 16:44:49 +0100
Michael Schnell wrote:
>[...]
> AFAIK, the existing Widget Type is selected in the IDE by setting it in
> "Additions and Overrides" and/or by selecting an appropriate application
> type when creating a new project.
>
> Of course I can't modify the IDE to supp
On 12/08/2015 04:19 PM, Mattias Gaertner wrote:
The Lazarus team is glad to announce the first release candidate of Lazarus 1.6.
This release was built with FPC 3.0.0.
The previous release Lazarus 1.4.4 was built with FPC 2.6.4.
Great !
So there will be a Lazarus release that relies on fpc 3.
53 matches
Mail list logo
