[Firebird-devel] [FB-Tracker] Created: (CORE-4644) Get both "335545060 : Missing security context " and "335544344 : I/O error during "open" operation" for existing database under heavy concurrent DML

2014-12-19 Thread Pavel Zotov (JIRA)
Get both "335545060 : Missing security context " and "335544344 : I/O error during "open" operation" for existing database under heavy concurrent DML

Re: [Firebird-devel] CMake build system

2014-12-19 Thread Egor Pugin
I updated the build system, so it is nearly twice faster than before. yvalve and Engine12 sources (not .epp) are compiled only once during the build. You can try on linux to see if there is still some annoying steps during rebuild. Also I added project groups to the project tree (boot, extern, exa

[Firebird-devel] [FB-Tracker] Created: (CORE-4643) Memory leak in FB 3.0 under brute-force attack

2014-12-19 Thread Pavel Zotov (JIRA)
Memory leak in FB 3.0 under brute-force attack -- Key: CORE-4643 URL: http://tracker.firebirdsql.org/browse/CORE-4643 Project: Firebird Core Issue Type: Bug Components: Security

[Firebird-devel] [FB-Tracker] Created: (CORE-4642) Can't connect to database without path from CWD when DatabaseAccess is restricted

2014-12-19 Thread Pavel Cisar (JIRA)
Can't connect to database without path from CWD when DatabaseAccess is restricted - Key: CORE-4642 URL: http://tracker.firebirdsql.org/browse/CORE-4642 Project: Firebird

[Firebird-devel] [FB-Tracker] Created: (CORE-4641) let FB3 can have security database specified in the connection string

2014-12-19 Thread Arioch (JIRA)
let FB3 can have security database specified in the connection string - Key: CORE-4641 URL: http://tracker.firebirdsql.org/browse/CORE-4641 Project: Firebird Core Issue Type

Re: [Firebird-devel] [PATCH] Fix mingw build using posix environment

2014-12-19 Thread Alexey Pavlov
2014-12-19 12:08 GMT+03:00 Alexey Pavlov : > > > > 2014-12-19 0:15 GMT+03:00 Alexpux : >> >> >> > 18 дек. 2014 г., в 15:45, Alexpux написал(а): >> > >> > >> >> 18 дек. 2014 г., в 15:42, Michal Kubecek написал(а): >> >> >> >> On Thu, Dec 18, 2014 at 03:37:04PM +0300, Alexpux wrote: >> >>> >>

Re: [Firebird-devel] [PATCH] Fix mingw build using posix environment

2014-12-19 Thread Alexey Pavlov
2014-12-19 0:15 GMT+03:00 Alexpux : > > > > 18 дек. 2014 г., в 15:45, Alexpux написал(а): > > > > > >> 18 дек. 2014 г., в 15:42, Michal Kubecek написал(а): > >> > >> On Thu, Dec 18, 2014 at 03:37:04PM +0300, Alexpux wrote: > >>> > 18 дек. 2014 г., в 15:29, Alex Peshkoff > написал(а): >

Re: [Firebird-devel] [PATCH] Cobol interface

2014-12-19 Thread Dmitry Yemanov
19.12.2014 10:05, Alexpux wrote: > > Next patch works for me. Applied. Dmitry -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboard

Re: [Firebird-devel] [PATCH] Cobol interface

2014-12-19 Thread Alexpux
> 19 дек. 2014 г., в 11:41, Dmitry Yemanov написал(а): > > 19.12.2014 11:34, Alexpux wrote: >> >> Looking into Cobol module I see there are lot of this such things. Also >> maybe need there replace deprecated procedures like «isc_interprete». > > IIRC, Cobol support exists for 32-bits only, s

Re: [Firebird-devel] [PATCH] Cobol interface

2014-12-19 Thread Dmitry Yemanov
19.12.2014 11:34, Alexpux wrote: > > Looking into Cobol module I see there are lot of this such things. Also maybe > need there replace deprecated procedures like «isc_interprete». IIRC, Cobol support exists for 32-bits only, so all these issues are just annoying warnings that never appear in pr

Re: [Firebird-devel] [PATCH] Cobol interface

2014-12-19 Thread Alexpux
> 19 дек. 2014 г., в 11:14, Dmitry Yemanov написал(а): > > 19.12.2014 10:05, Alexpux wrote: >> >> Next patch works for me. > > Doesn't this routine also need fixing: > > EXPORT RM_ENTRY(rmc_baddress) > { > U_IPTR retval = isc_baddress((char *)arg_vector[0].a_address); > *(ISC_ULON

Re: [Firebird-devel] [PATCH] Cobol interface

2014-12-19 Thread Dmitry Yemanov
19.12.2014 10:05, Alexpux wrote: > > Next patch works for me. Doesn't this routine also need fixing: EXPORT RM_ENTRY(rmc_baddress) { U_IPTR retval = isc_baddress((char *)arg_vector[0].a_address); *(ISC_ULONG *)arg_vector[-1].a_address = retval; return (0); } to become: