Mercurial > hg > index.cgi
view docs/readme-4.0.txt @ 577:e49d24f4a9a5
Correct bug in the object file output code leading to stack corruption
It turns out leaving a pointer to a stack allocated temporary in a
persistent data structure is not conducive to correct program operation.
Undo the export check setup in the object file output sequence so a
pointer to stack allocated memory is not left hanging when the function
returns. This seems to correct at least one mysterious crash bug, and
possibly others.
Thanks to Boisy Pitre for reporting the crash bug that led to this
discovery, as well as a previous crash bug that likely has the same
root cause.
Additional thanks to Ciaran Anscomb whose debugger wielding wizardry
revealed the exact location of this particular bit of unbrilliance.
author | William Astle <lost@l-w.ca> |
---|---|
date | Sat, 03 Aug 2024 14:30:06 -0600 |
parents | 2c24602be78f |
children |
line wrap: on
line source
With LWTOOLS 4.0, a substantial reorganization of the project has occurred. This document serves to explain the reasoning behind the various changes. The most obvious change is that the gnu auto tools have been eliminated. While they proved useful for initial distribution of the software, particularly for construction of the win32 binaries, they have since proved to add an unacceptable level of complexity to every aspect of development from merely tinkering with source files to doing complete releases. Thus, the auto tools have been ditched in favour of specific hand tuned help where required. The other substantial change is that the source code repository has been recreated from scratch. The old repository was full of cruft from various revision control systems that were used over the years (CVS, Subversion, and Mercurial). It was felt that starting a new Mercurial repository with a completely clean slate would simplify matters substantially. Thus, the old repository now serves as an archive.