nbackup segfaults and leaves db locked when not enough free disk space
--
Key: CORE-3481
URL: http://tracker.firebirdsql.org/browse/CORE-3481
Project: Firebird Core
Issue
On 17/05/2011 08:27, Vlad Khorsun wrote:
What about the following - we always pass status vector to release().
I'm sorry but i against it. addRef\release is and well known pair and its
usage also well known. I see no good reason to change it. More, if we
need to change it, then we use it
Speaking about documentation i'd said we must document usage of every
public
interface and specify explicitly how instance is constructed and destroyed.
Well - with this adjustment I can agree with every style.
(Though must say that addRef/release pair in our interfaces is already
On 05/17/11 16:07, Vlad Khorsun wrote:
To support wrong code and solve nothing. With the cost of all this mess,
all this otherwise unneeded discussion, all the global/local pool mess.
...only emotions and offence...
Agreed - nothing except emotions ...
On 17/05/2011 04:05, Alex Peshkoff wrote:
In FB2.5 yValve did not need any more MT-safeness except provided by
atomic counters and some helper locks like hanlers' map RwLock.
Initially I've planned to keep same approach for FB3. But I did not
review latest Adriano's changes from this POV.
I
On Tue, May 17, 2011 at 7:11 AM, Damyan Ivanov d...@debian.org wrote:
[Full CC for debiandevel]
-=| Damyan Ivanov, Mon, May 16, 2011 at 09:12:27PM +0300 |=-
-=| Ondřej Surý, Mon, May 16, 2011 at 05:27:53PM +0200 |=-
Hi Marius,
On Mon, May 16, 2011 at 16:39, marius adrian popa
PS: There is a paper
(http://www.aristeia.com/Papers/DDJ_Jul_Aug_2004_revised.pdf) from Scott
Meyers and Andrei Alexandrescu showing even or volatile usage in base
classes are wrong. Unfortunately it's down.
With MSVC we are safe as we use volatile and compiler used read\write
memory
On 17-05-2011 19:58, Vlad Khorsun wrote:
PS: There is a paper
(http://www.aristeia.com/Papers/DDJ_Jul_Aug_2004_revised.pdf) from Scott
Meyers and Andrei Alexandrescu showing even or volatile usage in base
classes are wrong. Unfortunately it's down.
With MSVC we are safe as we use
On 17-05-2011 19:58, Vlad Khorsun wrote:
PS: There is a paper
(http://www.aristeia.com/Papers/DDJ_Jul_Aug_2004_revised.pdf) from Scott
Meyers and Andrei Alexandrescu showing even or volatile usage in base
classes are wrong. Unfortunately it's down.
With MSVC we are safe as we use
