Difference between revisions of "Issues 2.6.0"

From Lazarus wiki
Jump to navigationJump to search
(→‎Merge requests for post RC1 fixes so far: Updated for postrc1 merge, first tranche)
Line 15: Line 15:
  
 
# <strike>r19515 already merged (typo in winunits-base shlobj.pp)</strike>
 
# <strike>r19515 already merged (typo in winunits-base shlobj.pp)</strike>
# r19380 bug in exesearch
+
# <strike>r19380 bug in exesearch</strike>
# r19485 fpunits.conf->.cfg
+
# <strike>r19485 fpunits.conf->.cfg</strike>
# r19486 safecall on win64 flag in i_win.pas
+
# <strike>r19486 safecall on win64 flag in i_win.pas</strike>
 
# r19525 Fix problem with QueryHook leading to crashes
 
# r19525 Fix problem with QueryHook leading to crashes
 
# r19526,r19531 haiku (confirmed by Olivier)
 
# r19526,r19531 haiku (confirmed by Olivier)
 
# r19342 nativent system unit (nativent dir only)
 
# r19342 nativent system unit (nativent dir only)
 
# Jonas and Florian would discuss what to do with <b>r18961/r19312/r19313</b> ? -> still ongoing
 
# Jonas and Florian would discuss what to do with <b>r18961/r19312/r19313</b> ? -> still ongoing
# <b>r19497</b>  check environment variable LOCALAPPDATA on windows as a possible cache location for instantfpc
+
# <strike><b>r19497</b>  check environment variable LOCALAPPDATA on windows as a possible cache location for instantfpc</strike>
 
# <b>r19339</b>  (Francesco) Updated libogcfpc to ver.1.8.8
 
# <b>r19339</b>  (Francesco) Updated libogcfpc to ver.1.8.8
# <b>r19493</b> deprecation msgs of tdbf. Can starting compiler handle this? Does that matter at all for non- compiler/RTL?
+
# <strike><b>r19493</b> deprecation msgs of tdbf. Can starting compiler handle this? Does that matter at all for non- compiler/RTL? -> 2.4.4 can </strike>
  
 
# <b>r19328</b> byte typecast in set declaration gives syntax error (Jonas remarked it has a mantis item target 2.6.0 Mantis #19328 by Paul)
 
# <b>r19328</b> byte typecast in set declaration gives syntax error (Jonas remarked it has a mantis item target 2.6.0 Mantis #19328 by Paul)
 
# <b>r19343</b> mantis 19975 (classhelper, no commit msg) -> looks complex, so initially I'd say deny; Comments?
 
# <b>r19343</b> mantis 19975 (classhelper, no commit msg) -> looks complex, so initially I'd say deny; Comments?
 
# OS/2 merging, many  revs, see [http://www.stack.nl/~marcov/mergelogs26/postrc1.txt] but hinges on <b>r18138</b> causes many conflicts.  (also r19551,r19552)
 
# OS/2 merging, many  revs, see [http://www.stack.nl/~marcov/mergelogs26/postrc1.txt] but hinges on <b>r18138</b> causes many conflicts.  (also r19551,r19552)
 +
## 18138 partially merged, but not marked as merged. Merging 18136 was also needed.
 
# Paul: Fixed today a serious bug which may cause compiler crashes: <b>r19563</b> Without the change any record member symbol was treated as a tfieldvarsym and tfieldvarsym members where accessed without a check.
 
# Paul: Fixed today a serious bug which may cause compiler crashes: <b>r19563</b> Without the change any record member symbol was treated as a tfieldvarsym and tfieldvarsym members where accessed without a check.
 
# fpcbuild r918,926,928
 
# fpcbuild r918,926,928
Line 35: Line 36:
 
##  [http://bugs.freepascal.org/view.php?id=20034|mantis 20034] (improved versioning of CHM's, Marco -- can probably easily be delayed)
 
##  [http://bugs.freepascal.org/view.php?id=20034|mantis 20034] (improved versioning of CHM's, Marco -- can probably easily be delayed)
 
##  [http://bugs.freepascal.org/view.php?id=20482|mantis 20482] (fpmake problem, Joost)
 
##  [http://bugs.freepascal.org/view.php?id=20482|mantis 20482] (fpmake problem, Joost)
 
  
 
== Issues with 2.6.0-rc1 ==
 
== Issues with 2.6.0-rc1 ==
  
 
# (potential) the usage of the heapmanager in a thread before it is initialized (Sergei, fpc-devel, nov 10th "Threads crash on freebsd")
 
# (potential) the usage of the heapmanager in a thread before it is initialized (Sergei, fpc-devel, nov 10th "Threads crash on freebsd")

Revision as of 12:11, 29 November 2011

Issues with 2.6.0 release candidates

This page is supposed to contain all issues discovered while testing release candidates and their status. Make sure to include information about the platform where the problem appears (if applicable). Once the issue gets resolved, you should strike it over and add number of SVN revision fixing it. If the revision number refers to a SVN repository different from "fpc" (i.e. "fpcbuild" or "fpcdocs"), include information about the SVN repository too.

Example:

  1. cpu-os: IE209101221 while compiling XYZ.pas - r123456
  2. docs: missing description of XYZ
  3. readme.txt: wrong version number - r654321 (fpcbuild)


Merge requests for post RC1 fixes so far

strikken means merged, bold means decisions/review/actions needed.

  1. r19515 already merged (typo in winunits-base shlobj.pp)
  2. r19380 bug in exesearch
  3. r19485 fpunits.conf->.cfg
  4. r19486 safecall on win64 flag in i_win.pas
  5. r19525 Fix problem with QueryHook leading to crashes
  6. r19526,r19531 haiku (confirmed by Olivier)
  7. r19342 nativent system unit (nativent dir only)
  8. Jonas and Florian would discuss what to do with r18961/r19312/r19313 ? -> still ongoing
  9. r19497 check environment variable LOCALAPPDATA on windows as a possible cache location for instantfpc
  10. r19339 (Francesco) Updated libogcfpc to ver.1.8.8
  11. r19493 deprecation msgs of tdbf. Can starting compiler handle this? Does that matter at all for non- compiler/RTL? -> 2.4.4 can
  1. r19328 byte typecast in set declaration gives syntax error (Jonas remarked it has a mantis item target 2.6.0 Mantis #19328 by Paul)
  2. r19343 mantis 19975 (classhelper, no commit msg) -> looks complex, so initially I'd say deny; Comments?
  3. OS/2 merging, many revs, see [1] but hinges on r18138 causes many conflicts. (also r19551,r19552)
    1. 18138 partially merged, but not marked as merged. Merging 18136 was also needed.
  4. Paul: Fixed today a serious bug which may cause compiler crashes: r19563 Without the change any record member symbol was treated as a tfieldvarsym and tfieldvarsym members where accessed without a check.
  5. fpcbuild r918,926,928
  6. open tickets with 2.6.0 as target
    1. 18702 (error in rewritten win32 cdecl handling, Joost)
    2. 20034 (improved versioning of CHM's, Marco -- can probably easily be delayed)
    3. 20482 (fpmake problem, Joost)

Issues with 2.6.0-rc1

  1. (potential) the usage of the heapmanager in a thread before it is initialized (Sergei, fpc-devel, nov 10th "Threads crash on freebsd")