[Firebird-devel] Builds with USE_VALGRIND fail
When I build HEAD with --enable-developer and -DUSE_VALGRIND I get
these errors:
alloc.cpp:2182:79: error: invalid conversion from ‘size_t (*)(size_t) {aka
long unsigned int (*)(long unsigned int)}’ to ‘unsigned int’ [-fpermissive]
common.h:772:51: error: invalid operands of types ‘size_t (*)(size_t) {aka
long unsigned int (*)(long unsigned int)}’ and ‘size_t {aka long unsigned
int}’ to binary ‘operator&’ #define ROUNDUP(n, b)(((n) + (b) - 1)
& ~((b) - 1))
alloc.cpp:2306:16: error: invalid operands of types ‘size_t {aka long
unsigned int}’ and ‘size_t (*)(size_t) {aka long unsigned int (*)(long
unsigned int)}’ to binary ‘operator-’ size = length - (VALGRIND_REDZONE +
GUARD_BYTES);
Similar errors appear when building B3_0_Release.
Should I log this as a bug?
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Builds with USE_VALGRIND fail
On 11/26/20 11:15 AM, Paul Reeves wrote:
When I build HEAD with --enable-developer and -DUSE_VALGRIND I get
these errors:
alloc.cpp:2182:79: error: invalid conversion from ‘size_t (*)(size_t) {aka
long unsigned int (*)(long unsigned int)}’ to ‘unsigned int’ [-fpermissive]
common.h:772:51: error: invalid operands of types ‘size_t (*)(size_t) {aka
long unsigned int (*)(long unsigned int)}’ and ‘size_t {aka long unsigned
int}’ to binary ‘operator&’ #define ROUNDUP(n, b)(((n) + (b) - 1)
& ~((b) - 1))
alloc.cpp:2306:16: error: invalid operands of types ‘size_t {aka long
unsigned int}’ and ‘size_t (*)(size_t) {aka long unsigned int (*)(long
unsigned int)}’ to binary ‘operator-’ size = length - (VALGRIND_REDZONE +
GUARD_BYTES);
Similar errors appear when building B3_0_Release.
Should I log this as a bug?
Useally we do not log DEV_BUILD problems (first of all not to confuse
users I think), I will take a look what's wrong.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Builds with USE_VALGRIND fail
On 11/26/20 12:05 PM, Alex Peshkoff via Firebird-devel wrote: Useally we do not log DEV_BUILD problems (first of all not to confuse users I think), I will take a look what's wrong. fixed Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Reserving a new error code facility
I'm currently writing a driver for the R2DBC specification (a new Java specification for reactive database drivers). Is it OK if I reserve a new facility code for R2DBC driver errors (similar like I did in the past for Jaybird)? Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
