issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-04 05:59:17 +0100
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-12-14 06:55:51 +0100
## Comment 6226
Date: 2006-11-04 17:59:17 +0100
From: Wouter Alink <<alink>>
MapiClient --help sais that 'dm' is the default
serialization mode for XQuery
however, "MapiClient -lxq" starts in 'xml' mode when i
do not provide the -o option.
p.s. i strongly agree with 'dm' being the default
serialization mode.
using pf 0.13.1
## Comment 6227
Date: 2006-12-14 18:55:51 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
I have fulfilled your wish: dm is default mode again
## Comment 6228
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590546 at http://sourceforge.net/support/tracker.php?aid=1590546
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: dm vs xml | https://api.github.com/repos/MonetDB/MonetDB/issues/1110/comments | 0 | 2020-11-30T09:21:21Z | 2024-06-27T11:20:50Z | https://github.com/MonetDB/MonetDB/issues/1110 | 753,304,909 | 1,110 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-04 05:11:47 +0100
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-02-20 11:05:30 +0100
## Comment 6220
Date: 2006-11-04 17:11:47 +0100
From: Wouter Alink <<alink>>
fn:substring-after("abcdef","x")
should return "" according to the specs, but instead it
returns the whole string "abcdef".
(bug seems to appear in both 0.12.1 as 0.13.1).
see:
http://www.w3.org/TR/xquery-operators/func-substring-after
## Comment 6221
Date: 2006-11-05 18:40:44 +0100
From: @drstmane
Logged In: YES
user_id=572415
test added in
pathfinder/tests/BugTracker/Tests/substring-after.SF-1590523.xq
fails as reported
## Comment 6222
Date: 2007-02-19 15:44:29 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
The bug is triggered by the implementation of the MIL proc locate which returns 0 on error which is not distinguishable from a match at the start of the string.
Assigning to Peter to decide whether locate (in module str) should be changed.
## Comment 6223
Date: 2007-02-20 09:10:23 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The locate proc is used by sql for the implementation of POSITION(str in str) which should return 0 on errors, ie locate works just fine.
## Comment 6224
Date: 2007-02-20 11:05:30 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
I misinterpreted the definition of the PROC locate() in the str module. You *can* see the difference between a match and a non-match since it returns a match at the start as 1.
So the fix is simply to check the result to see whether there was a match and act accordingly.
This has now been implemented.
A test had already been provided and works.
## Comment 6225
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590523 at http://sourceforge.net/support/tracker.php?aid=1590523
| XQ: substring-after | https://api.github.com/repos/MonetDB/MonetDB/issues/1109/comments | 0 | 2020-11-30T09:21:18Z | 2024-06-27T11:20:49Z | https://github.com/MonetDB/MonetDB/issues/1109 | 753,304,864 | 1,109 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-04 02:37:49 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-12-02 01:09:55 +0100
## Comment 6215
Date: 2006-11-04 14:37:49 +0100
From: @drstmane
Since Thursday Oct 91 2006 i.e., after checkins on
Wednesday Oct 18 2006 the following tests produce an extra
!ERROR: interpret_params: leftfetchjoin(param 2):
evaluation error.
in addition to their respective expected error message(s).
Is this intended (i.e., a "feature") or unintended
(i.e., a BUG)?
In the first case, please approve the new output as
correct/expected;
in the second case, please locate and fix the bug.
The related checkins are:
====================================================================
2006/10/17 - boncz: compiler/mil/milprint_summer.c,1.284
runtime/pathfinder.mx,1.252
*** empty log message ***
==================================================================
2006/10/18 - tsheyar: compiler/mil/milgen.brg,1.52
-- Fix in milgen.brg: the translation of the sort
operator now also copes
with sort operators that have no sort criterion.
(This might occur if
we have a cost overflow.)
===================================================================
2006/10/18 - tsheyar: compiler/algebra/planner.c,1.28
-- Small optimization in planner.c: If we have to
ensure a ordering that
is empty we do not need to add sort operators at all.
===================================================================
2006/10/18 - boncz: compiler/mil/milprint_summer.c,1.285
- improvements to subsequence and translate/replace
as suggested by Jan Rittinger:
You however ignore the return code of the first two
arguments and just
assume that they are DBL and not NORMAL. Some operators
can only return
their results in NORMAL mode. Thus we *always* have to
support the
NORMAL version (-- the other variants are only
optimizations).
>
> Now I put an assert in the replace/translate code to
only work for VALUES.
> Is actually possible that the strictly xs:string
typed functions
> replace/translate will ever be called with NORMAL?
> If so, is there an easy way to convert STR to NORMAL?
Yes -- just use 'addValues'.
e.g. if your result is in a MIL variable 'str_res' just
add:
if (code == NORMAL)
addValues (f, str_container(), "str_res",
"item");
else
milprintf(f, "item%s := str_res;\n",
item_ext);
===================================================================
## Comment 6216
Date: 2006-11-04 14:39:00 +0100
From: @drstmane
Logged In: YES
user_id=572415
oops, forgot to name the tests:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/shred_at_depth_258.SF-1174747.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1267018.swallowed_error_messages-1.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1267018.swallowed_error_messages-2.out.00.html
## Comment 6217
Date: 2006-11-12 12:31:48 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/shred_at_depth_258.SF-1174747.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1267018.swallowed_error_messages-1.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1267018.swallowed_error_messages-2.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/shred_at_depth_258.SF-1174747.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1267018.swallowed_error_messages-1.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1267018.swallowed_error_messages-2.out.00.html
## Comment 6218
Date: 2006-12-02 01:09:55 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
fixed
## Comment 6219
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590471 at http://sourceforge.net/support/tracker.php?aid=1590471
| XQ: tests produce new error message; Bug or Feature? | https://api.github.com/repos/MonetDB/MonetDB/issues/1108/comments | 0 | 2020-11-30T09:21:14Z | 2024-06-28T13:31:57Z | https://github.com/MonetDB/MonetDB/issues/1108 | 753,304,818 | 1,108 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-04 11:30:08 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-01-29 11:37:47 +0100
## Comment 6211
Date: 2006-11-04 11:30:08 +0100
From: @drstmane
Since there is the (pre-)alpha source-only "release" of
"MonetDB 4.99.19", the indeed officially released (and
supported) "MonetDB 4.12.0 has "disappeared" from the
downloads page
(http://sourceforge.net/project/showfiles.php?group_id=56967).
To fix this "inconvenience", I strongly propose to
remove/hide the "MonetDB 4.99.19" "release" --- at
least as soon as we release "MonetDB 4.14.0".
In case there are also plans to "release" a new
pre-)alpha source-only version of MonetDB5, I strongly
propose to (a) add a new packages "MonetDB5" (or
"MonetDB/Five" or "MonetDB/V") next to MonetDB and to
(b) give is a release/version number that starts with a "5"
(e.g. "5.0.0-Alpha_1") in order to avoid (1) that the
MonetDB5 alpha "release" "hides" the actual MonetDB4
*release*, and (2) that users get (unnecessarily)
confused by the version numbers.
## Comment 6212
Date: 2007-01-23 00:29:26 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Keep us reminded to take care of this for the upcoming release.
## Comment 6213
Date: 2007-01-29 11:37:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
New packaging clearly separates MonetDB4 & MonetDB5.
## Comment 6214
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590409 at http://sourceforge.net/support/tracker.php?aid=1590409
| SF: MonetDB4 has "disappeared" from downloads page | https://api.github.com/repos/MonetDB/MonetDB/issues/1107/comments | 0 | 2020-11-30T09:21:11Z | 2024-06-27T11:20:47Z | https://github.com/MonetDB/MonetDB/issues/1107 | 753,304,786 | 1,107 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-04 12:16:46 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-11-06 12:59:25 +0100
## Comment 6208
Date: 2006-11-04 00:16:46 +0100
From: @drstmane
below checkin causes test tests/Update/Tests/update.xq
to run for more than 10 minutes (without finishing; did
not test longer timeout), makes Mserver to grow beyond
13 GB, and requires more than 10 GB disk space in
dbfarm and/or xquery_log.
before/without these changes, the test runs in about
2.5 minutes (non-optimized debugging-Mserver) and
Mserver never grows larger than ~350 MB.
===================================================================
2006/11/03 - boncz:
compiler/include/compile_interface.h,1.16
compiler/mil/milprint_summer.c,1.295
runtime/pathfinder.mx,1.262
runtime/pf_support.mx,1.168
new features:
- automatic serialized transaction restart and convoys
for conflict-aborted
transactions.
- better garbage collection after delete_doc (let
ws_destroy that blocked
destruction of a collection throw it away -- the
zombie bat).
- proper support for updating functions
some bugfixes:
- log changes in the qn_histogram column as well (it
needs to be in sync)
- fixed some bugs in the coll_lock locking in pf_support
READS in the master bats are FORBIDDEN as well,
unless the lock is held
still lots of BUGS seen:
- (shred, insert, additive-shred) gives assert
- BBPname errors sfter restart
- with profiked modules, ws_create hangs on pfenter (?)
- nid_rid batgets is way too large (each session adds a
page to id --
maybe related to shredder assert)
- collection_cleanup should remove bats from deleted
collection
from the logger administration
===================================================================
## Comment 6209
Date: 2006-11-06 12:59:25 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
It appears that contrary to expectation the PROP_VAL,
PROP_TEXT, and PROP_COM tables are not marked with
key(true). So do the keeping unique bit ourselves.
(The relevant change was in add_string_bulk which was
changed to lock those tables earlier. The code would have
been correct if the expectation had been true, but since it
wasn't, we got a data explosion due to a Cartesian product.)
No test added since this was found by an existing test.
## Comment 6210
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590234 at http://sourceforge.net/support/tracker.php?aid=1590234
| XQ: test tests/Update/Tests/update.xq crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/1106/comments | 0 | 2020-11-30T09:21:08Z | 2024-06-27T11:20:46Z | https://github.com/MonetDB/MonetDB/issues/1106 | 753,304,749 | 1,106 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-03 08:59:29 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-12-07 06:58:18 +0100
## Comment 6199
Date: 2006-11-03 20:59:29 +0100
From: @drstmane
In runtime/Tests/serialization.milS
xquery("seq" ,query , 0).printf();
yields
!ERROR: monet_sprintf(): at least 1 parameters expected.
after recent code changes.
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/runtime/serialization.out.00.html
## Comment 6200
Date: 2006-11-04 14:23:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
The problem seems to occur since Wednesday Oct 25 2006,
hence, after changes made on Tuesday Oct 24 2006 (see list
below).
The last one seem most related, hence assigning to Fabian;
feel free to pass on once you're it is'n your bug/fault.
===================================================================
2006/10/24 - tsheyar: compiler/algebra/map/intro_proxy.c,1.10
-- FIX in proxy generation:
property inference only works if we start from the root
===================================================================
2006/10/24 - sjoerd: runtime/pathfinder.mx,1.255
Typo.
===================================================================
2006/10/24 - sjoerd: runtime/pf_support.mx,1.163
Fixed myinsert and renamed it myupdate.
Some other small changes.
===================================================================
2006/10/24 - roel_van_os: modules/pftijah/nexi.l,1.10
PF/Tijah: allow semicolon to occur in NEXI query. ; is now a
no-op for
backward compatibility.
===================================================================
2006/10/24 - roel_van_os: modules/pftijah/nexi.c,1.33
PF/Tijah:
- switch off priors by default: does not work well with NLLR yet
- make priors and default score configurable
===================================================================
2006/10/24 - roel_van_os: modules/pftijah/nexi.c,1.34
modules/pftijah/pftijah.mx,1.63
PF/Tijah:
- make default score one for LMS, zero for NLLR
- NLLR now obeys default score value: multiply with existing
scores when
base=1, add when base=0
===================================================================
2006/10/24 - roel_van_os: modules/pftijah/pftijah.mx,1.64
PF/Tijah: convert all terms to lowercase before looking them
up in the index.
At the moment, this is case folding done in pftijah.mx. This
is okay since
the tokenizer used at indexing time does cannot be
configured and it
converts terms to lowercase as well.
===================================================================
2006/10/24 - teubner: EXTENSIONS,1.2 compiler/core/core.c,1.47
compiler/core/coreopt.brg,1.35 compiler/core/fs.brg,1.43
compiler/core/simplify.brg,1.24
compiler/debug/abssynprint.c,1.26
compiler/debug/coreprint.c,1.27
compiler/include/abssyn.h,1.28
compiler/include/core.h,1.38
compiler/include/core_mnemonic.h,1.19
compiler/parser/parser.y,1.47
compiler/parser/scanner.l,1.40
compiler/semantics/normalize.brg,1.11
compiler/semantics/typecheck.brg,1.42
Parser support for the `execute at' syntax extension (XRPC).
Pathfinder's parser now recognizes expressions of the kind
"execute" "at" "{" Expr "}" "{" FunctionCall "}"
where the expression in the first pair of braces specifies an
URI where the function call given in the second pair should
be evaluated at. Note that, in order to avoid parser conflicts,
we did not directly use the syntax proposed in a recent paper
submission, but rather this one that adds the curly braces.
The system will try hard to convert the expression given in
the first pair of braces into a string.
An expression as shown above will lead to a Core tree situation
that uses the new node kind `xrpc':
xrpc
/ \
URI FunctionCall
It's now Jennie's task to support that in the back-end.
TODO: If *not* touched the code that is currently existing in
Pathfinder and uses the "old" `import rpc-module' syntax.
Jennie, will you rip out this old stuff, once you have
implemented
back-end support for the new syntax?
===================================================================
Jennie, will you rip out this old stuff, once you have
implemented
back-end support for the new syntax?
===================================================================
2006/10/24 - mr-meltdown: runtime/serialize_dflt.mx,1.17
Use % instead of to indicate meta-data headers
===================================================================
## Comment 6201
Date: 2006-11-04 15:03:04 +0100
From: @grobian
Logged In: YES
user_id=963970
Not Found
The requested URL
/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/runtime/serialization.out.00.html
was not found on this server.
## Comment 6202
Date: 2006-11-04 15:06:00 +0100
From: @drstmane
Logged In: YES
user_id=572415
URL will be available, again, once collection of last
night's testing results is completed.
I'll let you know.
Sorry for the inconvenience!
## Comment 6203
Date: 2006-11-04 15:28:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
For now the respective test output is also available at
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Fedora4/mTests10/runtime/.serialization.out.html
## Comment 6204
Date: 2006-11-05 16:48:26 +0100
From: @grobian
Logged In: YES
user_id=963970
I have no time to check this now, but I suspect that
changing the printf() to print() will fix this, as we use %
now, which is interpreted as a format character it seems.
Looks like a user-error anyway to use printf() there...
## Comment 6205
Date: 2006-11-12 12:29:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/runtime/serialization.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/runtime/serialization.out.00.html
## Comment 6206
Date: 2006-12-07 18:58:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Fixed in CVS:
To avoid that the "%" header-prefix of the "seq" serialization mode is mis-interpreted as format parameter,
we replace
xquery(...).printf();
resp.
printf(xquery(...));
by
printf("%s", xquery(...));
.
## Comment 6207
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590148 at http://sourceforge.net/support/tracker.php?aid=1590148
| XQ: runtime/Tests/serialization.milS: serializ. "seq" fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1105/comments | 0 | 2020-11-30T09:21:05Z | 2024-06-27T11:20:45Z | https://github.com/MonetDB/MonetDB/issues/1105 | 753,304,708 | 1,105 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-03 06:36:02 +0100
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-11-12 12:28:24 +0100
## Comment 6196
Date: 2006-11-03 18:36:02 +0100
From: @drstmane
all but the first test in
tests/W3C_use_cases/XQUF/Parts/Tests/
fail with
!WARNING: BATdescriptor: range error 88
!ERROR: logger could not use bat (88) for
1000000000_map_pid
!WARNING: BATdescriptor: range error 62
!ERROR: logger could not use bat (62) for
1000000000_rid_size
!WARNING: BATdescriptor: range error 91
!ERROR: logger could not use bat (91) for
1000000000_rid_level
!WARNING: BATdescriptor: range error 92
!ERROR: logger could not use bat (92) for
1000000000_rid_prop
!WARNING: BATdescriptor: range error 93
!ERROR: logger could not use bat (93) for
1000000000_rid_kind
!WARNING: BATdescriptor: range error 94
!ERROR: logger could not use bat (94) for
1000000000_rid_nid
!WARNING: BATdescriptor: range error 95
!ERROR: logger could not use bat (95) for
1000000000_nid_rid
!WARNING: BATdescriptor: range error 108
!ERROR: logger could not use bat (108) for
1000000000_attr_own
!WARNING: BATdescriptor: range error 109
!ERROR: logger could not use bat (109) for
1000000000_attr_qn
!WARNING: BATdescriptor: range error 110
!ERROR: logger could not use bat (110) for
1000000000_attr_prop
!WARNING: BATdescriptor: range error 107
!ERROR: logger could not use bat (107) for
1000000000_prop_val
!WARNING: BATdescriptor: range error 103
!ERROR: logger could not use bat (103) for
1000000000_prop_text
!WARNING: BATdescriptor: range error 104
!ERROR: logger could not use bat (104) for
1000000000_prop_com
!WARNING: BATdescriptor: range error 105
!ERROR: logger could not use bat (105) for
1000000000_prop_ins
!WARNING: BATdescriptor: range error 106
!ERROR: logger could not use bat (106) for
1000000000_prop_tgt
!WARNING: BATdescriptor: range error 102
!ERROR: logger could not use bat (102) for
1000000000_qn_loc
!WARNING: BATdescriptor: range error 101
!ERROR: logger could not use bat (101) for
1000000000_qn_uri
!WARNING: BATdescriptor: range error 100
!ERROR: logger could not use bat (100) for
1000000000_qn_prefix
!WARNING: BATdescriptor: range error 99
!ERROR: logger could not use bat (99) for
1000000000_qn_uri_loc
!WARNING: BATdescriptor: range error 98
!ERROR: logger could not use bat (98) for
1000000000_qn_prefix_uri_loc
!ERROR: logger could not read name (0)
cf. (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q6x.out.00.html
## Comment 6197
Date: 2006-11-12 12:28:24 +0100
From: @drstmane
Logged In: YES
user_id=572415
All these tests seem to work again --- at least in the
"Stable" release branch.
(Sorry, I have no idea who/which checkin made them work again.)
## Comment 6198
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1590066 at http://sourceforge.net/support/tracker.php?aid=1590066
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: "BATdescriptor: range error" in W3C_use_cases/XQUF/Parts | https://api.github.com/repos/MonetDB/MonetDB/issues/1104/comments | 0 | 2020-11-30T09:21:02Z | 2024-06-27T11:20:44Z | https://github.com/MonetDB/MonetDB/issues/1104 | 753,304,658 | 1,104 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-03 04:47:51 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-11-03 09:25:58 +0100
## Comment 6193
Date: 2006-11-03 16:47:51 +0100
From: @drstmane
tests Q6b, Q7, Q7x, Q8, Q9 in W3C_use_cases/XQUF/R/Tests/
fails with
Mserver:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/runtime/ll_staircasejoin.mx:525:
ll_child: Assertion `(size[pre] & (1<<31)) == 0' failed.
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_R/Q6b.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_R/Q7.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_R/Q7x.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_R/Q8.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_R/Q9.err.00.html
## Comment 6194
Date: 2006-11-03 21:25:58 +0100
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
When hopping from child to child (sibling to sibling),
the (loop-lifted) child step might hit a hole
--- e.g., after a sibling has been deleted or on a page
boundary ---
hence, holes must be treated properly (i.e., explicitely
skipped).
## Comment 6195
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1589990 at http://sourceforge.net/support/tracker.php?aid=1589990
| XQ: tests in W3C_use_cases/XQUF/R/ fail in ll-child-step | https://api.github.com/repos/MonetDB/MonetDB/issues/1103/comments | 0 | 2020-11-30T09:20:58Z | 2024-06-27T11:20:43Z | https://github.com/MonetDB/MonetDB/issues/1103 | 753,304,620 | 1,103 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-03 11:31:22 +0100
From: Maurice van Keulen <<mvankeulen>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-12-14 06:52:49 +0100
## Comment 6188
Date: 2006-11-03 11:31:22 +0100
From: Maurice van Keulen <<mvankeulen>>
Query below crashes server:
declare function depth($x as node()) as xs:integer
{
let $m := max(for $c in $x/child::node() return
depth($c))
return
if ($m) then 1+$m else 1
};
depth(<a><b/><b><c/></b></a>)
If you replace the "if ($m)" by "if (count($m) gt 0)"
then it runs fine.
## Comment 6189
Date: 2006-11-03 11:58:50 +0100
From: @drstmane
Logged In: YES
user_id=572415
added test in
pathfinder/tests/BugTracker/Tests/if-condition_testing_empty_sequence.SF-1589820.xq
Works fine for me!
## Comment 6190
Date: 2006-11-04 16:03:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
query also works fine in the testweb:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/if-condition_testing_empty_sequence.SF-1589820.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/if-condition_testing_empty_sequence.SF-1589820.err.00.html
Maurice,
could you please upgrade to the latest CVS version
(buildtools, MonetDB & pathfinder) and see whether the
problem still occurs with you?
## Comment 6191
Date: 2006-12-14 18:52:49 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
closing this
## Comment 6192
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1589820 at http://sourceforge.net/support/tracker.php?aid=1589820
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: if-condition testing empty sequence crashs server | https://api.github.com/repos/MonetDB/MonetDB/issues/1102/comments | 0 | 2020-11-30T09:20:56Z | 2024-06-28T13:31:57Z | https://github.com/MonetDB/MonetDB/issues/1102 | 753,304,581 | 1,102 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-03 07:22:41 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-11-03 10:06:26 +0100
## Comment 6184
Date: 2006-11-03 07:22:41 +0100
From: @drstmane
When compiling SQL with Intel's icc (with optimization
enabled) we get:
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5
-I../../..
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5
-I../../include
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5/../../include
-I../../common
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5/../../common
-I../../storage
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5/../../storage
-I../../server
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5/../../server
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5/atoms
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5/compiler
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5/kernel
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5/mal
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5/mil
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5/optimizer
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/monet5/.ntv.64.64.d-Fedora4/include/MonetDB5
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.11928/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-DLIBSQL -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
sql_user.c -KPIC -DPIC -o .libs/lib_sql_la-sql_user.o
/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5/sql_user.mx(74):
error 593: variable "schema_id" was set but never used
int schema_id, user_id;
^
/export/scratch0/monet/monet.ntv.64.64.d.11928/sql/src/backends/monet5/sql_user.mx(74):
error 593: variable "user_id" was set but never used
int schema_id, user_id;
^
compilation aborted for sql_user.c (code 2)
make[7]: *** [lib_sql_la-sql_user.lo] Error 1
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.ntv.64.64.d-Fedora4/make-k.out
## Comment 6185
Date: 2006-11-03 10:06:26 +0100
From: @njnes
Logged In: YES
user_id=43556
Fixed (compilation no test added)
## Comment 6186
Date: 2006-11-03 12:08:24 +0100
From: @romulogoncalves
Logged In: YES
user_id=1498628
Niels checked in the correction at 9:56 AM.
Regards,
Romulo
## Comment 6187
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1589733 at http://sourceforge.net/support/tracker.php?aid=1589733
| SQL fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1101/comments | 0 | 2020-11-30T09:20:53Z | 2024-06-27T11:20:41Z | https://github.com/MonetDB/MonetDB/issues/1101 | 753,304,540 | 1,101 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-02 11:44:54 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-11-03 10:09:22 +0100
## Comment 6179
Date: 2006-11-02 23:44:54 +0100
From: @grobian
(pegasus:~) fabian% run_monet_sql
!WARNING: GDKlockHome: created directory
/ufs/fabian/scratch/monetdb/five/program-x86_64/var/MonetDB5/dbfarm/demo/
!WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock.
!WARNING: BBPdir: initializing BBP.
MonetDB Server v4.99.19
Copyright (c) 1993-2006 CWI, all rights reserved
Compiled for x86_64-pc-linux-gnu/64bit with 64bit
OIDs dynamically linked
config:/ufs/fabian/scratch/monetdb/five/program-x86_64/etc/MonetDB5.conf
dbfarm:/ufs/fabian/scratch/monetdb/five/program-x86_64/var/MonetDB5/dbfarm
dbname:demo
Visit http://monetdb.cwi.nl/ for further information
>sql.start();
>create table suspect ( name varchar(100), picture_uri
varchar(200), notes varchar(500), victim_name
varchar(100), primary key (name));
!syntax error, unexpected IDENT in: "suspect"
>
what else does it expect after CREATE TABLE?
But it gets even weirder, forcing an IDENT makes SQL happy:
>create table "suspect" ( name varchar(100),
picture_uri varchar(200), notes varchar(500),
victim_name varchar(100), primary key (name));
&3
>
To make the confusement even bigger; consider the
following insert with idents instead of strings:
>insert into suspect (name, picture_uri, notes,
victim_name) values ("Dr. Thomas Neill Cream ",
"http://blabla/toolong", "did commit murders, but by
poisoning", "");
&2 1
?!?!? just accepted!
and it's really in there:
>select * from suspect
;
&1 0 1 4 1
% sys.suspect, sys.suspect, sys.suspect,
sys.suspect table_name
% name, picture_uri, notes, victim_name name
% varchar, varchar, varchar, varchar
type
% 23, 21, 36, 0 length
[ "Dr. Thomas Neill Cream ",
"http://blabla/toolong", "did commit murders,
but by poisoning", "" ]
>
And to conclude this night of confuxxlements:
>insert into suspect (name, picture_uri, notes,
victim_name) values ("Sander Borsboom", "lives
centuries later, so not much chance", "blah.jpg",
"noone (yet :D)");
!SELECT: identifier 'Sander Borsboom' unknown
>
(For the insert parts, the credits go to Sander who
(unfortunately) thinks that strings should be
double-quoted in SQL.)
## Comment 6180
Date: 2006-11-03 00:23:36 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Problem confirmed. It only appears upon start of server with
sql.start(). Possible problem is the recent change to reset the
input buffer to enable port to Windows.
## Comment 6181
Date: 2006-11-03 08:37:10 +0100
From: @grobian
Logged In: YES
user_id=963970
that seems unrelated to me. The students reported this on
the current (ADT2006 tag) sources
## Comment 6182
Date: 2006-11-03 10:09:22 +0100
From: @njnes
Logged In: YES
user_id=43556
Added test src/ADT2006/sander.sql
Fixed the m5/sql bug, was indeed caused by the stream changes.
We classified both single and double quoted strings as
STRING tokens and
only maded IDENTs out of the double quoted strings when they
were valid identifiers.
Now we never treat double quoted strings as STRINGS (only
identifiers) and give an error
if these aren't valid.
## Comment 6183
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1589593 at http://sourceforge.net/support/tracker.php?aid=1589593
| SQL: unexpected ident? | https://api.github.com/repos/MonetDB/MonetDB/issues/1100/comments | 0 | 2020-11-30T09:20:50Z | 2024-06-27T11:20:40Z | https://github.com/MonetDB/MonetDB/issues/1100 | 753,304,507 | 1,100 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-02 09:53:44 +0100
From: Loredana Afanasiev <<lafanasi>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-12-14 06:38:25 +0100
## Comment 6172
Date: 2006-11-02 21:53:44 +0100
From: Loredana Afanasiev <<lafanasi>>
Dear developers,
I am running an experiment of 3 XQuery queries on 9 XML
documents which I do not shredd upfront. The queries
run fine on the first 7 docs in increasing size.
Executing the queries on the 8th doc I get this error:
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = var a0024;
var a0023;
var a0022;
var a0021;
var a0020;
var a0019;
var a0018;
var a0017;
var a0016;
var a0015;
var a0014;
var a0013;
var a0012;
var a0011;
var a0010;
var a0009;
var a0008;
var a0007;
var a0006;
var a0005;
var a0004;
var a0003;
var a0002;
var a0001;
var a0000;
var unused;
var ws;
unused := nil;
Begin rule: "Query: serialize(FragList, Rel)"
a0000 := CATCH ({
ws := ws_create ();
Begin rule: "Rel: rec_fix(Rec, Rel)"
Begin rule (reduce1): "Rec:
rec_param(rec_arg(Rel, Rel), Rec)"
ERROR = Connection terminated
Timer 245.440 msec
Mserver is still running but trying to run any query
gives the same error.
XCheck's output html is at
http://ilps.science.uva.nl/~lafanasi/xcheck/until_child/output/outcome.html
there you can find the queries and XCheck's input
experiment file.
The tarball with all 9 docs are here:
http://ilps.science.uva.nl/~lafanasi/xcheck/mbench0.1.tgz
I hope you'll make sense of this.
Thanks,
Loredana
## Comment 6173
Date: 2006-11-03 00:42:51 +0100
From: @drstmane
Logged In: YES
user_id=572415
Loredana,
I'm pretty sure, you are (i.e., Mserver is) running out of
memory (see below why I guess so) --- to analyse the problem
in more detail, we'd need to see also the output of your
Mserver (your MapiClient output only tells us that your
Mserver seems to have crashed; your Mserver output should
tell you/us why...).
I re-run your experiments on my machine (Athon64 x2, 2 GHz,
2 GB RAM, Fedora Core 4, Linux 2.6.16, 64bit) with the
latest (i.e., tonight, Thursday Nov 2 2006) CVS version of
MonetDB/XQuery (compiled with 64bits, 64-bit OIDs
optimization disabled, debugging enabled, Pathfinder's
"milprint_summer" version as default) as follows:
Since your .tgz does not contain the .dtd that the .xml
documents refer to I had to remove the <!DOCTYPE ...> lines
from the .xml document to be able to process them in
MonetDB/XQuery.
Instead of (re-)installing XCheck, I simply mimic ti's
behaviour "by hand" as follows:
In one shell/terminal, I started the Mserver:
Mserver --dbinit='module(pathfinder); mapi_start();'
In a second shell/terminal, I ran the queries, just like I
supposed XCheck would do it:
for d in `ls -Sr /tmp/mbench0.1*.xml` ; do for q in
/tmp/Q?.xq ; do for i in 1 2 3 4 ; do echo $d $q $i ; cat $q
| sed 's|doc()|doc("'$d'")|g' | pf -A | MapiClient ; done ;
done ; done
Note, since my default compilation uses the
"milprint_summer" version of Pathfinder (i.e., without
support for the new transitive closure/recursion features, I
explicitely need to call `pf -A` to use the "algebra"
version which supports the "recurse" clause used in your
queries.
All queries run fine.
I noticed, though that the memory requirements grow with
both the growing document sizes and the queries.
For the first 7 documents (mbench0.1_totlevel8.xml, ...,
mbench0.1_totlevel14.xml), Mserver never grows beyond ~500
MB physical memory usage.
With mbench0.1_totlevel15.xml (22MB), Mserver grows up to 1
GB physical (1.5 GB virtual) memory usage with Q3.
With mbench0.1.xml (46MB), Mserver grows up to 1.5 GB
physical (2.5 GB virtual) memory usage with Q1 & Q2, and
even up to 2 GB physical (3 GB virtual) memory usage with Q3
--- still the queries runs almost CPU-bound in just "a
couple" of seconds (sorry did not really measure the times...).
From
http://ilps.science.uva.nl/~lafanasi/xcheck/until_child/output/outcome.html
I read that you're running on a (32-bit?) P4 machine with
"only" 500 MB of physical memory right? (how much swap
space, how much free space on the disc partition where your
dbfarm is located?)
Well then the queries exceed the physical memory already
with 8th document (mbench0.1_totlevel15.xml), and even reach
(if not exceed) the limits of the 32-bit address space with
the larges document.
Why does Mserver require so much memory for running your
(recusive = complex?) queries on documents of at most 46 MB
(67696 nodes)?
Well we need to check with Jan --- he generates the plans
for these queries ... ;-)
(finally) Good night.
## Comment 6174
Date: 2006-11-03 07:51:57 +0100
From: @drstmane
Logged In: YES
user_id=572415
Oops, sorry, I overlooked that you say that Mserver is still
running --- is there any output on the Mserver console?
## Comment 6175
Date: 2006-11-03 07:53:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
... and could you please check (with top) how big your
Mserver grows while running the queries?
## Comment 6176
Date: 2006-11-07 17:07:41 +0100
From: Loredana Afanasiev <<lafanasi>>
Logged In: YES
user_id=1636426
Hi Stefan,
Thanks for your beautifully detailed reply!!
I finally re-ran that experiment.
Last Friday Jan noticed an error message that made him think
that my problem was caused by a bug that was already fixed.
He installed MonetDB again from CVS (I suppose the latest
version) and now my experiment runs with no problems, though
it is very slow ( due to swapping ? )
As for the growing intermediate sizes, maybe it is better
that Jan looks into it? (Jan what do you say?)
groetjes,
l.
## Comment 6177
Date: 2006-12-14 18:38:25 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
This report was apparantly based on a previously repotred bug.
This bug was not identified.
I am going to suppose that this previous bug was well-documented, so I am closing this.
(in any case, MBench where this happened, is part of the test web)
## Comment 6178
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1589503 at http://sourceforge.net/support/tracker.php?aid=1589503
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ corrupt dbfarm | https://api.github.com/repos/MonetDB/MonetDB/issues/1099/comments | 0 | 2020-11-30T09:20:46Z | 2024-06-28T13:31:56Z | https://github.com/MonetDB/MonetDB/issues/1099 | 753,304,478 | 1,099 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-11-01 01:08:51 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-11-02 05:32:23 +0100
## Comment 6169
Date: 2006-11-01 13:08:51 +0100
From: @drstmane
After the recent configure changes, chosing an other
conpiler than gcc (via configuring with on of
--with-gcc=no / --without-gcc / --with-gcc=icc) fails,
i.e., the choice is ignored, and gcc is used.
It seems, as if the check for the compiler
(AC_PROG_CC()) now ends up in the configure script
before we set CC according to the --with-gcc choice ---
I could not yet find out why --- auto* magic ... |-((
## Comment 6170
Date: 2006-11-02 17:32:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
configure --with-gcc=<yes|no|compiler>
has been replaced by
configure CC=<compiler>
## Comment 6171
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1588555 at http://sourceforge.net/support/tracker.php?aid=1588555
| configure --with-gcc=no fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1098/comments | 0 | 2020-11-30T09:20:43Z | 2024-06-27T11:20:38Z | https://github.com/MonetDB/MonetDB/issues/1098 | 753,304,445 | 1,098 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-31 06:24:12 +0100
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2010-08-20 14:04:06 +0200
## Comment 6155
Date: 2006-10-31 18:24:12 +0100
From: @drstmane
With MonetDB/XQuery, the tests in
tests/W3C_use_cases/XQ/NS/Tests/
produce output that differs from the "expected results"
given in
http://www.w3.org/TR/2006/WD-xquery-use-cases-20060608/ns-queries-results
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q6.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q7.out.00.html
I'm not sure, whether this is indeed a bug, or rather a
"feature", i.e., an allowed variation of the output
within the XQuery/XML/namespace specifications.
Could an expert help, please?
## Comment 6156
Date: 2006-11-12 12:25:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q6.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q7.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q6.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q7.out.00.html
## Comment 6157
Date: 2007-02-19 15:51:15 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Assigning to Jens to decide the answer (or to assign to somebody else who has to decide).
The difference is that the expected output contains namespace declarations that are presumbaly in the input document byt which are not used in the output of the query. So the question is whether those namespace declarations are optional according to the XQuery standard.
## Comment 6158
Date: 2007-02-20 09:34:19 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
My interpretation of the W3C XQuery Serialization specification
is that our serialization is wrong here. So it is a bug.
Fixing this involves quite some changes to the code. Currently,
namespaces are completely handled during the (early) namespace
resolution (file ns.c). During namespace resolution, namespace
attributes are stripped from all element constructors and we lose
the direct correspondence between namespace bindings and element
constructors. To fix this corner case of our serializer, we'd
have to propagate more details about namespaces all the way
through our compiler pipeline. (Propagating namespace bindings
through the pipeline would also allow us to interpret computed
QNames in element constructors correctly.)
If I compare the effort required to fix this issue and the
significance of the problem, I would say this is a low-priority
bug.
## Comment 6159
Date: 2007-09-11 16:10:37 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: benjie-nguyen@users.sourceforge.net ----
Logged In: YES
user_id=1887942
Originator: NO
Greetings,
we have read up on the bug, we would like to stress that this bug is important to us : We use MonetDB as XML repository in the French ANR - RNTL "Web Content" project, which includes a large spectrum of industrial partners, such as Thales, EADS, and a number of SME.
Here is the context of our application :
We want to store documents in the database, and we have defined a UML model to represent these documents. This model is implemented by some partners (EADS) using JAVA classes and objects. These classes are serialized in XML using JAXB, and sent, via a web service that we have developped, (and can share if there is any interest), to the MonetDB server. This XML document is stored, and may be retrieved and sent to other clients, via a web service call. These clients will transform, using JAXB, the XML document into Java objects.
The problem :
In order to transform the XML document to java classes, JAXB needs a reference to the XSD representing our data model. The reference to this namespace is currently _lost_ when we store the document in MonetDB, therefore once we output the XML document over the web server, nothing can be made of it by the client that wishes to process it, once transformed into java objects.
We would rather not have to implement anything specific in order to manage these lost namespaces, so we would like to advocate for a revision of the importance of this bug, since JAXB is now standard with Java 6 and will probably be widely used to generate XML data to be store, and that we do not have much control on the XML that is generated by JAXB. We do however need to store it and retreive it "as-was".
Kind regards,
Benjamin NGUYEN
& Loïc SAINT-GHISLAIN
PRiSM Laboratory
University of Versailles
France
## Comment 6160
Date: 2007-09-11 18:40:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Jan, Teggy,
potentially being a "show-stopper" in below mentioned project (which has quite some "publicity potential" for MonetDB/XQuery and hence Pathfinder), I think it's reasonable to increase the priority of this bug, again. Despite Jens comment about the amount of work/effort that will be required to fix this bug, I'd like to raise the question, whether there is a reasonable way to get this one fixed in the foreseeable future --- surely not for the feature freeze later this week.
Obviously, the required expertise is in Munich. Maybe, there is a ways to combine forces (TUM+CWI, possibly also +University of Versailles) to get this bug solved say before the end of this year?
Thanks in advance!
Stefan
## Comment 6161
Date: 2007-09-11 19:15:15 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
Sorry I cannot be of much help on this any more.
A long while ago, I did some changes to the namespace resolution that
are somewhat preparatory for what is needed here. During namespace
resolution, an environment with statically-known namespaces is carried
around. The implementation thereby is ready such that the environment
could be annotated to every abstract syntax tree expression node
(environments are properly copied already, so you don't have to worry
about side effects to the environment during namespace resolution).
The large chunk of the work still remains to be done:
-- Annotate the statically known namespaces to AST nodes. (I think
this could be done trivially by annotating the current namespace
environment to every AST node.)
-- Propagate them to the Core tree. This needs a bit more work, and
the environment needs to be correctly propagated to the right Core
tree node. I remember this to be a bit tricky because there is no
1:1 relationship between Core and AST.
-- Finally propagate the information to the backend code generator.
(This also means that the environment needs to be represented as
a MonetDB data structure.) Once available on the MIL side, the
namespace environment can not only be used to properly implement
serialization, but also to implement casts to QNames correctly
(i.e., things like `element { "foo:bar" } { "Hello World!" }').
## Comment 6162
Date: 2007-09-12 11:22:00 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I think Jens refers to a different problem.
What is missing for the W3C tests to work fine is the preservation of Namespace declarations during shredding and serialization. (If I'm not 100% wrong) we are currently using the declarations only to assign the namespace URIs to all other nodes -- we however do not store Namespace declarations in the document encoding. (I think that's also what Benjamin wants: '... retreive it "as-was"'.)
Jens on the other side proposed to attach node constructors with all Namespaces visible in the XQuery query.
---- Sketch for a solution ----
To solve the 'reported' bug we would probably need to store an additional namespace declaration *tree* for each document. This tree would then maintain the relationship between all namespaces in a document and each node in the encoded document would refer to a node in the namespace tree. Using the node reference then allows to collect all visible namespaces by walking along the path from root to the referred namespace node. The price for this functionality is to build the additional namespace tree during shredding, maintaining two additional columns in the document encoding (ns_id|ns_cont) e.g., during updates or during node constructors in a query, and printing the namespace declarations during the serialization.
<a xmlns:v="v" xmlns:w="w">
<b xmlns:x="x">
<c xmlns:y="y" xmlns:w="another_w"/>
</b>
<d xmlns:z="z">
<e/>
</d>
</a>
Would result in the following document encoding:
pre|size|level|kind|name|cont|ns_id|ns_cont
0 5 -1 doc - 1 -1 1
1 3 0 elem a 1 11 1
2 1 1 elem b 1 12 1
3 0 2 elem c 1 14 1
4 1 1 elem d 1 15 1
5 0 2 elem e 1 15 1
and the following namespace tree (encoded with a pre|parent encoding)
pre|par|name|value
10 - v v
11 10 w w
12 11 x x
13 12 y y
14 13 w another_w
15 11 z z
Depending on the query the serialization now has to do different things:
1.) result is node 2 (name b):
During the serialization of node b namespace 12, 11, and 10 have to be printed -- the path from the referrenced namespace node (12) to root -- and during the serialization of node c namespace 14, 13 have to be printed -- the difference to the previously printed nodes.
2.) result is node 3 (name c):
During the serialization of node c namespace 14, 13, 12, and 10 have to be printed -- namespace node 11 has to be ignored as node 14 overwrites it.
3.) result is node 4 (name d):
During the serialization of node d namespace 15, 11, and 10 have to be printed and during serialization of node e no namespace attributes have to be generated.
All in all it looks like quite some work on the runtime part (and a small amount of work in the compiler -- fixing the node constructors). (Due to lack of time) I think I'm not the one implementing such a change (and thus un-assign myself from the bug). Are there any volunteers?
## Comment 6163
Date: 2007-09-12 17:58:32 +0200
From: @yzchang
Logged In: YES
user_id=341633
Originator: NO
Hi Jan,
Why no namespaces need to be generated for the serialization of node e? As node e has very much the same position as node c, I would expect that namespace nodes 15, 11 and 10 should be printed.
Jennie (who hasn't read the Serialization spec.)
## Comment 6164
Date: 2007-09-12 18:54:55 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
Just a little idea that I haven't thought through at all, but maybe you
find it helpful.
In XPath 1.0 there was a notion of `namespace nodes', which were part of
the XML document tree similar to other nodes. Namespace nodes were even
accessible via the special navigation axis `namespace::'. This concept
was abandoned in XPath 2.0/XQuery, but it may be an interesting approach
to store namespace information.
I could think of "namespace nodes" that are implemented analogously to
attributes (in fact, during serialization they even become attributes).
This might be easier to implement than some new "namespace tree".
Just my 2 US-¢
## Comment 6165
Date: 2007-09-13 10:15:14 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
@Jennie: I think you refer to the third examples (serializing node d). Node e needs no namespace declarations as these are already made available by node d (nodes inherit the namespaces by their ancestors as long as they do not overwrite them).
@Jens: The problem with your idea can be seen best if you look at the second example. If you store a namespace node for namespace 10 (name v) as child of node 1 (name a) and you only want to serialize node 3 (name c) then you would need to apply ancestor::*/namespace::* path steps for each result node to get the correct namespace definitions. This is getting even trickier if a node from a document (with namespace definitions in scope) has been part of a subtree copy due to node constructors (like in the above query Q2). Then namespace nodes at an ancestor are not reachable anymore (or node constructors would get way more complicated).
## Comment 6166
Date: 2009-11-11 18:46:46 +0100
From: @drstmane
===================================================================
2009/11/11 - stmane: All,1.1.1.1.32.1
Disabled tests that are bound to fail
as MonetDB/XQuery does (can) not support correct namespace serialization (yet?).
See also
ID: 1588053 "XQ: W3C_use_cases namespace tests fail: Bug or Feature?"
https://sourceforge.net/tracker/?func=detail&aid=1588053&group_id=56967&atid=482468
===================================================================
## Comment 6167
Date: 2009-11-12 10:47:50 +0100
From: @peterboncz
Ifear there is little chance that NS support will be beefed up anytime soom => Wont Fix
## Comment 6168
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1588053 at http://sourceforge.net/support/tracker.php?aid=1588053
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: W3C_use_cases namespace tests fail: Bug or Feature? | https://api.github.com/repos/MonetDB/MonetDB/issues/1097/comments | 0 | 2020-11-30T09:20:39Z | 2024-06-28T13:31:55Z | https://github.com/MonetDB/MonetDB/issues/1097 | 753,304,403 | 1,097 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-31 06:14:30 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-01-24 04:49:14 +0100
## Comment 6149
Date: 2006-10-31 18:14:30 +0100
From: @drstmane
In tests
tests/W3C_use_cases/XQ/R/Tests/Q13x.xq
tests/W3C_use_cases/XQ/R/Tests/Q18.xq
tests/W3C_use_cases/XQ/XMP/Tests/Q04.xq
"order by" produces result in wrong order; cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q13x.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q18.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_XMP/Q04.out.00.html
## Comment 6150
Date: 2006-11-12 12:24:26 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q13x.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q18.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_XMP/Q04.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q13x.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q18.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_XMP/Q04.out.00.html
## Comment 6151
Date: 2007-01-22 10:42:06 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
Using the algebra backend, the respective queries work fine, producing the correct output order:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q13alg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q13xalg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q18alg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_XMP/Q04alg.out.00.html
## Comment 6152
Date: 2007-01-24 16:49:14 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
fixed (probably)
## Comment 6153
Date: 2007-01-26 00:20:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
All credits go to Peter.
Thank you very much!
## Comment 6154
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1588043 at http://sourceforge.net/support/tracker.php?aid=1588043
| XQ: W3C_use_cases tests: "order by" produces wrong order | https://api.github.com/repos/MonetDB/MonetDB/issues/1096/comments | 0 | 2020-11-30T09:20:36Z | 2024-06-27T11:20:36Z | https://github.com/MonetDB/MonetDB/issues/1096 | 753,304,367 | 1,096 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-31 06:01:17 +0100
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-11-12 12:22:31 +0100
## Comment 6145
Date: 2006-10-31 18:01:17 +0100
From: @drstmane
Test tests/W3C_use_cases/XQ/R/Tests/Q03.xq produces
wrong result, cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q03.out.00.html
The test used to work fine with the CVS code base of
Oct 20 2006 --- don't know, which changes since then
cause the problem.
## Comment 6146
Date: 2006-10-31 18:06:21 +0100
From: @drstmane
Logged In: YES
user_id=572415
The same holds for tests
tests/W3C_use_cases/XQUF/Parts/Tests/Q1.milS
tests/W3C_use_cases/XQUF/Parts/Tests/Q2.milS
tests/W3C_use_cases/XQUF/Parts/Tests/Q3a1.milS
tests/W3C_use_cases/XQUF/Parts/Tests/Q3a2.milS
tests/W3C_use_cases/XQUF/Parts/Tests/Q6x.milS
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q3a1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q3a2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q6x.out.00.html
## Comment 6147
Date: 2006-11-12 12:22:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
All these tests seem to work again.
(Sorry, I have no idea who/which checkin made them work again.)
## Comment 6148
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1588034 at http://sourceforge.net/support/tracker.php?aid=1588034
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: W3C_use_cases tests: wrong result after recent checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/1095/comments | 0 | 2020-11-30T09:20:33Z | 2024-06-27T11:20:35Z | https://github.com/MonetDB/MonetDB/issues/1095 | 753,304,336 | 1,095 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-31 05:05:49 +0100
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-12-11 03:13:48 +0100
## Comment 6135
Date: 2006-10-31 17:05:49 +0100
From: @drstmane
tests tests/W3C_use_cases/XQ/R/Tests/Q02.xq
and tests/W3C_use_cases/XQ/R/Tests/Q06.xq
fail with
!ERROR: BATfetchjoin(tmp_463,tmp_376) does not hit
always (|bn|=5 != 8=|l|) => can't use fetchjoin.
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q06.err.00.html
## Comment 6136
Date: 2006-11-12 12:18:53 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q06.err.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q02.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q06.err.00.html
## Comment 6137
Date: 2006-12-11 09:19:11 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
The problem seems to be that in
iter_aggr := {max}(item_dbl_, iter_grp, reverse(loop001)).tmark(0@0);
(produced by milprint_summer.c's translateAggregates())
iter_grp's tail does not contain all group id's that occur in the extend's (reverse(loop001)) head,
and hence, {max} (IMHO correctly) produces NIL results for these groups.
A subsequent
item := dbl_values.addValues(iter_aggr).tmark(0@0);
inserts the NIL into dbl_values,
but --- since NILs don't match NILs --- does not find them back, resulting in an incomplete item,
which in turn leads to an incomplete right input to some subsequent fetchjoin().
Please see the attached .tar.gz file with annotated MIL code of the queries and their traces/results for details.
Unfortunately, I could not find out, why the iter_grp's tail does not contain all group id's that occur in the extend's (reverse(loop001)) head --- let alone why these queries trigger/require a fn:max() at all ...
Maybe some "milprint_summer.c expert" (JanR, Peter, Sjoerd, ...?) knows more ...
Jan,
could you please have a (quick?) look at it, comment and pass-on if necessary?
Thanks!
File Added: Q02-Q06.tgz
## Comment 6138
Date: 2006-12-11 09:21:43 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
ps:
attached scripts can be run via (e.g.):
Mtest_pathfinder tests/W3C_use_cases/XQ/R/Tests shred_docs
Mserver -d10 --set monet_prompt='' --dbname=mTests_tests_W3C_use_cases_XQ_R < /tmp/Q02.mil
Mserver -d10 --set monet_prompt='' --dbname=mTests_tests_W3C_use_cases_XQ_R < /tmp/Q06.mil
## Comment 6139
Date: 2006-12-11 10:02:10 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
I have no clue what the third argument of the grouped operator does -- reverse(loop001) however looks wrong as the aggregations should only return results for the groups that have at least one input tuple (empty sequence stays empty sequence -- see also http://www.w3.org/TR/2005/WD-xpath-functions-20050404/func-max).
I assume the integration of the loop relation in the MIL aggregate will create additional rows for the empty sequence, which is incorrect.
## Comment 6140
Date: 2006-12-11 10:23:37 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
if the third parameter only provides the result bat where the tail values are adjusted you could replace the following line in milprint_summer.c
"var iter_aggr := {%s}(item%s, iter_grp, reverse(loop%03u)).tmark(0@0);\n"
either by
"var iter_aggr := {%s}(item%s, iter_grp, reverse(loop%03u).mirror().semijoin(reverse(iter_grp))).tmark(0@0);\n"
or by
"var iter_aggr := {%s}(item%s, iter_grp, iter_grp.tunique()).tmark(0@0);\n"
A Monet expert (Stefan?) who knows what variant is more expensive may replace the current code by the cheaper alternative.
## Comment 6141
Date: 2006-12-11 10:25:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
{max}(b[oid::2,any::1], g[oid::2,oid::3], e[oid::3,any]) : r[oid::3,any::1]
is a grouped aggregation that receives
b[oid::2,any::1]: the BAT to be aggregated on tail
g[oid::2,oid::3]: a BAT that maps b's tuple oid::2 to the group oid::3
heads of b & g are aligned
e[oid::3,any]: the group extend, i.e., the unique head of e lists the IDs of all groups as identified by some previous group-by operation.
{max}() returns r[oid::3,any::1] with r's head aligned with that of b (i.e., |r| == |b|); group IDs of e's head that do not occur in g's tail receive a NIL result (max({}) = NIL).
I haven't traced yet where and how loop001 is generated nor whether the "incomplete" item is indeed correct (missing item == empty sequence ??) and "only" treated incorrectly later on ...
## Comment 6142
Date: 2006-12-11 13:10:42 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This is now fixed in CVS.
Can someone with a stable branch please patch the first example -- our serializer writes '<high_bid></high_bid>' into '<high_bid/>'.
## Comment 6143
Date: 2006-12-11 15:13:48 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
I also fixed the stable output.
Thanks for fixing the bug!
... Well, these two tests are fixed, but therefore, 5 other test now fail --- closing this bug report, opening new one(s) soon ...
## Comment 6144
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1587991 at http://sourceforge.net/support/tracker.php?aid=1587991
| XQ: tests W3C_use_cases/XQ/R/ Q0[26] fail in BATfetchjoin | https://api.github.com/repos/MonetDB/MonetDB/issues/1094/comments | 0 | 2020-11-30T09:20:29Z | 2024-06-27T11:20:34Z | https://github.com/MonetDB/MonetDB/issues/1094 | 753,304,304 | 1,094 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-30 11:20:38 +0100
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2006-11-12 12:16:59 +0100
## Comment 6130
Date: 2006-10-30 11:20:38 +0100
From: @drstmane
After checkins on Thursday Oct 26 2006, all XRpc tests
fail with
QUERY = import rpc-module namespace xrpc =
"http://www.monetdb.nl/xmark/"
at
"/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/pathfinder/benchmarks/XMark/XRpc/Tests/xmark.xq";
xrpc:q01("localhost", "auctionG.xml", "person0")
ERROR = !ERROR: CMDfind: value not found.
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XMark_XRpc/q01.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XRpc_basic_queries/add_dbl.err.00.html
## Comment 6131
Date: 2006-11-04 15:35:22 +0100
From: @drstmane
Logged In: YES
user_id=572415
The problem seems to occur since Friday Oct 27 2006, i.e.,
after checkins on Thursday Oct 26 2006:
===================================================================
2006/10/26 - boncz: compiler/mil/milprint_summer.c,1.287
compiler/semantics/xquery_fo.c,1.84
runtime/pathfinder.mx,1.256
runtime/pf_support.mx,1.164
fast NID node retriveal by NID
- moved support for id/idref node retrieval into pathfinder.mx
having this as an API function will allow us to provide
this functionality
using indices later (i.e. be able to lock and isolte a
hash index).
it also helps a port of this functionality to algebra.
for the moment, there are no shared hash tables, and
ID/IDREF queries
on updatable XML documents will be slowish (sequential
scans needed)
the new NID access is a good alternative to look up nodes.
- implemented in ID node retrieval support for string sthat
are numbers,
these are interpreted as NIDs, not ID attributes.
- implemented a new fn:nid(element()*) as xs:string* builtin
function
that returns the NIDs of element nodes.
- fixed some constant support things (mposjoin)
===================================================================
2006/10/26 - teubner: compiler/include/types.h,1.20
compiler/mil/milprint_summer.c,1.288
compiler/semantics/subtyping.c,1.41
compiler/semantics/typecheck.brg,1.43
compiler/semantics/types.c,1.21
compiler/semantics/xquery_fo.c,1.85
Implemented the `document management' type.
There is now a special primitive type in Pathfinder's type
system: `docmgmt'. This is the return type of all document
management functions (add-doc(), del-doc()). Type checking
will ensure that document management is not mixed with (a)
update statements (that update the content of some document,
but not the document collection itself) or (b) ordinary
XQuery results.
===================================================================
2006/10/26 - teubner: compiler/mil/milprint_summer.c,1.289
Tag deprecated uses of PFty_t.type using ifdef's.
See my email on the developers list on this topic.
===================================================================
## Comment 6132
Date: 2006-11-08 16:16:35 +0100
From: @yzchang
Logged In: YES
user_id=341633
Spent some time on this error. Thanks to Stefan's
adminstration! I found that the problems is caused by the
following change in xquery_prepare():
RCS file: /cvsroot/monetdb/pathfinder/runtime/pathfinder.mx,v
retrieving revision 1.271
diff -r1.271 pathfinder.mx
4155,4156c4155
< if ( (strncmp(p, "module", 6) == 0 &&
ISSPACE(p[6])) ||
< (strncmp(p, "rpc-module", 10) == 0 &&
ISSPACE(p[10])) ){
---
> if ( strncmp(p, "module", 6) == 0 &&
ISSPACE(p[6])) {
Due to this change, module imported by "rpc-module" is not
loaded; hence, proc_vid is empty; hence, CMDfind(proc_vid,
<function-sig>) will fail.
I don't think it is necessary to undo this change, since
"rpc-module" is removed in the new XRPC syntax. Once I
commit my changes concerning the new XRPC syntax, this error
will disappear.
Jennie
## Comment 6133
Date: 2006-11-12 12:16:59 +0100
From: @drstmane
Logged In: YES
user_id=572415
With Jennies new implementation of XRPC, all (revised) XRPC
tests work again.
## Comment 6134
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1587097 at http://sourceforge.net/support/tracker.php?aid=1587097
| XQ: XRpc tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1093/comments | 0 | 2020-11-30T09:20:26Z | 2024-06-27T11:20:33Z | https://github.com/MonetDB/MonetDB/issues/1093 | 753,304,261 | 1,093 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-30 11:12:28 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-11-01 12:10:52 +0100
## Comment 6127
Date: 2006-10-30 11:12:28 +0100
From: @drstmane
After checkins on Friday Oct 20 2006 and Saturday Oct
21 2006, the MBench tests fail on 64-bit systems with
64-bit OIDs with
MAPI = monetdb@localhost:36116
QUERY =
count(doc("/var/tmp/monet.GNU.64.64.d.23771/pathfinder/Fedora4/mTests/benchmarks/MBench/sf0.1.xml")[*])
ERROR = !ERROR: interpret: unknown variable 'name'.
!ERROR: interpret_params: del_doc(param 2):
evaluation error.
MAPI = monetdb@localhost:36116
QUERY =
count(doc("/var/tmp/monet.GNU.64.64.d.23771/pathfinder/Fedora4/mTests/benchmarks/MBench/sf0.1.xml")[*])
ERROR = !ERROR: ws_free: query cleanup failed, Mserver
must be restarted.
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_MBench/load_docs.err.00.html
## Comment 6128
Date: 2006-11-01 00:10:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS by fixing typo "name" -> "names" in
pathfinder.mx's del_doc_base()
## Comment 6129
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1587090 at http://sourceforge.net/support/tracker.php?aid=1587090
| XQ: MBench tests fail with 64-bit OIDs | https://api.github.com/repos/MonetDB/MonetDB/issues/1092/comments | 0 | 2020-11-30T09:20:23Z | 2024-06-27T11:20:32Z | https://github.com/MonetDB/MonetDB/issues/1092 | 753,304,225 | 1,092 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-30 11:04:45 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-12-01 01:45:36 +0100
## Comment 6121
Date: 2006-10-30 11:04:45 +0100
From: @drstmane
the changes in runtime/pathfinder.mx r1.257 -> r1.258
"fix id/idref bug introduced recently (thanks Jan)"
seem to fix XPath tests q11 & q15 and XPathMark test Q25,
but cause XPath tests q12, q13, q17 and XPathMark tests
Q26, Q27, Q28, Q29 to fail with
ERROR = !ERROR: BATfetchjoin(tmp_330,tmp_351) does not
hit always (|bn|=1 != 6=|l|) => can't use fetchjoin.
!ERROR: CTrefine: both BATs must have the same
cardinality and their heads must form a 1-1 match.
(or alike)
## Comment 6122
Date: 2006-10-31 12:37:56 +0100
From: @drstmane
Logged In: YES
user_id=572415
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPath/q12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPath/q17.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPath/q17.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q26.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q27.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q28.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q29.err.00.html
## Comment 6123
Date: 2006-11-03 20:54:44 +0100
From: @drstmane
Logged In: YES
user_id=572415
All XPath & XPathMark queries seem to work fine, again
EXCEPT XPathMark query Q27, which now returns an incomplete
result:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q27.out.00.html
## Comment 6124
Date: 2006-11-12 12:14:28 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q27.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q27.out.00.html
## Comment 6125
Date: 2006-12-01 01:45:36 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
fixed in gdk_relop.mx (CMDfetchbat / wrong BATslice upper bound)
## Comment 6126
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1587081 at http://sourceforge.net/support/tracker.php?aid=1587081
| XQ: XPath/XPathMark tests fail after recent id/idref changes | https://api.github.com/repos/MonetDB/MonetDB/issues/1091/comments | 0 | 2020-11-30T09:20:20Z | 2024-06-27T11:20:31Z | https://github.com/MonetDB/MonetDB/issues/1091 | 753,304,192 | 1,091 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-30 10:00:49 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-11-02 08:44:40 +0100
## Comment 6118
Date: 2006-10-30 10:00:49 +0100
From: @drstmane
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/src_modules_plain/ascii_io2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/src_modules_plain/ascii_io3.out.00.html
## Comment 6119
Date: 2006-11-02 20:44:40 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels.
Thanks!
## Comment 6120
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1587037 at http://sourceforge.net/support/tracker.php?aid=1587037
| ascii_io tests fail after recent code changes | https://api.github.com/repos/MonetDB/MonetDB/issues/1090/comments | 0 | 2020-11-30T09:20:16Z | 2024-06-27T11:20:30Z | https://github.com/MonetDB/MonetDB/issues/1090 | 753,304,148 | 1,090 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-29 08:37:04 +0100
From: @mlkersten
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-10-30 09:08:26 +0100
## Comment 6111
Date: 2006-10-29 20:37:04 +0100
From: @mlkersten
The latest changes to MAPI seem to have
lost the ability to show performance
trace data in SQL.
If you run mserver5/SQL and use
>trace select count(*) from tables;
onthe console then this produces a nice listing
however, if you use the same in MapiClient
then the trace information is not displayed
anymore.
(it is marked as comments by the server)
## Comment 6112
Date: 2006-10-29 20:46:11 +0100
From: @grobian
Logged In: YES
user_id=963970
can you clarify, or perhaps give an example?
## Comment 6113
Date: 2006-10-29 22:33:03 +0100
From: @mlkersten
Logged In: YES
user_id=490798
The example is in the initial statement.
Try
..>mclient -lsql
>trace select count(*) from tables;
and
..>mclient -lsql -t
>trace select count(*) from tables;
You will notice that since the last changes to the Mapi protocol
the essential information on performance data is ignored.
This is certainly not the intension.
Type the same query at the console and you see the intended
(an until a few days ago) the intended behavior.
[All tools rebuild from scratch to re-confirm this error]
## Comment 6114
Date: 2006-10-30 09:08:26 +0100
From: @grobian
Logged In: YES
user_id=963970
Small mistake in Mapi.mx. Please recompile M4. Fixed in CVS.
## Comment 6115
Date: 2006-10-30 09:31:00 +0100
From: @grobian
Logged In: YES
user_id=963970
Additionally, also fixed JDBC to cope with this output.
## Comment 6116
Date: 2006-10-31 08:33:51 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Thanks. The problem seems solved.
No test script has been added, because
the testweb would not notice the lack/availability
of the trace output. (it is marked )
## Comment 6117
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1586814 at http://sourceforge.net/support/tracker.php?aid=1586814
| MAPI: lost output | https://api.github.com/repos/MonetDB/MonetDB/issues/1089/comments | 0 | 2020-11-30T09:20:13Z | 2024-06-27T11:20:30Z | https://github.com/MonetDB/MonetDB/issues/1089 | 753,304,109 | 1,089 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-29 08:27:26 +0100
From: @yzchang
To: @njnes
Version: -- development
Last updated: 2006-10-29 08:32:25 +0100
## Comment 6106
Date: 2006-10-29 20:27:26 +0100
From: @yzchang
(I use the CVS HEAD version of MonetDB and pathfinder
and I have just built everything from scratch.)
If I use the '-s' option of MapiClient to specify an
output mode for my XQuery query, I get the following
error messages:
$ cat t.xq
(12, "abc")
$ mapiclnt -lx -s xml t.xq
MAPI = monetdb@localhost:50000
QUERY = xml
ERROR = !illegal reference to context node: at
(1,1-2,1): ``.'' is unbound
! halted in ../../../compiler/core/fs.brg
(reduce), line 2785
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>12 abc</XQueryResult>
$ mapiclnt -lx -s xml-typed t.xq
MAPI = monetdb@localhost:50000
QUERY = xml-typed
ERROR = !illegal reference to context node: at
(1,1-2,1): ``.'' is unbound
! halted in ../../../compiler/core/fs.brg
(reduce), line 2785
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>12 abc</XQueryResult>
Without the '-s' option, everything works fine:
$ mapiclnt -lx t.xq
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>12 abc</XQueryResult>
This seems that the value of option '-s' is treated
incorrectly as an XQuery query.
I think that this is not a pathfinder serilization
problem, because specifying an alternative output mode
in the PROC xquery works as expected:
MonetDB>xquery("xml", "(123, <a/>)").print();
[ "<?xml version=\"1.0\"
encoding=\"utf-8\"?>\n<XQueryResult>123<a/></XQueryResult>\n"
]
MonetDB>xquery("xml-typed", "(123, <a/>)").print();
[ "<?xml version=\"1.0\"
encoding=\"utf-8\"?>\n<result:sequence
xmlns:result=\"http://monetdb.cwi.nl/XQuery/results\"
xmlns:xs=\"http://www.w3.org/2001/XMLSchema\"
xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><result:atomic-value
xsi:type=\"xs:integer\">123</result:atomic-value><result:element><a/></result:element></result:sequence>\n"
]
Regards,
Jennie
## Comment 6107
Date: 2006-10-29 20:32:25 +0100
From: @njnes
Logged In: YES
user_id=43556
The -s switch of MapiClient has been misused by XQuery to
pass output formatting options. This is fixed,
ie now you need to use -o format or --output=format.
## Comment 6108
Date: 2006-10-29 20:39:30 +0100
From: @yzchang
Logged In: YES
user_id=341633
What kind of statement can be run with the '-s' option?
Shouldn't the bug be marked as invalid then?
## Comment 6109
Date: 2006-10-29 20:46:55 +0100
From: @njnes
Logged In: YES
user_id=43556
-s 'select 1;' in sql
or -s '1+1' should work in xquery
## Comment 6110
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1586808 at http://sourceforge.net/support/tracker.php?aid=1586808
| MAPI: error when using '-s' to specify XQuery output mode | https://api.github.com/repos/MonetDB/MonetDB/issues/1088/comments | 0 | 2020-11-30T09:20:10Z | 2024-06-28T13:31:55Z | https://github.com/MonetDB/MonetDB/issues/1088 | 753,304,061 | 1,088 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-29 06:32:08 +0100
From: Wouter Scherphof <<wscherphof>>
To: @sjoerdmullender
Version: -- development
Last updated: 2007-02-02 09:22:44 +0100
## Comment 6103
Date: 2006-10-29 06:32:08 +0100
From: Wouter Scherphof <<wscherphof>>
In the documentation (TechDocs/Core/mel), the
varsizeADTops listed are:
.HEAP
.PUT
.GET
.DEL
.LEN
I found that:
1) .LEN is now called .LENGTH.
2) .GET is obsoleted.
3) .READ and .WRITE are new and mandatory.
4) .CONVERT is new and optional.
Ad 2): How to get an atom from the heap then?
Ad 3): What are read and write for?
Ad 4): What is convert for?
And: anything else I should know?
Regards, Wouter.
## Comment 6104
Date: 2007-02-02 09:22:44 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Documentation has been added.
## Comment 6105
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1586545 at http://sourceforge.net/support/tracker.php?aid=1586545
| MEL: documentation of varsizeADTops outdated | https://api.github.com/repos/MonetDB/MonetDB/issues/1087/comments | 0 | 2020-11-30T09:20:06Z | 2024-06-27T11:20:27Z | https://github.com/MonetDB/MonetDB/issues/1087 | 753,304,011 | 1,087 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-29 01:36:20 +0200
From: @peterboncz
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-10-31 11:11:52 +0100
## Comment 6099
Date: 2006-10-29 01:36:20 +0200
From: @peterboncz
let $node := exactly-one(doc("JTR.xml")/*[1]/*[1])
return do insert <an/> as first into $node treat as
element()
This is from the UvA practicum. Am I doing something
wrong, or is the implementation of TREAT AS incomplete?
## Comment 6100
Date: 2006-10-29 10:13:46 +0100
From: @drstmane
Logged In: YES
user_id=572415
For those who wonder, here's the error that's triggered by
this query:
$ echo '
let $node := exactly-one(doc("JTR.xml")/*[1]/*[1])
return do insert <an/> as first into $node treat as element()
' | pf
type error: no variant of function upd:insertIntoAsFirst
accepts the given argument type(s): node; (node* | node)*
type error: maybe you meant:
type error: upd:insertIntoAsFirst ((element { item* } |
document { node })?, node*) as stmt
type error: illegal arguments for function upd:insertIntoAsFirst
halted in
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/typecheck.brg
(fun_not_found), line 1316
Apparently, once predicates are involved in XPath
expressions, Pathfinder's static typing cannot derive the
type of (in this case) $node as "element { item* }", but
only (more general) as "node".
## Comment 6101
Date: 2006-10-31 11:11:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
Problem has been fixed by JanR's recent typing fixes in CVS.
Thanks, Jan!
Test has been added in
pathfinder/tests/BugTracker/Tests/treat_as.SF-1586454.milS
## Comment 6102
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1586454 at http://sourceforge.net/support/tracker.php?aid=1586454
| XQ: treat as | https://api.github.com/repos/MonetDB/MonetDB/issues/1086/comments | 0 | 2020-11-30T09:20:01Z | 2024-06-27T11:20:27Z | https://github.com/MonetDB/MonetDB/issues/1086 | 753,303,960 | 1,086 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-27 10:08:49 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-10-28 12:27:32 +0200
## Comment 6096
Date: 2006-10-27 10:08:49 +0200
From: Jan Rittinger <<jan.rittinger>>
If pathfinder is out of memory PFoops tries to get more
memory allocated -- with a call of PFstrndup (line 135
in oops.c) -- to print the error.
## Comment 6097
Date: 2006-10-28 12:27:32 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
It is true that PFoops() calls PFmalloc(). If the latter called PFoops() in case we run out of memory, we would indeed have a problem here.
PFmalloc(), however, explicitly does *not* call PFoops(), avoiding just the problems that you mention in this bug report. So I don't think we
have a problem here.
## Comment 6098
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1585633 at http://sourceforge.net/support/tracker.php?aid=1585633
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: PFoops uses malloc | https://api.github.com/repos/MonetDB/MonetDB/issues/1085/comments | 0 | 2020-11-30T09:19:58Z | 2024-06-28T13:31:54Z | https://github.com/MonetDB/MonetDB/issues/1085 | 753,303,917 | 1,085 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-23 05:18:40 +0200
From: mihalych <<mihalych_>>
To: @njnes
Version: -- development
Last updated: 2006-10-29 08:33:05 +0100
## Comment 6093
Date: 2006-10-23 17:18:40 +0200
From: mihalych <<mihalych_>>
My table had a column declared as decimal(15,2).
I were trying to load data from a file using command
COPY INTO <table> FROM <file>
File had value for decimal field in integer format and
I got error:
ERROR = !ERROR: decimal wrong format (17)
After I changed 17 to 17.0 I could load data but value
in the column was 1.70
Example:
create table lineitem ( l_orderkey INTEGER NOT NULL,
l_partkey INTEGER NOT NULL, l_suppkey INTEGER
NOT NULL, l_linenumber INTEGER NOT NULL, l_quantity
DECIMAL(15,2) NOT NULL, l_extendedprice DECIMAL(15,2)
NOT NULL, l_discount DECIMAL(15,2) NOT NULL, l_tax
DECIMAL(15,2) NOT NULL, l_returnflag CHAR(1)
NOT NULL, l_linestatus CHAR(1) NOT NULL, l_shipdate
DATE NOT NULL, l_commitdate DATE NOT NULL,
l_receiptdate dATE NOT NULL, l_shipinstruct CHAR(25)
NOT NULL, l_shipmode CHAR(10) NOT NULL, l_comment
VARCHAR(44) NOT NULL);
copy into lineitem from '/tmp/lineitem_1.tbl' using
delimiters '|';
The data file is attached.
## Comment 6094
Date: 2006-10-23 21:14:09 +0200
From: @njnes
Logged In: YES
user_id=43556
We run the tpch sf-0.01 each night and never noticed the bug
because we use type INT for the l_quantity (which we think
thats better as you never buy half a product).
The the bug, indeed we didn't handle scales correctly. Only
the full 2 digits after the dot were handled
correctly.
I fixed this and added your example problem to the tests
(src/test/BugTracker/copy_decimal*)
## Comment 6095
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1582957 at http://sourceforge.net/support/tracker.php?aid=1582957
| SQL: COPY does not parse decimal numbers properly | https://api.github.com/repos/MonetDB/MonetDB/issues/1084/comments | 0 | 2020-11-30T09:19:55Z | 2024-06-27T11:20:25Z | https://github.com/MonetDB/MonetDB/issues/1084 | 753,303,885 | 1,084 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-21 01:16:52 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-11-03 11:40:46 +0100
## Comment 6086
Date: 2006-10-21 13:16:52 +0200
From: @grobian
http://bugs.gentoo.org/show_bug.cgi?id=152204
http://bugs.gentoo.org/show_bug.cgi?id=151557
Have fun.
## Comment 6087
Date: 2006-10-26 14:11:36 +0200
From: @grobian
Logged In: YES
user_id=963970
It appears gcc 4.2 (the pre-release snapshot I use on
pegatoo) fails to compile glibc properly (optimisation
related maybe). I compiled glibc-2.5 with gcc 4.1.1 and am
able to run Java now.
## Comment 6088
Date: 2006-10-26 14:12:26 +0200
From: @grobian
Logged In: YES
user_id=963970
oops, wrong bug...
## Comment 6089
Date: 2006-10-30 15:21:09 +0100
From: @grobian
Logged In: YES
user_id=963970
In case you feel like getting the same error on your Own
Workstation(tm), try:
1) set you path like this:
(pegasus:~) fabian% echo $path
/ufs/fabian/scratch/programs/gentoo/bin
/ufs/fabian/scratch/programs/gentoo/usr/bin /usr/bin /bin
1a) feel free to include my buildtools in your path as well:
/ufs/fabian/scratch/monetdb/current/program-x86_64/bin
2) configure monetdb
(pegasus:~) fabian% mkdir -p /var/tmp/monetdb-gentoo-compilation
(pegasus:~) fabian% cd /var/tmp/monetdb-gentoo-compilation
(pegasus:/var/tmp/monetdb-gentoo-compilation) fabian%
~fabian/scratch/monetdb/current/monetdb/configure
...
configure: "MonetDB requires libpthread (try --with-pthread)"
configure: error: "A required package is missing"
3) Ok, no message what it is looking for, or what test it
tries, so no clue on how to see why it doesn't find it. So
a few headaches later... ok the tests are done earlier. We
know what it complains about (unfortunately, MonetDB
configure insists on adding -m32, which is plainly
"annoying"), so we can continue, taking the safe route to
quickly eliminate some crap that might interfere as well:
(pegasus:/var/tmp/monetdb-gentoo-compilation) fabian% sed -i
-e 's|CFLAGS="\$CFLAGS \\\$(X_CFLAGS)"||'
~fabian/scratch/monetdb/current/monetdb/configure || echo
"Fixing $3/configure failed!"
(pegasus:/var/tmp/monetdb-gentoo-compilation)
~fabian/scratch/monetdb/current/monetdb/configure
--enable-bi1970-01-01 01:01:04 +0100
...
4) Yay! Let's compile!
(pegasus:/var/tmp/monetdb-gentoo-compilation) make
...
and voila!
gcc -m64 -DHAVE_CONFIG_H -I.
-I/ufs/fabian/scratch/monetdb/current/monetdb/src/mapi/clients/perl/Cimpl
-I../../../../..
-I/ufs/fabian/scratch/monetdb/current/monetdb/src/mapi/clients/perl/Cimpl
-I../../C
-I/ufs/fabian/scratch/monetdb/current/monetdb/src/mapi/clients/perl/Cimpl/../../C
-I../../../../common
-I/ufs/fabian/scratch/monetdb/current/monetdb/src/mapi/clients/perl/Cimpl/../../../../common
-I/ufs/fabian/scratch/programs/gentoo/usr/lib64/perl5/5.8.8/x86_64-linux/CORE
-g -O2 -std=c99 -Wall -W -c MapiLib.pm.c -fPIC -DPIC -o
.libs/MapiLib.pm.o
In file included from
/ufs/fabian/scratch/programs/gentoo/usr/lib64/perl5/5.8.8/x86_64-linux/CORE/perl.h:2759,
from MapiLib.pm.c:502:
/ufs/fabian/scratch/programs/gentoo/usr/lib64/perl5/5.8.8/x86_64-linux/CORE/scope.h:232:
error: expected specifier-qualifier-list before 'sigjmp_buf'
In file included from
/ufs/fabian/scratch/programs/gentoo/usr/lib64/perl5/5.8.8/x86_64-linux/CORE/perl.h:4485,
from MapiLib.pm.c:502:
/usr/include/sys/ipc.h:25:3: warning: warning "Files using
this header must be compiled with _SVID_SOURCE or _XOPEN_SOURCE"
MapiLib.pm.c: In function 'SWIG_Perl_ConvertPtr':
MapiLib.pm.c:709: warning: unused parameter 'flags'
MapiLib.pm.c: In function 'SWIG_Perl_ConvertPacked':
...
## Comment 6090
Date: 2006-11-03 10:10:28 +0100
From: @njnes
Logged In: YES
user_id=43556
Recent configure changes made it possible to compile
MonetDB, so can we close this issue...
## Comment 6091
Date: 2006-11-03 11:40:46 +0100
From: @grobian
Logged In: YES
user_id=963970
Actually, it is/was invalid, because modification of the
configure script removed more than was correct.
## Comment 6092
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1581779 at http://sourceforge.net/support/tracker.php?aid=1581779
| BUILD: MonetDB doesn't compile on Gentoo | https://api.github.com/repos/MonetDB/MonetDB/issues/1083/comments | 0 | 2020-11-30T09:19:52Z | 2024-06-28T13:31:53Z | https://github.com/MonetDB/MonetDB/issues/1083 | 753,303,837 | 1,083 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-19 04:27:48 +0200
From: bjbuter <<bjbuter>>
To: @njnes
Version: -- development
Last updated: 2006-10-20 01:19:10 +0200
## Comment 6083
Date: 2006-10-19 16:27:48 +0200
From: bjbuter <<bjbuter>>
OS: Fedora Core 1
Compiler: gcc-3.3.2
MonetDB V4.13.1, compiled from CVS
Crashes and generates a segmentation fault
When a table is in both the from as left join clause
Example SQL Query, id = primary key for both tables:
select *
from A, B
left join B on B.id = A.id;
## Comment 6084
Date: 2006-10-20 13:19:10 +0200
From: @njnes
Logged In: YES
user_id=43556
Added test in src/test/BugTracker/ambiguous_join
This bug revealed to problems one we allowed ambiguous names
in join expressions (both sides should have unique table
names). Also we allowed outer references within the join on
part, this is not allowed and resulted in a infinite
recursion. Both problems were fixed.
## Comment 6085
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1580565 at http://sourceforge.net/support/tracker.php?aid=1580565
| Segmentation fault when table in "from" and "left join" | https://api.github.com/repos/MonetDB/MonetDB/issues/1082/comments | 0 | 2020-11-30T09:19:49Z | 2024-06-27T11:20:22Z | https://github.com/MonetDB/MonetDB/issues/1082 | 753,303,809 | 1,082 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-19 08:56:22 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-10-26 02:12:47 +0200
## Comment 6078
Date: 2006-10-19 08:56:22 +0200
From: @drstmane
Most probably since Friday, Oct 06 2006, the following
ant on our Gentoo machine (pegatoo) fails to compile
JDBC, complaining about wrong usage of java-config and
triggering an assertion (see below and/or
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.GNU.32.32.d-Gentoo1.12.5/make-k.out
).
A similar assertion also occurs with various tests:
"lt-Mserver: pthread_mutex_lock.c:80:
__pthread_mutex_lock: Assertion `mutex->__data.__owner
== 0' failed."
(see the testweb for MonetDB, SQL & Pathfinder).
========
make[7]: Entering directory
`/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc/tests'
"/usr/bin/ant" -f "`echo
/var/tmp/monet.GNU.32.32.d.23178/sql/src/jdbc/tests/build.xml`"
-Dbuilddir="`echo
/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc/tests`"
-Djardir="`echo
/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc/tests`"
compile
usage: java-config [options]
Java Configuration Utility Version 2.0.30
Copyright 2004-2005 Gentoo Foundation
Distributed under the terms of the GNU General Public
License v2
Please contact the Gentoo Java Herd <java@gentoo.org>
with problems.
java-config-2: error: --classpath option requires an
argument
java: ../nptl/pthread_mutex_lock.c:80:
__pthread_mutex_cond_lock: Assertion
`mutex->__data.__owner == 0' failed.
make[7]: *** [compile_ant_target] Aborted
make[7]: Target `all-am' not remade because of errors.
make[7]: Leaving directory
`/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc/tests'
make[6]: *** [all] Error 2
make[6]: Leaving directory
`/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc/tests'
make[6]: Entering directory
`/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc'
"/usr/bin/ant" -f "`echo
/var/tmp/monet.GNU.32.32.d.23178/sql/src/jdbc/build.xml`"
-Dbuilddir="`echo
/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc`"
-Djardir="`echo
/var/tmp/monet.GNU.32.32.d.23178/sql/Gentoo1.12.5/src/jdbc`"
jar_jdbcclient
usage: java-config [options]
Java Configuration Utility Version 2.0.30
Copyright 2004-2005 Gentoo Foundation
Distributed under the terms of the GNU General Public
License v2
Please contact the Gentoo Java Herd <java@gentoo.org>
with problems.
java-config-2: error: --classpath option requires an
argument
java: ../nptl/pthread_mutex_lock.c:80:
__pthread_mutex_cond_lock: Assertion
`mutex->__data.__owner == 0' failed.
make[6]: *** [jar_jdbcclient_ant_target] Aborted
========
## Comment 6079
Date: 2006-10-19 08:59:04 +0200
From: @grobian
Logged In: YES
user_id=963970
this bug is unrelated to Java, the kernel seems to misbehave
since the reboot that Mathijs gave pegatoo because it
appeared to be stuck (when looking at the display)
## Comment 6080
Date: 2006-10-19 10:27:31 +0200
From: @grobian
Logged In: YES
user_id=963970
It's glibc of course, not the kernel.
## Comment 6081
Date: 2006-10-26 14:12:47 +0200
From: @grobian
Logged In: YES
user_id=963970
It appears gcc 4.2 (the pre-release snapshot I use on
pegatoo) fails to compile glibc properly (optimisation
related maybe). I compiled glibc-2.5 with gcc 4.1.1 and am
able to run Java now.
## Comment 6082
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1580270 at http://sourceforge.net/support/tracker.php?aid=1580270
| Pegatoo's glibc causes trouble | https://api.github.com/repos/MonetDB/MonetDB/issues/1081/comments | 0 | 2020-11-30T09:19:46Z | 2024-06-27T11:20:22Z | https://github.com/MonetDB/MonetDB/issues/1081 | 753,303,764 | 1,081 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-18 11:33:57 +0200
From: @peterboncz
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-12-11 11:16:29 +0100
## Comment 6070
Date: 2006-10-18 11:33:57 +0200
From: @peterboncz
t.xq:
declare function
recursiveActor($destinations as xs:string*,
$actor as xs:string) as node()
{
let $db := <film><filmName>x</filmName><actorName>Sean
Connery</actorName></film>
let $val := $db//filmName[../actorName=$actor]
let $cnt := count($destinations)
let $pos := ($cnt / 2) cast as xs:integer
let $dsts1 := subsequence($destinations, 1, $pos)
let $dsts2 := subsequence($destinations, $pos+1)
return
(if ($cnt > 1)
then recursiveActor($dsts1, $actor)
else (),
$val,
if ($cnt > 2)
then recursiveActor($dsts2, $actor)
else ())
};
recursiveActor(("http://a.org",
"http://b.org",
"http://c.org",
"http://d.org",
"http://e.org"), "Sean Connery")
-bash-3.00$ pf t.xq
type error: binding sequence in a for clause has static
type `empty'
halted in
/data/home/boncz/pathfinder/compiler/semantics/typecheck.brg
(reduce), line 466
## Comment 6071
Date: 2006-10-18 11:37:15 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Sorry, the return type of the recursive funtion should be
node()*:
declare function
recursiveActor($destinations as xs:string*,
$actor as xs:string) as node()*
## Comment 6072
Date: 2006-11-04 17:30:09 +0100
From: @drstmane
Logged In: YES
user_id=572415
added test in
pathfinder/tests/BugTracker/Tests/recursion_type_error.SF-1579524.*
correct/expected output still pending
## Comment 6073
Date: 2006-12-07 13:06:04 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
As long as the query writer does not know the difference between the path step "/" and the divison "div" a type error is the perfect result.
## Comment 6074
Date: 2006-12-07 13:07:10 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
It also took me a while to see it :( (return bug to sender :))
## Comment 6075
Date: 2006-12-11 23:16:29 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: YES
ehh..
yes.
sorry.
## Comment 6076
Date: 2006-12-12 00:22:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
I was really tempted to re-open this one, because the respective test (see below) still fails, which IMHO does *forbid* closing a bug report without checking and fixing the respective test --- even is the bug report is considered "incalid"!
But then I considered making this my last "good deed" for today, this month, this year, ... ever?
Fixed the test script (which JanR had actually already done on Thr Dec 7 2006 in the development trunk) and approved stable output (which has not yet been done in the development trunk, either) as follows:
<XQueryResult><filmName>x</filmName><filmName>x</filmName><filmName>x</filmName><filmName>x</filmName><filmName>x</filmName><filmName>x</filmName><filmName>x</filmName></XQueryResult>
Could someone *please* validate the correctness of this result?
Thank you very much!
## Comment 6077
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1579524 at http://sourceforge.net/support/tracker.php?aid=1579524
| XQ: type error in recursion | https://api.github.com/repos/MonetDB/MonetDB/issues/1080/comments | 0 | 2020-11-30T09:19:42Z | 2024-06-28T13:31:52Z | https://github.com/MonetDB/MonetDB/issues/1080 | 753,303,726 | 1,080 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-18 11:08:47 +0200
From: @peterboncz
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2007-05-25 02:27:58 +0200
## Comment 6061
Date: 2006-10-18 11:08:47 +0200
From: @peterboncz
I am not really sure whether this is a legal xquery:
(1,2)/.
(Galax does not like it either. Both Pf and galax
accept it with elements: (<a/>,<b/>)/. )
but the PF error message is a bit confusing:
-bash-3.00$ pf t.xq
type error: illegal combination of query and update
features
halted in
/data/home/boncz/pathfinder/compiler/semantics/typecheck.brg
(reduce), line 417
## Comment 6062
Date: 2006-10-18 11:24:15 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Hi Peter,
your input is illegal because the `/' operator only allows
node sequence on its left-hand side (and not a sequence of
integers).
The error message is indeed confusing. I will look into
this.
## Comment 6063
Date: 2006-11-04 17:29:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
test added in
pathfinder/tests/BugTracker/Tests/update_error.SF-1579510.*
correct/expected error message still pending
## Comment 6064
Date: 2007-02-19 15:51:53 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Any news on this?
## Comment 6065
Date: 2007-02-20 15:26:47 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
Fixed in CVS.
## Comment 6066
Date: 2007-03-24 11:18:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opened, as the respective test still fails:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/update_error.SF-1579510.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/update_error.SF-1579510.err.00.html
If the new error message
ERROR = !warning: query will always return an error
!ERROR: err:XP0019: Argument to location step must be a node sequence.
is the "desired" one or at least "acceptable", please update the stable output accordingly before closing the bug report.
## Comment 6067
Date: 2007-04-21 19:28:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Jens,
Any news on this one?
Thanks!
Stefan
## Comment 6068
Date: 2007-05-25 02:27:58 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: YES
approved the new error message; thanks Jens!
## Comment 6069
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1579510 at http://sourceforge.net/support/tracker.php?aid=1579510
| XQ: update error for "(1,2)/." | https://api.github.com/repos/MonetDB/MonetDB/issues/1079/comments | 0 | 2020-11-30T09:19:39Z | 2024-06-27T11:20:20Z | https://github.com/MonetDB/MonetDB/issues/1079 | 753,303,699 | 1,079 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-17 01:08:21 +0200
From: @romulogoncalves
To: @sjoerdmullender
Version: -- development
Last updated: 2006-10-17 01:28:52 +0200
## Comment 6058
Date: 2006-10-17 13:08:21 +0200
From: @romulogoncalves
I update build tools, execute bootstrapp, configure,
make , make install
Then I check out MonetDB4 v4.13.1 from cvs
bootstraap, configure, make and I got this error:
/ufs/goncalve/MonetDB/MonetDB4/MonetDB/src/mapi/mapi.mx:
In function 'mil_client_engine':
/ufs/goncalve/MonetDB/MonetDB4/MonetDB/src/mapi/mapi.mx:304:
error: too many arguments to function 'parseClient'
make[6]: *** [lib_mapi_la-mapi.lo] Error 1
make[6]: Leaving directory
`/net/amelia/export/scratch1/goncalve/MonetDB/monetdb4/build/src/mapi'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/net/amelia/export/scratch1/goncalve/MonetDB/monetdb4/build/src/mapi'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/net/amelia/export/scratch1/goncalve/MonetDB/monetdb4/build/src/mapi'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/net/amelia/export/scratch1/goncalve/MonetDB/monetdb4/build/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/net/amelia/export/scratch1/goncalve/MonetDB/monetdb4/build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/net/amelia/export/scratch1/goncalve/MonetDB/monetdb4/build'
make: *** [all] Error 2
Best regards,
Romulo Goncalves
## Comment 6059
Date: 2006-10-17 13:28:52 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
I had checked in some code in MonetDB/src/mapi/mapi.mx that
was not supposed to be checked in.
## Comment 6060
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1578845 at http://sourceforge.net/support/tracker.php?aid=1578845
| MonetDB4 compilation error; | https://api.github.com/repos/MonetDB/MonetDB/issues/1078/comments | 0 | 2020-11-30T09:19:36Z | 2024-06-27T11:20:19Z | https://github.com/MonetDB/MonetDB/issues/1078 | 753,303,660 | 1,078 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-17 01:00:19 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-10-19 02:43:44 +0200
## Comment 6054
Date: 2006-10-17 13:00:19 +0200
From: @grobian
- This works fine:
INSERT INTO "examines" ("docID", "vicID") VALUES
(
(
SELECT "docID"
FROM "doctors"
WHERE "name" LIKE 'Dr. Llewellyn%'
),
(
SELECT "vicID"
FROM "victims"
WHERE "name" LIKE 'Mary Ann Walker%'
)
);
monetdb-> 1 affected row
INSERT INTO "timelines" ("vicID", "time", "event") VALUES
(
(
SELECT "vicID"
FROM "victims"
WHERE "name" LIKE 'Mary Ann Walker%'
),
'11:00 PM',
'Polly is seen walking etc...'
);
Error: ERROR: interpret: no matching MIL operator to
'CTgroup(grp, str)'.
MAYBE YOU MEAN:
CTgroup(BAT[oid,any], BAT[oid,any]) : grp
CTgroup(grp, BAT[oid,any]) : grp
CTgroup(BAT[oid,any]) : grp
CTgroup(oid, BAT[oid,any]) : BAT[oid,oid]
CTgroup(BAT[oid,oid], any::1) : BAT[oid,oid]
CTgroup(any::1) : any::1
Thanks in advance, Tijn.
I think timelines has three varchar columns.
## Comment 6055
Date: 2006-10-17 13:36:17 +0200
From: @grobian
Logged In: YES
user_id=963970
follow up:
I actually tried those workarounds, but:
INSERT INTO "timelines" ("vicID", "time", "event") VALUES
(
(
SELECT "vicID", '11:00 PM', 'Polly is a sweet bird....'
FROM "victims"
WHERE "name" LIKE 'Mary Ann Walker%'
)
);
Error: INSERT INTO: number of values doesn't match number of
columns of
table 'timelines'
INSERT INTO "timelines" ("vicID", "time", "event") VALUES
(
(
SELECT "vicID"
FROM "victims"
WHERE "name" LIKE 'Mary Ann Walker%'
),
(
SELECT '11:00 PM'
),
(
SELECT 'Nice Polly...'
)
);
Error: ERROR: interpret: no matching MIL operator to
'CTgroup(grp, str)'.
MAYBE YOU MEAN:
CTgroup(BAT[oid,any], BAT[oid,any]) : grp
CTgroup(grp, BAT[oid,any]) : grp
CTgroup(BAT[oid,any]) : grp
CTgroup(oid, BAT[oid,any]) : BAT[oid,oid]
CTgroup(BAT[oid,oid], any::1) : BAT[oid,oid]
CTgroup(any::1) : any::1
Of course inserting a set using VALUES is wrong (parser
should/could complain on this?), but at least the error
messages are a bit misleading.
## Comment 6056
Date: 2006-10-19 14:43:44 +0200
From: @njnes
Logged In: YES
user_id=43556
Test added to src/test/BugTracker/insert_values
The parsing of subqueries is improved and handling of
single value returns is handled through the resently
introduced zero_or_one function, which makes sure an
error is produced when more the one value is returned by the
subquery.
## Comment 6057
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1578838 at http://sourceforge.net/support/tracker.php?aid=1578838
| SQL: no matching MIL operator to 'CTgroup(grp, str)' on INSE | https://api.github.com/repos/MonetDB/MonetDB/issues/1077/comments | 0 | 2020-11-30T09:19:33Z | 2024-06-27T11:20:18Z | https://github.com/MonetDB/MonetDB/issues/1077 | 753,303,624 | 1,077 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-17 10:26:03 +0200
From: @sjoerdmullender
To: Romulo Goncalves <<goncalve>>
Version: -- development
Last updated: 2006-10-18 03:12:30 +0200
## Comment 6046
Date: 2006-10-17 10:26:03 +0200
From: @sjoerdmullender
When I start Mserver with the SQL server, I often get a
crash. The crash happens in find_sql_column_node
because the first parameter is NULL. I traced it back
to dependency_schem_user that calls find_sql_column
with a NULL value for the "users" parameter.
## Comment 6047
Date: 2006-10-17 10:39:22 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
It was a mistake with the table name. Yesterday when I run
Mtest on of the files was open with new changes. Mtest did
not give any problems, so I close the file saving the
changes (the idea was to close it without saving the
changes) and I check in that changes which were not tested
by Mtest. I already check in the fix.
Sorry, for the inconvenient.
Best Regards,
Romulo Goncalves
## Comment 6048
Date: 2006-10-17 10:53:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Since it was a bug that has now been fixed, I'd call it
"Fixed", not "Invalid".
## Comment 6049
Date: 2006-10-17 11:26:10 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Well, it is not complete fixed. The Mserver 4 it also have
problems. I am moving one of the function to the backends
because M4 and M5 have different name for the users table.
M4 is db_users and in M5 is db_user_info.
I am fixing the problem. In few minutes I will check in the fix.
Best Regards,
Romulo Goncalves
## Comment 6050
Date: 2006-10-17 11:27:21 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Reopening since the bug has not, in fact, been fixed.
I start with an empty database (rm -rf .../var/MonetDB) and
start the server as follows:
Mserver --dbinit 'module(mapi); module(sql_server);
mapi_register(sql_frontend()); mapi_start();'
This causes the above mentioned crash. And the crash
happens because the "users" varible is NULL in
dependency_schem_user.
## Comment 6051
Date: 2006-10-17 12:48:12 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
The last check in is to fix the problem when you start
mserver4. It crased when the system tryed to find the table
db_user_info.
Beste regards,
Romulo Goncalves
## Comment 6052
Date: 2006-10-18 15:12:30 +0200
From: @njnes
Logged In: YES
user_id=43556
bug was fixed. Test not needed as simple start up of m4/sql
allready triggered the bug.
## Comment 6053
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1578741 at http://sourceforge.net/support/tracker.php?aid=1578741
| crash when starting Mserver with SQL | https://api.github.com/repos/MonetDB/MonetDB/issues/1076/comments | 0 | 2020-11-30T09:19:29Z | 2024-06-27T11:20:17Z | https://github.com/MonetDB/MonetDB/issues/1076 | 753,303,574 | 1,076 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-15 03:38:59 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-12-09 03:22:23 +0100
## Comment 6042
Date: 2006-10-15 15:38:59 +0200
From: @drstmane
Query qa06 of MBench fails with:
ERROR = !ERROR: merged_union: BAT 6 (1 BUNs) must have
the same size as BAT 2 (256 BUNs).
!ERROR: CMDmerged_union: operation failed.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_MBench/qa06.err.00.html
## Comment 6043
Date: 2006-11-12 12:13:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_MBench/qa06.err.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/benchmarks_MBench/qa06.err.00.html
## Comment 6044
Date: 2006-12-09 15:22:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
fixed in CVS:
Since the introduction of [void,void] BATs and function receiving an [oid,oid] BAT must eb able to deal not only with [VoID,oid] and [oid,VoID] BATs, but also with [VoID,VoID] BATs.
Hence, in MonetDB/src/modules/plain/aggrX3.mx, we have to replace BUNtloc(g, ...) by BUNtail(g, ...), since the [oid,oid] group-map BAT g may now also be [VoID,VoID].
ToDo:
Extend code-expansion in MonetDB/src/modules/plain/aggrX3.mx, to get the (expensive) BUNtail(g, ...) out of inner loops.
In fact, g:[VoID,VoID] could be treated quite efficiently...
## Comment 6045
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1577629 at http://sourceforge.net/support/tracker.php?aid=1577629
| XQ: MBench query qa06: merged_union fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1075/comments | 0 | 2020-11-30T09:19:26Z | 2024-06-27T11:20:16Z | https://github.com/MonetDB/MonetDB/issues/1075 | 753,303,527 | 1,075 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-13 11:25:09 +0200
From: Wouter Scherphof <<wscherphof>>
To: @sjoerdmullender
Version: -- development
Last updated: 2006-10-15 10:53:35 +0200
## Comment 6033
Date: 2006-10-13 23:25:09 +0200
From: Wouter Scherphof <<wscherphof>>
After building the template (example module) on
Windows (the "native tools"), the hello() function
shows improper behaviour:
C:\monetdb\template\NT>runmserver
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further
information.
MonetDB>print(hello("world"));
[ 2.6374965078940011e-308 ]
MonetDB>var w := hello("world");
MonetDB>print(w);
[ 1.QNAN ]
MonetDB>
Regards, Wouter Scherphof.
## Comment 6034
Date: 2006-10-14 14:06:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
added test in template/src/Tests/hello.milS
works fine on Linux
## Comment 6035
Date: 2006-10-15 11:12:06 +0200
From: Wouter Scherphof <<wscherphof>>
Logged In: YES
user_id=93938
I ran the new test; here's my hello.test.out:
"
stdout of test 'hello` in directory 'src` itself:
11:00:42 >
11:00:42 > Mserver "--
config=C:\monetdb\MonetDB\NT\conf\MonetDB.conf" --
debug=10 --
set "monet_mod_path=C:\monetdb\template\NT\src\.libs;C:\mon
etdb\MonetDB\NT\src\modules\plain\.libs;C:\monetdb\MonetDB\
NT\src\modules\plain;C:\monetdb\MonetDB\NT\src\modules\cont
rib\.libs;C:\monetdb\MonetDB\NT\src\modules\contrib;C:\mone
tdb\MonetDB\NT\src\modules\calibrator\.libs;C:\monetdb\Mone
tDB\NT\src\modules\calibrator;C:\monetdb\MonetDB\NT\src\mod
ules\mnetcdf\.libs;C:\monetdb\MonetDB\NT\src\modules\mnetcd
f;C:\monetdb\MonetDB\NT\src\mapi\.libs;C:\monetdb\MonetDB\N
T\src\mapi" --
set "gdk_dbfarm=C:\monetdb\MonetDB\NT\dbfarm" --
set "sql_logdir=C:\monetdb\MonetDB\NT\log" --set
mapi_port=32127 --set monet_prompt= --trace --
dbname=mTests_src < hello.milS
11:00:42 >
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
module(example);
print(hello("world"));
[ 2.6374965080726553e-308 ]
var x:=hello("workd");
print(type(x));
[ 11 ]
print(x);
[ 1.QNAN ]
quit();
11:00:42 >
11:00:42 > Done.
11:00:42 >
"
## Comment 6036
Date: 2006-10-15 12:01:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Wouter,
Sjoerd (hopefully) fixed the bug after I added the test.
Hence, did you cvs-update and recompile your "template"
before running the test?
If not, please do so.
If yes, or if the test still failes after the update, which
version of MonetDB are you using?
## Comment 6037
Date: 2006-10-15 12:28:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
Wouter,
I just see that your test output indicates that you're using
MonetDB 4.13.1;
however the fact that the type of the result of function
hello() is 11 (dbl) and not str (13) makes me wonder --- str
used to be 11 before two new data types (bte & wrd) were
introduced recently. I'm afraid, something seem to be
messed-up with your MonetDB installation.
Hence, a couple of questions:
Are you using source tarballs from our daily builds or are
you using cvs sources?
In case of tarballs, when did you download them?
In case of cvs sources, when did you first cvs checkout (and
build) your current source trees of buildtools, MonetDB &
template, and when did you last cvs update (and rebuild)
buildtools, MonetDB & template?
Note, they all need to be in sync; i.e., in case there are
any problems after updating template, also update and
rebuild buildtools & MonetDB (in that order), and then
rebuild template.
Also make sure, that there are no legacy remains of
previous/older versions on your systems (at least appearing
in your environment variables).
In particular, if your original installation of buildtools
and/or MonetDB was befoe Oct 05 2006 than, please remove the
whole <prefix>\lib (or even the whole <prefix> in case you
don't have any valuable data in <prefix>\var) before
rebuilding them. The directory structure in <prefix>\lib has
changed, and hence, old left-over libraries/DLLs might be
found and used instead of the new ones.
## Comment 6038
Date: 2006-10-15 15:42:58 +0200
From: Wouter Scherphof <<wscherphof>>
Logged In: YES
user_id=93938
I did update and rebuild template before running the test.
And I also did update and rebuild buildtools, MonetDB and
template before filing the bug. I guess the problem indeed
is that "old left-over libraries/DLLs might be found and
used instead of the new ones". I already hoped that the "11"
type would give you guys a clue :-) I will proceed now with
wiping everything out and starting all over.
## Comment 6039
Date: 2006-10-15 22:31:31 +0200
From: Wouter Scherphof <<wscherphof>>
Logged In: YES
user_id=93938
That helped. I think the whole problem was that I forgot
to do a nmake install (which, by the way, really should
be: nmake NEED_MX=1 install).
Thanks for your swift responses.
Regards, Wouter.
## Comment 6040
Date: 2006-10-15 22:53:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
appears to be fixed.
## Comment 6041
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1576870 at http://sourceforge.net/support/tracker.php?aid=1576870
| hello() misbehaves on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1074/comments | 0 | 2020-11-30T09:19:22Z | 2024-06-27T11:20:15Z | https://github.com/MonetDB/MonetDB/issues/1074 | 753,303,476 | 1,074 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-13 11:43:14 +0200
From: @Teggy
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-12-17 04:40:51 +0100
## Comment 6027
Date: 2006-10-13 11:43:14 +0200
From: @Teggy
Hi all. The query
let $x := <x id="0"><z id="0">zero</z></x>
return $x/z[@id = 0]
should yield <x id="0"><z id="0">zero</z></x>
but returns the empty sequence with the algebraic code
generator.
Note that (child::z step removed)
let $x := <x id="0"><z id="0">zero</z></x>
return $x[@id = 0]
works fine, though.
Cheers,
--Teggy
## Comment 6028
Date: 2006-10-13 11:46:43 +0200
From: @Teggy
Logged In: YES
user_id=642632
Woops. The first query
let $x := <x id="0"><z id="0">zero</z></x>
return $x/z[@id = 0]
is expected to return <z id="0">zero</z> instead of (), of
course.
--Teggy
## Comment 6029
Date: 2006-12-06 17:31:52 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This is most probably related to http://sourceforge.net/support/tracker.php?aid=1610247
Replacing 'z' by '*' works correctly ('let $x := <x id="0"><z id="0">zero</z></x> return $x/*[@id = 0]') and the only difference in the generated MIL code is the following line:
< a0001 := loop_lifted_child_step_with_nsloc_test (a0000, a0003, a0004, ws, 2, "", "z");
---
> a0001 := loop_lifted_child_step_with_kind_test (a0000, a0003, a0004, ws, 2, ELEMENT);
## Comment 6030
Date: 2006-12-17 16:40:51 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
this seems to work now
## Comment 6031
Date: 2006-12-17 17:24:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
test added in pathfinder/tests/BugTracker/Tests/Attic/attribute_value_comparison.SF-1576463.alg.*
seems to work fine.
## Comment 6032
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1576463 at http://sourceforge.net/support/tracker.php?aid=1576463
| PF/algebra: attribute/value comparison fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1073/comments | 0 | 2020-11-30T09:19:19Z | 2024-06-27T11:20:14Z | https://github.com/MonetDB/MonetDB/issues/1073 | 753,303,435 | 1,073 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-11 01:04:31 +0200
From: @sjoerdmullender
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2007-01-27 03:07:09 +0100
## Comment 6023
Date: 2006-10-11 13:04:31 +0200
From: @sjoerdmullender
The ia64 RPMs that are distributed through SourceForge
were built using the Intel C compiler. Moreover, these
RPMs depend on shared libraries that are part of the
icc distribution. This means that they are not
actually usable for "standard" installations, i.e.
installations where the correct version of icc was not
installed.
I realize that it is useful to try to build these RPMs
on a nightly basis, so we should continue doing so.
However, it is not so useful to distribute them. It
might be better to create ia64 RPMs using gcc for
distribution purposes.
## Comment 6024
Date: 2007-01-23 00:29:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Keep us reminded to take care of this for the upcoming release.
## Comment 6025
Date: 2007-01-27 15:07:09 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
IA64 RPMs for the upcoming have been built with gcc.
## Comment 6026
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1575184 at http://sourceforge.net/support/tracker.php?aid=1575184
| BUILD: ia64 RPMs built using icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1072/comments | 0 | 2020-11-30T09:19:16Z | 2024-06-27T11:20:13Z | https://github.com/MonetDB/MonetDB/issues/1072 | 753,303,395 | 1,072 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-09 12:00:11 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-10-14 01:56:56 +0200
## Comment 6017
Date: 2006-10-09 12:00:11 +0200
From: @drstmane
With 64-bit OIDs, all queries of the multi-document
XMach-1 benchmark hang "endlessly" (i.e., run into a
timeout, even if the timeout is extended to 10 minutes).
With 32-bit OIDs (both on 32-bit and 64-bit systems)
all XMach-1 queries run fine.
See e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMach-1/q1.err.00.html
## Comment 6018
Date: 2006-10-09 19:49:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
The problem appears to be as follows:
At the end of the query, ws_destroy() calls ws_free(), which
sets lock "pf_short" before calling _ws_free().
_ws_free(), in turn, checks whether the size of currently
cached documents (respectively the BATs that store them)
exceed the cache size limit (which in this case apparently
happens only with 64-bit OIDs, but not with 32-bit OIDs),
and if so, calls delete_all_docs(), which in turn calls
del_doc_base().
del_doc_base() also tries to set lock "pf_short", and
obviously has to wait, since its calling ancestor ws_free()
still holds the lock.
Hence, we have a classical deadlock!
I leave it to Peter to solve this inherent deadlock.
## Comment 6019
Date: 2006-10-10 02:06:45 +0200
From: @drstmane
Logged In: YES
user_id=572415
The same deadlock can occur between ws_opendoc() and
del_doc_base():
ws_opendoc() sets lock "pf_short", then calls _ws_opendoc(),
which might in turn call del_doc_base() to delete
stale/outdated cached documents.
del_doc_base() will then dead-lock when trying to aquire the
"pf_short" lock that's already held by its calling ancestor
ws_opendoc().
## Comment 6020
Date: 2006-10-10 08:46:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
The bug might potetially be fixed by the attached patch.
It renames del_doc_base() to _del_doc_base() and avoids
using lock "pf_short" inside _del_doc_base(). Instead, a new
del_doc_base() wrapper is added that sets lock "pf_short"
before calling _del_doc_base().
_del_doc_base() is used directly where ever we already hold
a "pf_short" lock.
del_doc_base() is used in all other places.
Caveat:
When calling the new del_doc_base(), lock "pf_short" is
set/held during the whole time that _del_doc_base(), which
is longer than in the original del_doc_base(), where lock
"pf_short" was only set/held during the execution of
_del_doc() & _del_doc_replace(), but releaved before setting
lock "pf_wal" and calling subcommit() ...
## Comment 6021
Date: 2006-10-14 13:56:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
resolved dead-locks on lock pf_lock between ws_destroy()
resp. ws_opendoc() and del_doc_base()
(Peter & Stefan)
## Comment 6022
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1573630 at http://sourceforge.net/support/tracker.php?aid=1573630
| XQ: all XMach-1 queries hang endlessly with 64bit OIDs | https://api.github.com/repos/MonetDB/MonetDB/issues/1071/comments | 0 | 2020-11-30T09:19:13Z | 2024-06-27T11:20:12Z | https://github.com/MonetDB/MonetDB/issues/1071 | 753,303,358 | 1,071 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-09 11:55:01 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-10-09 12:59:19 +0200
## Comment 6014
Date: 2006-10-09 11:55:01 +0200
From: @drstmane
Query q23 the X007 benchmark
========
let $doc :=
doc("/var/tmp/monet.GNU.64.64.d.30924/pathfinder/Fedora4/mTests/tests/X007/load_docs.xml")//doc/text()
let $d :=
doc(exactly-one($doc[1]))/ComplexAssembly/ComplexAssembly/ComplexAssembly/ComplexAssembly/BaseAssembly/CompositePart/Document[@MyID
= 25]
return
<After_DOC>
{$doc/ComplexAssembly/ComplexAssembly/ComplexAssembly/ComplexAssembly/BaseAssembly/CompositePart/Document[.
>> zero-or-one($d)]}
</After_DOC>
========
fails with
========
ERROR = !type error: no variant of function
op:node-after accepts the given argument type(s):
element Document { item* }; node?
!type error: maybe you meant:
!type error: op:node-after (node, node) as
boolean
!type error: illegal arguments for function
op:node-after
! halted in
/var/tmp/monet.GNU.64.64.d.30924/pathfinder/compiler/semantics/typecheck.brg
(fun_not_found), line 1288
========
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_X007/q23.err.00.html
## Comment 6015
Date: 2006-10-09 12:59:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by JanR in CVS:
-- replacing zero-or-one() by exactly-one() will probably help
Dankeschoen!!
## Comment 6016
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1573627 at http://sourceforge.net/support/tracker.php?aid=1573627
| XQ: X007 query q23: "type error" | https://api.github.com/repos/MonetDB/MonetDB/issues/1070/comments | 0 | 2020-11-30T09:19:10Z | 2024-06-27T11:20:11Z | https://github.com/MonetDB/MonetDB/issues/1070 | 753,303,322 | 1,070 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-09 11:52:46 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-11-01 11:12:16 +0100
## Comment 6009
Date: 2006-10-09 11:52:46 +0200
From: @drstmane
Query q05 of the X007 benchmark
========
let $doc :=
doc("/var/tmp/monet.GNU.64.64.d.30924/pathfinder/Fedora4/mTests/tests/X007/load_docs.xml")//doc/text()
for $b in
doc(exactly-one($doc[1]))/ComplexAssembly/ComplexAssembly/ComplexAssembly/ComplexAssembly/BaseAssembly,
$d in $b/CompositePart/Document
let $a := $b/CompositePart/Connection/AtomicPart
where $d/@MyID = $a/@docId
return $a
========
fails with
========
ERROR = !variable(s) out of scope or unknown: at
(6,10-6,11): $d
!variable(s) out of scope or unknown: erroneous
variable references reported above
! halted in
/var/tmp/monet.GNU.64.64.d.30924/pathfinder/compiler/semantics/varscope.c
(PFvarscope), line 660
========
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_X007/q05.err.00.html
## Comment 6010
Date: 2006-10-31 17:33:07 +0100
From: @drstmane
Logged In: YES
user_id=572415
The problem is that scoping seems to be broken in some
(though not all) cases with FOR and LET clauses that contain
(bind) multiple variables in a comma-seperated list, i.e.,
for $v1 := ... ,
$v2 := ...
and/or
let $v3 := ... ,
$v4 := ...
here are the cases where the error occurs:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_X007/q05.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q13.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_SEQ/Q5b.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_STRING/Q4.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q6.out.00.html
In these cases, though, everything seems to work fine:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_X007/q04.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_X007/q06.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_X007/q17.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_X007/q21.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_X007/q22.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XBench_DC_MD/q19.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XBench_DC_SD/q19.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XBench_TC_MD/q19.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XBench_TC_SD/q19.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XBench_TC_MD/q04.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XMach-1/q1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_NS/Q7.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q05o.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q05u.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q10.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q11.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_R/Q12x.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_SEQ/Q5c.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_SGML/Q10.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_AddressBook/Q1x.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q3a1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQUF_Parts/Q3a2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_XMP/Q02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_W3C_use_cases_XQ_XMP/Q05.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/ID.1490847.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XQuery/string-join.out.00.html
## Comment 6011
Date: 2006-10-31 18:00:09 +0100
From: @Teggy
Logged In: YES
user_id=642632
A shorter failing example is
let $x := 1, $y := 2
let $z := 3
return $y
--Teggy
## Comment 6012
Date: 2006-11-01 23:12:16 +0100
From: @Teggy
Logged In: YES
user_id=642632
This should be working now. Fix committed.
--Teggy
## Comment 6013
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1573626 at http://sourceforge.net/support/tracker.php?aid=1573626
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: variable scoping bug with multi-variable for/let clauses | https://api.github.com/repos/MonetDB/MonetDB/issues/1069/comments | 0 | 2020-11-30T09:19:07Z | 2024-06-27T11:20:10Z | https://github.com/MonetDB/MonetDB/issues/1069 | 753,303,283 | 1,069 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-08 07:05:06 +0200
From: @mlkersten
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-10-18 09:39:29 +0200
## Comment 6003
Date: 2006-10-08 19:05:06 +0200
From: @mlkersten
When you attempt to start SQL with an old catalog,
there is no indication what to do. The error message
should be extended with a) a reference to the
documentation and/or b) the easiest solution
(moving the old database aside using complete path
information)
problem reported by R. Kersten
## Comment 6004
Date: 2006-10-08 19:09:29 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Rene: Windows applications often ask what to do with
the existing application data & settings when you
uninstall a program
If the catalog is out of date, you may want to rename it.
## Comment 6005
Date: 2006-10-17 11:50:39 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
The last check in is to fix the problem when you start
mserver4. It crased when the system tryed to find the table
db_user_info.
Beste regards,
Romulo Goncalves
## Comment 6006
Date: 2006-10-17 12:47:45 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
Sorry the last comment from romulog was inserted in the
wrong discussion. It should have been inserted in "crash
when starting Merver with SQL".
Beste Regards,
Romulo Goncalves
## Comment 6007
Date: 2006-10-18 09:39:29 +0200
From: @grobian
Logged In: YES
user_id=963970
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!mvc_init: unable to create system tables
!ERROR: Incompatible database version 030201, this server
supports version 030202
!ERROR: Please move away
/ufs/fabian/scratch/monetdb/current/program-x86_64/var/MonetDB/log/demo/
and its corresponding dbfarm.
Is this sufficient? If not, please reopen.
## Comment 6008
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1573245 at http://sourceforge.net/support/tracker.php?aid=1573245
| SQL: Incomplete error message | https://api.github.com/repos/MonetDB/MonetDB/issues/1068/comments | 0 | 2020-11-30T09:19:03Z | 2024-06-27T11:20:09Z | https://github.com/MonetDB/MonetDB/issues/1068 | 753,303,222 | 1,068 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-08 10:31:06 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2006-10-09 11:42:00 +0200
## Comment 6000
Date: 2006-10-08 10:31:06 +0200
From: @drstmane
casts/converts in batconvert fail on BATs with
void-view head, i.e., BATs with a TYPE_void head that
is not "physically" void but a void-view on some
non-void storage type.
Why? --- Well, recall my "suggestive complaints" ... ;-)
Test added as
monet5/tests/BugTracker/Tests/batcalc-convert_on_void_view.SF-<ID_of_this_bug_report>.mal
$ cat /tmp/bc.mal
include microbenchmark;
head: oid
a:=microbenchmark.uniform(0:oid,9,9);
head: void view on oid
d:=algebra.markH(a,10:oid);
io.print(d);
e:=batcalc.sht(d);
io.print(e);
f:=batcalc.lng(d);
io.print(f);
$ mserver5 /tmp/bc.mal
MonetDB Server v4.99.19
Copyright (c) 1993-2006 CWI, all rights reserved
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs dynamically linked
config:/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d.--disable-optimize_--enable-debug_--enable-assert.PREFIX./MONET5/etc/MonetDB5.conf
dbfarm:/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d.--disable-optimize_--enable-debug_--enable-assert.PREFIX./MONET5/var/MonetDB5/dbfarm
dbname:demo
Visit http://monetdb.cwi.nl/ for further information
include microbenchmark;
head: oid
a:=microbenchmark.uniform(0:oid,9,9);
head: void view on oid
d:=algebra.markH(a,10:oid);
io.print(d);
e:=batcalc.sht(d);
io.print(e);
f:=batcalc.lng(d);
io.print(f);
function user.main():void; 0 (main:void)
line 26
"/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/kernel/microbenchmark.mx"
1 (_1:str)
head: oid 2 (_2:str)
a := microbenchmark.uniform(0@0:oid,9,9); 3
MBMuniform (a:bat[:oid,:int])<-(_4:oid)(_5:int)(_5:int)
head: void view on oid 4 (_6:str)
d := algebra.markH(a,10@0:oid); 5 ALGmarkHead
(d:bat[:void,:int])<-(a:bat[:oid,:int])(_8:oid)
io.print(d); 6 IOprint_val
(_9:int)<-(d:bat[:void,:int])
e := batcalc.sht(d); 7 CMDconvertint_sht
(e:bat[:void,:sht])<-(d:bat[:void,:int])
io.print(e); 8 IOprint_val
(_11:int)<-(e:bat[:void,:sht])
f := batcalc.lng(d); 9 CMDconvertint_lng
(f:bat[:void,:lng])<-(d:bat[:void,:int])
io.print(f); 10 IOprint_val
(_13:int)<-(f:bat[:void,:lng])
end main; 11
-----------------
t h name
void int type
-----------------
[ 10@0, 1 ]
[ 11@0, 6 ]
[ 12@0, 2 ]
[ 13@0, 0 ]
[ 14@0, 8 ]
[ 15@0, 3 ]
[ 16@0, 7 ]
[ 17@0, 4 ]
[ 18@0, 5 ]
-----------------
h t name
void sht type
-----------------
[ 10@0, 1 ]
[ 11@0, -9253 ] <<<<<<<<<
[ 12@0, 1 ] <<<<<<<<<
[ 13@0, 0 ]
[ 14@0, 6 ] <<<<<<<<<
[ 15@0, -9253 ] <<<<<<<<<
[ 16@0, 2 ] <<<<<<<<<
[ 17@0, 0 ] <<<<<<<<<
[ 18@0, 2 ] <<<<<<<<<
-------------------------
h t name
void lng type
-------------------------
[ 10@0, 1 ]
[ 11@0, -606348325 ] <<<<<<<<<
[ 12@0, 1 ] <<<<<<<<<
[ 13@0, 0 ]
[ 14@0, 6 ] <<<<<<<<<
[ 15@0, -606348325 ] <<<<<<<<<
[ 16@0, 2 ] <<<<<<<<<
[ 17@0, 0 ] <<<<<<<<<
[ 18@0, 2 ] <<<<<<<<<
## Comment 6001
Date: 2006-10-09 23:42:00 +0200
From: @mlkersten
Logged In: YES
user_id=490798
The new BAT coercion code solves this problem.
## Comment 6002
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1573060 at http://sourceforge.net/support/tracker.php?aid=1573060
| M5: casts/converts in batconvert fail on void-view heads | https://api.github.com/repos/MonetDB/MonetDB/issues/1067/comments | 0 | 2020-11-30T09:18:59Z | 2024-06-27T11:20:08Z | https://github.com/MonetDB/MonetDB/issues/1067 | 753,303,182 | 1,067 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-10-01 12:18:50 +0200
From: @mlkersten
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-10-03 01:26:28 +0200
## Comment 5996
Date: 2006-10-01 12:18:50 +0200
From: @mlkersten
Stefan (et.al).
In M5 I generated a call
BATjoin(:bat[:int,:oid],:bat[:oid,:void), E)
where E was an estimate.
This fired in BATpropcheck the test
(((b->batBuns->free > b->batBuns->size) &
((b->htype != TYPE_void) | (b->ttype !=
TYPE_void))) << 14);
because the first term was violated.
Replacing E by oid_nil solved it.
Now, the question remains, is size_estimate a real
estimate or a required_size. If an estimate then
it seems that BATjoin does not ignore it when
the actual size result is larger then needed.
If it is a required size, we need at least to
remove the confusion it creates.
Or BATpropcheck is too strict.
I have not yet been able to prepare the MIL
equivalent test.
## Comment 5997
Date: 2006-10-02 18:04:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Martin,
I cannot simply reproduce your problem:
========
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(radix);
MonetDB>debugmask((2*1024*1024)+10);
MonetDB>var a := uniform(123456);
MonetDB>var b := uniform(123456);
MonetDB>print(count(join(a,reverse(b))));
BATjoin: BAThashjoin(l,r,9223372036854775808);
[ 123456 ]
MonetDB>print(count(join(a,reverse(b),1LL)));
BATjoin: BAThashjoin(l,r,1);
[ 123456 ]
MonetDB>print(count(join(a,reverse(b),999999LL)));
BATjoin: BAThashjoin(l,r,999999);
[ 123456 ]
MonetDB>print(count(join(a,reverse(b),123456LL)));
BATjoin: BAThashjoin(l,r,123456);
[ 123456 ]
MonetDB>
========
Could you please provide/attach more information about the
case where the problem occured?
## Comment 5998
Date: 2006-10-03 01:26:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
in case BATfetchjoin was called with a result size
estimation != oid_nil,
a result BAT of the given size was allocated and filled
withou further checks;
without estimation (estimate == oid_nil) the size of the
left input was used
as save upper bound.
Fix: in case an estimation < BATcount(l) is provided, we
increase it to the
save upper bound of estimate = BATcount(l) (and hence still
avoid size checking
in BATfetchjoin'\''s inner loop.
For the next time:
In case you cannot find a simple way (script) to reproduce a
bug, please try to provide as detailed informtation as
possible; e.g., in case a join fails, re-run the test in
your setting with debugmask 2*1024*1024 to enable oin
algorithm tracing --- would have saved me a couple of hours
(and tomorrows lecture...) to reproduce a complex setup and
find out myself that (only) fetchjion failed...
Also added a (simple!) test in
tests/BugTracker/Tests/BATpropcheck-BATjoin.SF-1568652.milS
(created by simply running the original failing SQL query
(TPCH Q5) in Martin's "private" M5 setup, and simply
printing the join arguments before the crash ...).
## Comment 5999
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1568652 at http://sourceforge.net/support/tracker.php?aid=1568652
| BATpropcheck/BATjoin | https://api.github.com/repos/MonetDB/MonetDB/issues/1066/comments | 0 | 2020-11-30T09:18:56Z | 2024-06-27T11:20:07Z | https://github.com/MonetDB/MonetDB/issues/1066 | 753,303,146 | 1,066 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-28 03:00:50 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-09-29 09:45:36 +0200
## Comment 5991
Date: 2006-09-28 15:00:50 +0200
From: Maurice van Keulen <<mvankeulen>>
The attached query fails with error message
ERROR = !ERROR: interpret_while: bit(nil) => don't know
what to do!
Many simplications of the query somehow avoid the bug,
such as (1) putting everything outside the function,
(2) removing either <nonmultiple> or <count> from the
result of the function, (3) changing the 1 in the third
line to "1".
## Comment 5992
Date: 2006-09-28 15:07:47 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The error seems to be in the while in the proc log2 in
pf_support.
## Comment 5993
Date: 2006-09-28 18:57:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
(hopefully) fixed in CVS:
ll_htordered_unique_thetajoin could not properly handle the
case that one input is empty,
which would trigger log2() to be called with a NIL argument,
the max() of an empty BAT;
hence, we simply avoid this "optimization" step by having
ll_htordered_unique_thetajoin()
return an empty result immediately in case one input it empty.
At least Maurice'\''s test now works fine, and no other
tests seems to be harmed...
Added test in
tests/BugTracker/Tests/interpret_while-bit_nil.SF-1567021.xq
Maurice,
could you please double-check and close?
(Worked perfectly with the other bug report(s)!)
## Comment 5994
Date: 2006-09-29 09:45:36 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Fix seems to resolve the bug nicely.
## Comment 5995
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1567021 at http://sourceforge.net/support/tracker.php?aid=1567021
| interpret_while: bit(nil) => don't know what to do! | https://api.github.com/repos/MonetDB/MonetDB/issues/1065/comments | 0 | 2020-11-30T09:18:53Z | 2024-06-27T11:20:06Z | https://github.com/MonetDB/MonetDB/issues/1065 | 753,303,119 | 1,065 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-28 09:06:51 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-09-28 07:02:29 +0200
## Comment 5988
Date: 2006-09-28 09:06:51 +0200
From: @drstmane
After yesterday's ll_upwards changes, test
tests/XQuery/Tests/transient_upward_steps.xq runs into
a timeout (even if I increase that to 10 minutes);
i.e., it seems to hang (possibly in some end-less loop).
## Comment 5989
Date: 2006-09-28 19:02:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Peter in CVS.
## Comment 5990
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1566825 at http://sourceforge.net/support/tracker.php?aid=1566825
| PF: test tests/XQuery/Tests/transient_upward_steps.xq hangs | https://api.github.com/repos/MonetDB/MonetDB/issues/1064/comments | 0 | 2020-11-30T09:18:50Z | 2024-06-27T11:20:05Z | https://github.com/MonetDB/MonetDB/issues/1064 | 753,303,092 | 1,064 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-28 08:59:23 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-09-29 09:01:45 +0200
## Comment 5986
Date: 2006-09-28 08:59:23 +0200
From: @drstmane
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora4/make-k.out
for details
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/pathfinder/compiler/debug
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/pathfinder/compiler/debug
-I../include
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/pathfinder/compiler/debug/../include
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.1454/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-DLIBDEBUG -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
/export/scratch0/monet/monet.ntv.64.64.d.1454/pathfinder/compiler/debug/abssynprint.c
-KPIC -DPIC -o .libs/libdebug_la-abssynprint.o
/export/scratch0/monet/monet.ntv.64.64.d.1454/pathfinder/compiler/debug/../include/logical.h(796):
error 310: old-style parameter list (anachronism)
PFla_op_t *PFla_rec_nil ();
^
compilation aborted for
/export/scratch0/monet/monet.ntv.64.64.d.1454/pathfinder/compiler/debug/abssynprint.c
(code 2)
make[5]: *** [libdebug_la-abssynprint.lo] Error 1
## Comment 5987
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1566822 at http://sourceforge.net/support/tracker.php?aid=1566822
| PF: compilation fails with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1063/comments | 0 | 2020-11-30T09:18:47Z | 2024-06-27T11:20:04Z | https://github.com/MonetDB/MonetDB/issues/1063 | 753,303,061 | 1,063 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-28 08:54:49 +0200
From: @drstmane
To: Romulo Goncalves <<goncalve>>
Version: -- development
Last updated: 2006-09-29 10:57:51 +0200
## Comment 5976
Date: 2006-09-28 08:54:49 +0200
From: @drstmane
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.GNU.64.64.d-Fedora4/make-k.out
for details.
gcc -m64 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.64.64.d.1454/sql/src/server
-I../..
-I/var/tmp/monet.GNU.64.64.d.1454/sql/src/server
-I../include
-I/var/tmp/monet.GNU.64.64.d.1454/sql/src/server/../include
-I../common
-I/var/tmp/monet.GNU.64.64.d.1454/sql/src/server/../common
-I../storage
-I/var/tmp/monet.GNU.64.64.d.1454/sql/src/server/../storage
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5/atoms
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5/compiler
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5/kernel
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5/mal
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5/mil
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5/optimizer
-I/var/tmp/monet.GNU.64.64.d.1454/monet5/.GNU.64.64.d-Fedora4/include/MonetDB5
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/common
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/gdk
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/monet
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/plain
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/contrib
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/mapi
-I/var/tmp/monet.GNU.64.64.d.1454/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/C
-DLIBSQLSERVER -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-sign-compare -c sql_scan.c -fPIC -DPIC -o
.libs/libsqlserver_la-sql_scan.o
cc1: warnings being treated as errors
/var/tmp/monet.GNU.64.64.d.1454/sql/src/server/sql_scan.mx:
In function 'number':
/var/tmp/monet.GNU.64.64.d.1454/sql/src/server/sql_scan.mx:650:
warning: 'token' may be used uninitialized in this function
make[5]: *** [libsqlserver_la-sql_scan.lo] Error 1
## Comment 5977
Date: 2006-09-28 09:20:59 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
I compiled in my computer and I do not have such errors. It
is also strange that the checkin of yesterday did not arrive
in my email.
Regards,
Romulo
## Comment 5978
Date: 2006-09-28 09:36:08 +0200
From: @grobian
Logged In: YES
user_id=963970
assign a default value to token. Is used to be SQLint, what
should it be now?
## Comment 5979
Date: 2006-09-28 09:47:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Compilation fails when configured with --enable-optimize
(default with nightly testing) --- sorry for not mentioning
this explicitly in the first place ...
Hence, it's indeed still "your" bug ;-)
About the checkin emails:
Only the first of your yesterday's checkin messages arrived
in my mailbox:
===================================================================
2006/09/27 - romulog: src/server/sql_parser.mx,1.212
src/server/sql_scan.mx,1.107
src/server/sql_select.mx,1.155
Convert hexadecimal numbers to decimal numbers in SQL
queries. Translation done directly in the parser.
===================================================================
The other two did not (yet):
===================================================================
2006/09/27 - romulog: src/server/sql_scan.mx,1.108
Fixing bug in the function number().
The current character should be tested again to see if it is
a digit or not.
===================================================================
2006/09/27 - romulog: src/backends/monet5/sql_gencode.mx,1.206
src/server/sql_psm.mx,1.21 src/test/psm.sql,1.8
src/test/Tests/psm.stable.out,1.4
Now the IF clause can be defined without an ELSE clause.
A test was added to psm to test this new feature.
===================================================================
Might be an "ordinary" SF overload problem ...
## Comment 5980
Date: 2006-09-28 09:48:03 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
It should be SQLint. The checkin was already done. Why my
compiler did not give such errors?
Regards, Romulo
## Comment 5981
Date: 2006-09-28 09:54:28 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
In my configure I use --enable-debug. It set all the options
include optimize, right or wrong?
Regards,
Romulo
## Comment 5982
Date: 2006-09-28 09:55:12 +0200
From: @drstmane
Logged In: YES
user_id=572415
Romulo,
as said, the error occurs only when compiled with
optimization enabled. It is fine, if you compile with
different options before checking in, i.e., you don't have
to test with optimization enabled (just like you don't have
to test with other compilers and or on other systems).
Nightly testing does all this "for you" --- you only need to
check the next compilation/testing results after your
checking to see, whether your changes caused any problems
with the automatic testing setup, i.e., on an other
platform, with an other compiler and/or with other
configure/compilation options.
## Comment 5983
Date: 2006-09-28 10:15:55 +0200
From: @romulogoncalves
Logged In: YES
user_id=1498628
It was a mistake not like fabian said SQLint, but it should
be sqlINT.
Regards, Romulo....
## Comment 5984
Date: 2006-09-29 10:57:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Romulo in CVS.
## Comment 5985
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1566821 at http://sourceforge.net/support/tracker.php?aid=1566821
| SQL: compilation fails with gcc | https://api.github.com/repos/MonetDB/MonetDB/issues/1062/comments | 0 | 2020-11-30T09:18:44Z | 2024-06-27T11:20:03Z | https://github.com/MonetDB/MonetDB/issues/1062 | 753,303,021 | 1,062 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-26 09:51:03 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-09-26 07:43:02 +0200
## Comment 5973
Date: 2006-09-26 09:51:03 +0200
From: @drstmane
Since the back-merge of the "new_updates" branch into
the development trunk, 4 of the VOC tests fail if
MonetDB/XQuery is compiled with 32-bit OIDs.
(Most probably, this problem already occured in the
"new_updates" branch, but we (at least I) never tested
that one with 32-bit OIDs.)
For details, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.32.d-Fedora4/tests_WebSite/voc2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_WebSite/voc3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_WebSite/voc4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_WebSite/voc5.out.00.html
## Comment 5974
Date: 2006-09-26 19:43:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
the "poor man's binary search / exploiting forward scan"
requires that we use strides that are a multipe of any
expected BUNsize;
the idea to use multiples (actually even powers) of 32
should be save ---
provided that we avoid typos ...
32 = 32^1 is OK
1024 = 32^2 is OK
32768 = 32^3 is OK
104876, however is not 32^4; actaully it's largest power of
2 factor is 4;
1048576 = 32^4 work much better ...
(yet another nasty bug that took far too much time to be
fixed ... |-(()
## Comment 5975
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1565537 at http://sourceforge.net/support/tracker.php?aid=1565537
| XQuery: VOC tests fail with 32-bit OIDs | https://api.github.com/repos/MonetDB/MonetDB/issues/1061/comments | 0 | 2020-11-30T09:18:41Z | 2024-06-27T11:20:02Z | https://github.com/MonetDB/MonetDB/issues/1061 | 753,302,986 | 1,061 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-25 12:26:29 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-10-06 11:23:05 +0200
## Comment 5968
Date: 2006-09-25 12:26:29 +0200
From: @drstmane
Since Friday's (Sep 22 2006) changes to autogen ("Add a
-module flag to libtool invocations to link modules.
[...]"), MonetDB fails to compile on Darwin.
See the following for details (look for "***"):
initial `make`:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.32.32.d-Darwin8.7.0/make.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-Darwin8.7.0/make.out
subsequent `make -k`:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.32.32.d-Darwin8.7.0/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-Darwin8.7.0/make-k.out
## Comment 5969
Date: 2006-09-26 12:27:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for info:
We now also get linker warnings like
*** Warning: Linking the shared library lib_enum.la against
the loadable module
*** lib_streams.so is not portable!
on all (Unix-like) platforms.
## Comment 5970
Date: 2006-09-26 13:15:25 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I noticed the warning, but secretly hoped that it was benign.
The problem that is solved by the -module flag is that
without it we get name clashes between M4 and M5 on Cygwin
because without it module dlls are installed in the same bin
directory. Also, since we are actually creating modules
that are to be loaded with dlopen, the -module flag is the
right thing to do. However, some modules are *also* used as
libraries, and this is what causes the problem.
Removing the -module flag is not desirable, in my opinion,
since it causes problems on Windows. This means we should
perhaps split the modules that are also used as libraries
into actual libraries and modules.
## Comment 5971
Date: 2006-10-06 11:23:04 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Things compile again on Darwin.
The solution was to again get rid of the -module flag to
libtool and instead have an extra directory layer to solve
the file name clash between M4 and M5 on Cygwin.
## Comment 5972
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1564970 at http://sourceforge.net/support/tracker.php?aid=1564970
| MonetDB fails to compile on Darwin since autogen changes | https://api.github.com/repos/MonetDB/MonetDB/issues/1060/comments | 0 | 2020-11-30T09:18:37Z | 2024-06-27T11:20:01Z | https://github.com/MonetDB/MonetDB/issues/1060 | 753,302,946 | 1,060 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-25 12:09:00 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-09-28 11:17:19 +0200
## Comment 5964
Date: 2006-09-25 12:09:00 +0200
From: Maurice van Keulen <<mvankeulen>>
The query
let $doc := <a>foo</a>
return
for $elem in $doc/descendant-or-self::node()
return <res>{$elem/name()}</res>
fails with
ERROR = !ERROR: merged_union: BAT 4 (1 BUNs) must have
the same size as BAT 2 (2 BUNs).
!ERROR: CMDmerged_union: operation failed.
I've noticed many other similar errors, e.g. concerning
alignment, where I suspect name(), but I haven't been
able to reproduce these in small examples.
## Comment 5965
Date: 2006-09-27 19:39:50 +0200
From: @drstmane
Logged In: YES
user_id=572415
hopefully fixed in CVS.
Maurice,
could you please check, whether the fix also works for you,
and whether the stable output I provided in
pathfinder/tests/BugTracker/Tests/fn-name_on_text_nodes.SF-1564964.stable.out
is correct?
If so, please close the bug report.
## Comment 5966
Date: 2006-09-28 11:17:19 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Fix checks out fine.
## Comment 5967
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1564964 at http://sourceforge.net/support/tracker.php?aid=1564964
| XQuery: name() on text nodes fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1059/comments | 0 | 2020-11-30T09:18:34Z | 2024-06-27T11:20:00Z | https://github.com/MonetDB/MonetDB/issues/1059 | 753,302,900 | 1,059 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-25 10:51:05 +0200
From: @grobian
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2007-12-19 04:20:04 +0100
## Comment 5957
Date: 2006-09-25 10:51:05 +0200
From: @grobian
sql/src/jdbc/example/XQueryLoad.java fails when being
executed with the following error:
% java -cp ../jars/monetdb-1.4-jdbc.jar:. XQueryLoad
Exception in thread "main" java.sql.SQLException:
ERROR: interpret: no matching MIL operator to
'shred_stream(Stream, str, str, int)'.
MAYBE YOU MEAN:
shred_stream(Stream, str, str, lng) : void
shred_stream(BAT[str,BAT], Stream, lng, lock) :
void
at
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2342)
at
nl.cwi.monetdb.jdbc.MonetConnection.copyToServer(MonetConnection.java:1184)
at
nl.cwi.monetdb.jdbc.MonetStatement.executeBatch(MonetStatement.java:194)
at XQueryLoad.main(XQueryLoad.java:42)
It looks like the Xcopy command of the server isn't
working properly.
## Comment 5958
Date: 2006-10-29 01:38:45 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Is this still a problem?
## Comment 5959
Date: 2006-12-14 18:51:46 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Fabian:
is this problem still occurring?
I am wondering why jdbc calls shred_stream? Maybe it is functionality that allows shredding of client-side XML?
In any case; that is part of the mapi handler code (xquery_client_engine / pathfinder.mx) that works; at least when called from MapiClient.
Anyway, it is not so clear to me how to reproduce the bug. If a test script should be added, would it be in the SQL or the JDBC test web?
questions.. questions..
Peter
PS
The current signature for shred_stream() is:
shred_stream(BAT[str,bat], Stream s, lng percentage, lock l)
and in MIL one generate statements like:
var b := bat(str,bat);
shred_stream(b, s, 0LL, lock(nil));
## Comment 5960
Date: 2006-12-14 19:04:14 +0100
From: @grobian
Logged In: YES
user_id=963970
Originator: YES
Hard to add a test for, since we can't assure XQuery support from SQL. (Clients move should make this possible to add a test for).
I cannot set this up currently, so cannot check if it works now.
## Comment 5961
Date: 2006-12-18 11:13:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
making this one "pending", in case we ever come up with an idea (how) to add a respective test.
## Comment 5962
Date: 2007-12-19 04:20:04 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 5963
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1564916 at http://sourceforge.net/support/tracker.php?aid=1564916
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: Xcopy command fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1058/comments | 0 | 2020-11-30T09:18:30Z | 2024-06-27T11:19:59Z | https://github.com/MonetDB/MonetDB/issues/1058 | 753,302,858 | 1,058 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-22 09:48:32 +0200
From: Maurice van Keulen <<mvankeulen>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-12-17 05:36:37 +0100
## Comment 5952
Date: 2006-09-22 09:48:32 +0200
From: Maurice van Keulen <<mvankeulen>>
Query below fails with error message
ERROR = !type error: can't cast type 'string*' to type
'node*'
! halted in milprint_summer.c
(simplifyCoreTree), line 8956
Probably something to do with name()
declare function namestring($node as element())
as xs:string
{
let $n1 := $node/descendant-or-self::element()/name()
return string-join($n1,",")
};
let $doc := <movies><movie><title>King
Kong</title><year>1933</year></movie></movies>
return namestring($doc)
## Comment 5953
Date: 2006-09-27 17:07:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
In fact, this is a compile-time type error.
## Comment 5954
Date: 2006-09-27 19:36:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
test added in
pathfinder/tests/BugTracker/Tests/type_errors_with_fn-name.SF-1563354.xq
(correct/expected output needs to be provided by hand or
approved once the bug is fixed)
## Comment 5955
Date: 2006-12-17 17:36:37 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
this works now.. for me at least.
## Comment 5956
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1563354 at http://sourceforge.net/support/tracker.php?aid=1563354
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: compile-time type errors with name() | https://api.github.com/repos/MonetDB/MonetDB/issues/1057/comments | 0 | 2020-11-30T09:18:27Z | 2024-06-27T11:19:58Z | https://github.com/MonetDB/MonetDB/issues/1057 | 753,302,814 | 1,057 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-21 03:30:02 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-11-03 07:27:53 +0100
## Comment 5941
Date: 2006-09-21 15:30:02 +0200
From: Maurice van Keulen <<mvankeulen>>
The attached query contains a function "integrate"
which runs fine when called as
"integrate($allb,$db1,$db2)", but it failes with the
error below when called with slightly different
operands "integrate($alla,$da1,$da2)" (see bottom part
of attached query)
ERROR = !ERROR: batbat_lng_add_inplace: BATs l & r must
be void-headed and head-aligned.
!ERROR: batbat_lng_add_inplace: operation failed.
!ERROR: interpret_params: access(param 1):
evaluation error.
## Comment 5942
Date: 2006-09-28 10:23:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Tests added as
pathfinder/tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-OK.SF-1562868.xq
using "integrate($allb,$db1,$db2)", runs w/o error;
Maurice,
could you please check/verify the stable output I checked in?
pathfinder/tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-KO.SF-1562868.xq
using "integrate($alla,$da1,$da2)", fails with above error;
correct/expected output needs to be added by hand or
approved once the bug is fixed.
## Comment 5943
Date: 2006-09-29 09:48:53 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
I tried to isolate the bug, but could not reduce the query
to less than the newly attached query. Removing query code
at various places seems to circumvent the bug.
## Comment 5944
Date: 2006-09-29 11:32:32 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The problem happens in the first call to [:+=] in
ll_htordered_unique_thetajoin and in the second occurance of
that function in the generated MIL code. The arguments
join_item1, join_item2, and match_outer007 all are of length
8, but match_outer006 only has length 4, and that difference
is what generates the error.
## Comment 5945
Date: 2006-09-29 11:54:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
some more back-tracing:
match_outer006 is created in milprint_summer's evaluate_join
function in section "/* introduce the correct map relation
(if lev_snd == UDF_LEV) */"
For the newly attached query, the generated code:
========
var mapping := loop000.reverse().mirror();
mapping := mapping.leftjoin(outer001.reverse());
mapping := mapping.leftfetchjoin(inner001);
mapping := mapping.leftjoin(outer002.reverse());
mapping := mapping.leftfetchjoin(inner002);
match_outer006 :=
iter.leftjoin(mapping.reverse()).tmark(iter.seqbase());
========
results in the following trace:
========
[ "loop000" ]
-----------------
h t name
void void type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 2@0 ]
[ 2@0, 3@0 ]
[ 3@0, 4@0 ]
[ 4@0, 5@0 ]
[ 5@0, 6@0 ]
[ 6@0, 7@0 ]
[ 7@0, 8@0 ]
[ "outer001.reverse()" ]
-----------------
h t name
oid void type
-----------------
[ 1@0, 0@0 ]
[ 2@0, 1@0 ]
[ 3@0, 2@0 ]
[ 6@0, 3@0 ]
[ 7@0, 4@0 ]
[ 8@0, 5@0 ]
[ 12@0, 6@0 ]
[ 15@0, 7@0 ]
[ "inner001" ]
-----------------
h t name
void void type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 2@0 ]
[ 2@0, 3@0 ]
[ 3@0, 4@0 ]
[ 4@0, 5@0 ]
[ 5@0, 6@0 ]
[ 6@0, 7@0 ]
[ 7@0, 8@0 ]
[ "outer002.reverse()" ]
-----------------
h t name
oid void type
-----------------
[ 1@0, 0@0 ]
[ 2@0, 1@0 ]
[ 3@0, 2@0 ]
[ 6@0, 3@0 ]
[ 7@0, 4@0 ]
[ 8@0, 5@0 ]
[ 12@0, 6@0 ]
[ 15@0, 7@0 ]
[ "inner002" ]
-----------------
h t name
void void type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 2@0 ]
[ 2@0, 3@0 ]
[ 3@0, 4@0 ]
[ 4@0, 5@0 ]
[ 5@0, 6@0 ]
[ 6@0, 7@0 ]
[ 7@0, 8@0 ]
[ "mapping" ]
-----------------
h t name
oid oid type
-----------------
[ 1@0, 1@0 ]
[ 2@0, 2@0 ]
[ 3@0, 3@0 ]
[ 8@0, 4@0 ]
[ "iter" ]
-----------------
t h name
void void type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 2@0 ]
[ 2@0, 3@0 ]
[ 3@0, 4@0 ]
[ 4@0, 5@0 ]
[ 5@0, 6@0 ]
[ 6@0, 7@0 ]
[ 7@0, 8@0 ]
[ "match_outer006" ]
-----------------
t h name
void oid type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 2@0 ]
[ 2@0, 3@0 ]
[ 3@0, 8@0 ]
========
I haven't traced further back, yet, where/why the
non-matching loop000/outer001 resp. inner001/outer002 BATs
are generated...
## Comment 5946
Date: 2006-09-29 14:32:12 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Sorry, but I have to conclude that you will have quite a
hard time figuring out what's wrong here (- it took myself
about 2 hours :( ... :|).
The problem is that the mps code evolved over the time,
which lead to decisions that do not match the original
intentention:
The idea to generate a chain of map-joins to map the results
of a thetajoin conflicts with the translation of the
if-then-else expression. An if-then-else expression is
optimized if the condition is either true or false for all
iterations. This optimization leads to a map relation that
is only a copy of the previous one (and not a new scope
e.g., 'outer002 := outer001; inner002 := inner001;'). A
chain of joins (with e.g.,
'inner001.leftfetchjoin(outer002.reverse());') thus leads to
bogus values...
The fast and ugly solution would be to replace 'skip = 0' in
milprint_summer.c by 'true'...
... But feel free to find a better solution :)
## Comment 5947
Date: 2006-10-02 10:33:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Replacing "(skip = 0)" by "(true)" in milprint_summer.c
seems to fix the new test
tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-KO2.SF-1562868.xq,
but the other two tests for this bug
tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-OK.SF-1562868.xq,
tests/BugTracker/Tests/complex-XQuery-batbat_lng_add_inplace-error-KO.SF-1562868.xq,
as well as
tests/BugsViaSourgeforce/Tests/ID.1297836-1.xq
then fail with
ERROR = !ERROR: interpret: no matching MIL operator to
'ord_uselect(oid, oid)'.
!MAYBE YOU MEAN:
! ord_uselect(BAT[any::1,any::2], any::2) :
BAT[any::1,void]
! ord_uselect(BAT[any::1,any::2], any::2, any::2,
bit, bit) : BAT[any::1,void]
! ord_uselect(BAT[any::1,any::2], any::2, any::2) :
BAT[any::1,void]
and
tests/XQuery/Tests/fn_true_false.xq
fails with
QUERY = if (true()) then false() else true()
ERROR = !ERROR: interpret: no matching MIL operator to
'mirror(void)'.
!MAYBE YOU MEAN:
! mirror(BAT[any::1,any]) : BAT[any::1,any::1]
!ERROR: interpret_params: join(param 1): evaluation
error.
... more work is necessary to solve this one ...
## Comment 5948
Date: 2006-10-13 14:57:01 +0200
From: Maurice van Keulen <<mvankeulen>>
Logged In: YES
user_id=654674
Replacing the "(skip = 0)" with "(true)" also produces many
'mirror(void)'-errors in my trials. They seem be caused by a
variable "item" not being materialized, which results the
variable "selected" to become nil and selected.mirror()
fails. Adding the following line to translateIfThenElse in
milprint_summer (after the comment explaining the idea)
seems to solve it.
milprintf(f, "item%03u := item%03u.materialize(ipik);\n",
bool_res, bool_res);
I'm not sure, however, whether or not this is the proper
fix, i.e., whether or not the materialization-issue is
better dealt with in another way.
## Comment 5949
Date: 2006-10-15 13:21:51 +0200
From: @drstmane
Logged In: YES
user_id=572415
Indeed, the attached patch, i.e., replacing all "(skip = 0)"
with "(true)" in translateIfThen() and adding
milprintf(f, "item%03u := item%03u.materialize(ipik);\n",
bool_res, bool_res);
to translateIfThenElse() seems to solve this bug without
casuing any other harm.
I haven't had time to analyse/understand the details, yet...
## Comment 5950
Date: 2006-11-03 19:27:53 +0100
From: @drstmane
Logged In: YES
user_id=572415
(finally) fixed in CVS:
trading in optimization (performance?) for correctness:
The optimization to omit the eveluation of empty
if-then-else branches
is broken, and since noone has been able to fix it, yet, we
simply
disable this optimization --- the performance "penalty"
should not be
too big, since the inpu to the respective branch is empty.
## Comment 5951
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1562868 at http://sourceforge.net/support/tracker.php?aid=1562868
| XQ: complex q fails with error in "batbat_lng_add_inplace" | https://api.github.com/repos/MonetDB/MonetDB/issues/1056/comments | 0 | 2020-11-30T09:18:24Z | 2024-06-27T11:19:57Z | https://github.com/MonetDB/MonetDB/issues/1056 | 753,302,780 | 1,056 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-21 10:21:01 +0200
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2007-01-17 06:35:33 +0100
## Comment 5936
Date: 2006-09-21 10:21:01 +0200
From: @drstmane
Configured with "--enable-optimize" (the default for
automatic nightly testing),
PFtijah fails to compile with gcc 3.4.5 on Solaris 10 x86.
For details, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d-SunOS5.10/make-k.out
========
gcc -DHAVE_CONFIG_H -I.
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/common
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/gdk
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/monet
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/plain
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/contrib
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/mapi
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -O2 -std=c99 -D__EXTENSIONS__ -Wall -W
-fno-strict-aliasing -O6 -fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop -frerun-loop-opt
-DHWCOUNTERS -DHW_SunOS -DHW_i86pc
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -c
/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/nexi.c
-fPIC -DPIC -o
.libs/lib_pftijah_la-nexi.o/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/nexi.c:
In function `myfileName':
/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/nexi.c:1353:
warning: int format, pid_t arg (arg 5)
gmake[5]: *** [lib_pftijah_la-nexi.lo] Error 1
--------
gcc -DHAVE_CONFIG_H -I.
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/common
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/gdk
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/monet
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/plain
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/contrib
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/mapi
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -O2 -std=c99 -D__EXTENSIONS__ -Wall -W
-fno-strict-aliasing -O6 -fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop -frerun-loop-opt
-DHWCOUNTERS -DHW_SunOS -DHW_i86pc
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -c pftijah_tokenize.yy.c -fPIC
-DPIC -o .libs/lib_pftijah_la-pftijah_tokenize.yy.o
In file included from
/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/common/monet_utils.h:5,
from
/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/gdk/gdk.h:5,
from
/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/pftijah_tokenize.l:7:
/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/monetdb_config.h:661:1:
"_FILE_OFFSET_BITS" redefined
In file included from
/opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/include/stdio.h:36,
from lex.yy.c:29:
/usr/include/sys/feature_tests.h:188:1: this is the
location of the previous definition
gmake[5]: *** [lib_pftijah_la-pftijah_tokenize.yy.lo]
Error 1
--------
gcc -DHAVE_CONFIG_H -I.
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/common
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/gdk
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/monet
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/plain
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/contrib
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/mapi
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -O2 -std=c99 -D__EXTENSIONS__ -Wall -W
-fno-strict-aliasing -O6 -fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop -frerun-loop-opt
-DHWCOUNTERS -DHW_SunOS -DHW_i86pc
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -c nexi.yy.c -fPIC -DPIC -o
.libs/lib_pftijah_la-nexi.yy.o
In file included from
/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/common/monet_utils.h:5,
from
/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/gdk/gdk.h:5,
from serialize_pftijah.h:3,
from
/export/scratch1/monet/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/nexi.l:19:
/export/scratch1/monet/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-SunOS5.10/include/MonetDB/monetdb_config.h:661:1:
"_FILE_OFFSET_BITS" redefined
In file included from
/opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/include/stdio.h:36,
from lex.yy.c:29:
/usr/include/sys/feature_tests.h:188:1: this is the
location of the previous definition
gmake[5]: *** [lib_pftijah_la-nexi.yy.lo] Error 1
========
## Comment 5937
Date: 2006-09-21 11:39:14 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Repaired it (I think). I will check tomorrow.
* Put an (int) cast before the getpid() call
* simplified the include structure in pftijah_tokenize.l to
prevent multiple definitions for _FILE_OFFSET_BITS
## Comment 5938
Date: 2006-09-26 20:18:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Until the quite "priciple" compilation problems (cf.,
http://sourceforge.net/mailarchive/forum.php?thread_id=30604011&forum_id=39803)
are "properly" solved, we do not try to compile the pftijah
modules on SunOS/Solaris.
## Comment 5939
Date: 2007-01-17 18:35:33 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
With the repository split, the way of including *_config.h has been fixed, and compilation of PfTijah now also works fine on SunOS.
## Comment 5940
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1562713 at http://sourceforge.net/support/tracker.php?aid=1562713
| PFtijah fails to compile with gcc 3.4.5 on Solaris10 x86 | https://api.github.com/repos/MonetDB/MonetDB/issues/1055/comments | 0 | 2020-11-30T09:18:20Z | 2024-06-27T11:19:56Z | https://github.com/MonetDB/MonetDB/issues/1055 | 753,302,730 | 1,055 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-21 10:17:22 +0200
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2006-09-25 10:40:49 +0200
## Comment 5928
Date: 2006-09-21 10:17:22 +0200
From: @drstmane
Configured with "--enable-optimize" (the default for
automatic nightly testing),
PFtijah fails to compile with gcc 4.0.2 on Gentoo
1.12.4 and gcc 3.4.4 on Debian 3.1.
For details, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d-Gentoo1.12.4/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Debian3.1/make-k.out
========
t.GNU.32.32.d.18954/pathfinder/modules/pftijah -I../..
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../runtime
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c
pftijah_tokenize.yy.c -fPIC -DPIC -o
.libs/lib_pftijah_la-pftijah_tokenize.yy.o
cc1: warnings being treated as errors
lex.yy.c: In function 'yy_get_next_buffer':
lex.yy.c:1032: warning: comparison between signed and
unsigned
make[5]: *** [lib_pftijah_la-pftijah_tokenize.yy.lo]
Error 1
--------
gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../..
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../runtime
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.18954/MonetDB/.GNU.32.32.d-Gentoo1.12.4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/var/tmp/monet.GNU.32.32.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c nexi.yy.c
-fPIC -DPIC -o .libs/lib_pftijah_la-nexi.yy.o
cc1: warnings being treated as errors
lex.yy.c: In function 'yy_get_next_buffer':
lex.yy.c:1336: warning: comparison between signed and
unsigned
make[5]: *** [lib_pftijah_la-nexi.yy.lo] Error 1
========
## Comment 5929
Date: 2006-09-21 15:22:08 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I find this a hard one to check. I cannot see what lex.yy.c
is generated by (f)lex on these architectures. So I cannot
see which signed/unsigned comparisson causes the problem!
Any hints???
## Comment 5930
Date: 2006-09-21 15:30:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
At
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d-Gentoo1.12.4/pathfinder-0.13.1.tar.gz
and
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Debian3.1/pathfinder-0.13.1.tar.gz
you find the nightly tar-balls created via `make dist` on
the respective platforms. In there, you sould find the
(f)lex & bison/yacc generated .c files.
Let us now (here) whether this helps, or whether you need
more...
## Comment 5931
Date: 2006-09-21 16:04:29 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
OK Thanx Stefan. But it does not bring the solution any
closer because I think it is a flex problem because I do not
have any influence on the code generated. The error occurs
in line 1336. This line reads:
YY_INPUT((&YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
(yy_n_chars), num_to_read );
The definition of YY_INPUT is:
ifndef YY_INPUT
define YY_INPUT(buf,result,max_size) \
if ( YY_CURRENT_BUFFER_LVALUE->yy_is_interactive ) \
{ \
int c = '*'; \
size_t n; \
for ( n = 0; n < max_size && \
(c = getc( nexiin )) != EOF &&
c != '\n'; ++n ) \
buf[n] = (char) c; \
if ( c == '\n' ) \
buf[n++] = (char) c; \
if ( c == EOF && ferror( nexiin ) ) \
YY_FATAL_ERROR( "input in flex
scanner failed" ); \
result = n; \
} \
else \
{ \
errno=0; \
while ( (result = fread(buf, 1, max_size,
nexiin))==0 && ferror(nexiin)) \
{ \
if( errno != EINTR) \
{ \
YY_FATAL_ERROR( "input in
flex scanner failed" ); \
break; \
} \
errno=0; \
clearerr(nexiin); \
} \
}\
\
endif
I did not change anything here so the code is completely
generated by flex. So I would not know a quick solution at
this momenbt without screwing up on other architectures. I
will have a look at other flexers.
Continuing!
## Comment 5932
Date: 2006-09-21 16:51:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
Yep, this indeed seem to be a flex 2.5.33 problem:
It defines "num_to_read" as int and then compares it to "n",
which is a size_t ...
We use flex 2.5.33 only on these two platform (Gentoo 1.12.4
& Debian 3.1); all others use flex 2.5.4, which defines both
"num_to_read" & "n" as int.
The problem only occurs with pfthijah, as all other lexers
in the MonetDB source base (MEL, MIL, XQuery) define their
own YY_INPUT.
Possible solutions here:
1) provide a self-made YY_INPUT also with pftijah
2) disallow usage of flex 2.5.33 (we already reject flex
2.5.31); since there is no newer flex, yet (cf.
http://flex.sourceforge.net/), we're left with flex 2.5.4...
## Comment 5933
Date: 2006-09-22 09:18:39 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Choose the option of creating my own define YY_INPUT. I do
not think all other arch have to suffer for Debian and Gentoo.
Because the flexers are never used interactive I took the
non-interactive part of the flex 2.5.4 YY_INPUT macro as
default. Hope this does not break other arch's.
So I added the next lines to both flex input files:
/* This hack is to prevent problems with flex 2.5.33 and
lower on Debian and
* Gentoo systems. When flex.2.5.4 and higher is obligatory
this define
* may be removed
*/
ifndef YY_INPUT
define YY_INPUT(buf,result,max_size) \
if ( ((result = fread( buf, 1, max_size, yyin )) == 0) \
&& ferror( yyin ) ) \
YY_FATAL_ERROR( "input in flex scanner
failed" );
endif
## Comment 5934
Date: 2006-09-25 10:40:49 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Problem solved for this architecture! Closing!
## Comment 5935
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1562712 at http://sourceforge.net/support/tracker.php?aid=1562712
| PFtijah fails to compile with gcc 3.4.4 & gcc 4.2.0 | https://api.github.com/repos/MonetDB/MonetDB/issues/1054/comments | 0 | 2020-11-30T09:18:17Z | 2024-06-27T11:19:55Z | https://github.com/MonetDB/MonetDB/issues/1054 | 753,302,694 | 1,054 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-21 10:07:05 +0200
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2006-09-25 10:05:15 +0200
## Comment 5924
Date: 2006-09-21 10:07:05 +0200
From: @drstmane
Configured with "--enable-optimize" (the default for
automatic nightly testing),
PFtijah fails to compile with Intel's icc 9.1 on
several Linux platforms.
For details, see, e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora4/make-k.out
========
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c
-KPIC -DPIC -o .libs/lib_pftijah_la-nexi.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c(123):
error 310: old-style parameter list (anachronism)
command_tree **p_command_array, **CAS_plan_gen();
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c(1096):
error 181: argument is incompatible with corresponding
format string conversion
fscanf(rmi_file, "%d", &rmi_model);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c(1099):
error 181: argument is incompatible with corresponding
format string conversion
fscanf(rmi_file, "%d", &rmi_computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c(1120):
error 181: argument is incompatible with corresponding
format string conversion
fscanf(rmi_file, "%d", &rmi_model);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c(1123):
error 181: argument is incompatible with corresponding
format string conversion
fscanf(rmi_file, "%d", &rmi_computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c(95):
error 593: variable "query_set" was set but never used
bool query_set;
^
compilation aborted for
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi.c
(code 2)
make[5]: *** [lib_pftijah_la-nexi.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c
-KPIC -DPIC -o .libs/lib_pftijah_la-nexi_preprocessor.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c(19):
error 310: old-style parameter list (anachronism)
char *word; /* in/out: the word stemmed */
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c(24):
error 1011: missing return statement at end of
non-void function "DutchStem"
}
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c(27):
error 310: old-style parameter list (anachronism)
char *word; /* in/out: the word stemmed */
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c(32):
error 1011: missing return statement at end of
non-void function "Stem"
}
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c(38):
error 593: variable "num_term" was set but never used
int num_term;
^
compilation aborted for
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_preprocessor.c
(code 2)
make[5]: *** [lib_pftijah_la-nexi_preprocessor.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_rewriter.c
-KPIC -DPIC -o .libs/lib_pftijah_la-nexi_rewriter.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_rewriter.c(594):
error 593: variable "term_num" was set but never used
int term_num, mterm_num, iterm_num;
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_rewriter.c(594):
error 593: variable "mterm_num" was set but never used
int term_num, mterm_num, iterm_num;
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_rewriter.c(594):
error 593: variable "iterm_num" was set but never used
int term_num, mterm_num, iterm_num;
^
compilation aborted for
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_rewriter.c
(code 2)
make[5]: *** [lib_pftijah_la-nexi_rewriter.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c
-KPIC -DPIC -o .libs/lib_pftijah_la-nexi_generate_mil.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(99):
error 593: variable "new_cnt" was set but never used
int cnt, new_cnt;
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(288):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
select_root();\n", com_num);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(291):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
select_node(%s,%s);\n", com_num, p_com->argument,
txt_retr_model->e_class);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(300):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_node(%d);\n", com_num, com_nr_left,0);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(300):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_node(%d);\n", com_num, com_nr_left,0);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(303):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_node(%s,%s);\n", com_num, com_nr_left,
p_com->argument, txt_retr_model->e_class);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(303):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_node(%s,%s);\n", com_num, com_nr_left,
p_com->argument, txt_retr_model->e_class);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(312):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
select_node_vague(%s,%s,\"%s\");\n", com_num,
p_com->argument, txt_retr_model->e_class,
txt_retr_model->exp_class);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(318):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
p_select_node_t(%s,%d,%d,%d,%d,%d,%s,\"%s\",%d,%d,%f,%f,%d,%d,%d,%d,%s,%s,%d);\n",
com_num, p_com->argument, txt_retr_model->model,
txt_retr_model->or_comb, txt_retr_model->and_comb,
txt_retr_model->up_prop, txt_retr_model->down_prop,
txt_retr_model->e_class, txt_retr_model->exp_class,
txt_retr_model->stemming,
txt_retr_model->size_type, txt_retr_model->param1,
txt_retr_model->param2, txt_retr_model->param3,
txt_retr_model->prior_type, txt_retr_model->prior_size,
img_retr_model->model, img_retr_model->descriptor,
img_retr_model->attr_name, img_retr_model->computation);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(328):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
select_term(%s,%d);\n", com_num, p_com->argument,
txt_retr_model->stemming);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(336):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_term();\n", com_num, com_nr_left);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(336):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_term();\n", com_num, com_nr_left);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(339):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_term(%s,%d);\n", com_num, com_nr_left,
p_com->argument, txt_retr_model->stemming);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(339):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.select_term(%s,%d);\n", com_num, com_nr_left,
p_com->argument, txt_retr_model->stemming);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(430):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
select_image(\"%s\",\"%s\",%s);\n", com_num,
img_retr_model->descriptor, img_retr_model->attr_name,
p_com->argument);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(441):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.containing(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(441):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.containing(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(441):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.containing(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(448):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.containing();\n", com_num, com_nr_left);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(448):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.containing();\n", com_num, com_nr_left);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(461):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.contained_by(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(461):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.contained_by(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(461):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.contained_by(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(468):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.contained_by();\n", com_num, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(468):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.contained_by();\n", com_num, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(480):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d := R%d.union(R%d);\n",
com_num, com_nr_left, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(480):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d := R%d.union(R%d);\n",
com_num, com_nr_left, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(480):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d := R%d.union(R%d);\n",
com_num, com_nr_left, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(490):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.intersect(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(490):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.intersect(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(490):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.intersect(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(502):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_sum(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(502):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_sum(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(502):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_sum(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(508):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_avg(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(508):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_avg(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(508):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_avg(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(514):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(514):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(514):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(514):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(520):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(520):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(520):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(520):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(538):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_sum(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(538):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_sum(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(538):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_sum(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(544):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_avg(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(544):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_avg(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(544):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_avg(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(550):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(550):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(550):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(550):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(556):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(556):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(556):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(556):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(571):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_sum();\n", com_num, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(571):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_sum();\n", com_num, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(577):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_avg();\n", com_num, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(577):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_avg();\n", com_num, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(583):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(%d);\n", com_num,
com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(583):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(%d);\n", com_num,
com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(583):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsumd(%d);\n", com_num,
com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(589):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(%d);\n", com_num,
com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(589):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(%d);\n", com_num,
com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(589):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_contained_by_wsuma(%d);\n", com_num,
com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(603):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.prior_ls(%d);\n", com_num, com_nr_left,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(603):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.prior_ls(%d);\n", com_num, com_nr_left,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(603):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.prior_ls(%d);\n", com_num, com_nr_left,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(609):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_Bool(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(609):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_Bool(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(609):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_Bool(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(615):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_not_containing_t_Bool(R%d);\n", com_num,
com_nr_left, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(615):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_not_containing_t_Bool(R%d);\n", com_num,
com_nr_left, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(615):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_not_containing_t_Bool(R%d);\n", com_num,
com_nr_left, com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(627):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_Bool(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(627):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_Bool(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(627):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_Bool(R%d);\n", com_num, com_nr_left,
com_nr_right);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(633):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LM(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(633):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LM(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(633):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LM(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(633):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LM(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(639):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LMs(R%d, %f, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->param1,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(639):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LMs(R%d, %f, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->param1,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(639):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LMs(R%d, %f, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->param1,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(639):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_LMs(R%d, %f, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->param1,
txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(645):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_tfidf(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(645):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_tfidf(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c(645):
error 181: argument is incompatible with corresponding
format string conversion
MILPRINTF(MILOUT, "R%d :=
R%d.p_containing_t_tfidf(R%d, %d);\n", com_num,
com_nr_left, com_nr_right, txt_retr_model->size_type);
^
compilation aborted for
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/nexi_generate_mil.c
(code 4)
make[5]: *** [lib_pftijah_la-nexi_generate_mil.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
pftijah.c -KPIC -DPIC -o .libs/lib_pftijah_la-pftijah.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/pftijah.mx(2320):
error 593: variable "one_tid" was set but never used
bit one_tid = FALSE;
^
compilation aborted for pftijah.c (code 2)
make[5]: *** [lib_pftijah_la-pftijah.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
pftijah_stem.c -KPIC -DPIC -o
.libs/lib_pftijah_la-pftijah_stem.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/pftijah_stem.mx(656):
error 424: extra ";" ignored
};
^
compilation aborted for pftijah_stem.c (code 2)
make[5]: *** [lib_pftijah_la-pftijah_stem.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
pftijah_tokenize.yy.c -KPIC -DPIC -o
.libs/lib_pftijah_la-pftijah_tokenize.yy.o
lex.yy.c(1078): error 177: function "yyunput" was
declared but never referenced
static void yyunput( int c, register char *yy_bp )
^
compilation aborted for pftijah_tokenize.yy.c (code 2)
make[5]: *** [lib_pftijah_la-pftijah_tokenize.yy.lo]
Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
serialize_pftijah.c -KPIC -DPIC -o
.libs/lib_pftijah_la-serialize_pftijah.o
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(669):
error 181: argument is incompatible with corresponding
format string conversion
str += sprintf (str, "%03ldh ", elapsed /
3600000000UL);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(674):
error 181: argument is incompatible with corresponding
format string conversion
str += sprintf (str, "%02ldm ", elapsed /
60000000UL);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(679):
error 181: argument is incompatible with corresponding
format string conversion
str += sprintf (str, "%02lds ", elapsed /
1000000UL);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(684):
error 181: argument is incompatible with corresponding
format string conversion
str += sprintf (str, "%03ldms ", elapsed /
1000UL);
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(946):
error 593: variable "docBAT" was set but never used
BAT* docBAT;
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(954):
error 593: variable "start" was set but never used
long start, stop;
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(954):
error 593: variable "stop" was set but never used
long start, stop;
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(396):
error 177: function "useStrtokScanner" was declared
but never referenced
useStrtokScanner(tjCtx* tjctx, char* s)
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(420):
error 177: function "handle_sizeHint" was declared but
never referenced
handle_sizeHint(XqueryCtx* ctx, int hinted_size) {
^
/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/serialize_pftijah.mx(662):
error 177: function "timer_str" was declared but never
referenced
timer_str (long elapsed)
^
compilation aborted for serialize_pftijah.c (code 2)
make[5]: *** [lib_pftijah_la-serialize_pftijah.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
nexi.tab.c -KPIC -DPIC
-o .libs/lib_pftijah_la-nexi.tab.o
y.tab.c(1304): error 177: label "yyerrorlab" was
declared but never referenced
yyerrorlab:
^
compilation aborted for nexi.tab.c (code 2)
make[5]: *** [lib_pftijah_la-nexi.tab.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah
-I../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../runtime
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../../compiler/include
-I/export/scratch0/monet/monet.ntv.64.64.d.18954/pathfinder/modules/pftijah/../../compiler/include
-DLIBPFTIJAH -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
nexi.yy.c -KPIC -DPIC -o .libs/lib_pftijah_la-nexi.yy.o
lex.yy.c(1382): error 177: function "yyunput" was
declared but never referenced
static void yyunput( int c, register char *yy_bp )
^
compilation aborted for nexi.yy.c (code 2)
make[5]: *** [lib_pftijah_la-nexi.yy.lo] Error 1
========
## Comment 5925
Date: 2006-09-21 15:19:40 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Solved all problems I think. Will check tomorrow!
## Comment 5926
Date: 2006-09-25 10:05:15 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
No more errors in the log. Closing the bug.
## Comment 5927
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1562697 at http://sourceforge.net/support/tracker.php?aid=1562697
| PFtijah fails to compile with Intel's icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1053/comments | 0 | 2020-11-30T09:18:12Z | 2024-06-27T11:19:54Z | https://github.com/MonetDB/MonetDB/issues/1053 | 753,302,629 | 1,053 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-20 10:02:33 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-11-03 11:39:39 +0100
## Comment 5919
Date: 2006-09-20 10:02:33 +0200
From: @grobian
This is a high priority bug, since there is proof now
that on the same platform, using another compiler can
result in new warnings/errors. See for example Gentoo
compilers on our Fedora Core workstations.
As result, setting -Werror and friends is EVIL and
BREAKS COMPILATION for many users. Students
repeatedly reported compilation issues, and also Gentoo
users get errors due to these AWKWARD flags. For example:
http://bugs.gentoo.org/show_bug.cgi?id=148230
I have to fix this by hacking the configure(.in) script
not to touch the CFLAGS.
Since these flags are fine within our lab setting,
where we have access to the machines we compile
ourself, I STRONGLY suggest that CFLAG trickery is
moved to conf.bash or something, and that the MonetDB/*
configure scripts just respect the user/environment
CFLAGS. This does not only help me@gentoo, but every
user that is on Debian, Ubuntu, Mandrake, etc. such as
reported by students.
Please fix this before the next release, this is a
major issue and pain.
## Comment 5920
Date: 2006-10-18 19:05:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just quick hint for now:
you can easily switch off "-Werror" by calling configure
with "--enable-warning" --- maybe a bit counter-intuitive,
but that's how it "happened to be", i.e., "--enable-warning"
is/does the opposit of the (implicit) "--enable-error"...
Apart from that, there are IMHO very good reasons to have
-Werror at least in the development source --- it keeps
"lazy" developers from ignoring warnings that might indeed
be bugs (possibly valid C, but not working as intended).
Of course, we should consider having -Werror as default only
in the development sources, but only optional in the
released sources, e.g., by adding a switch like
--enable-Werror, which is then on for the development trunk
and off for the release branch.
Further clean-up of all the CFLAGS settings (and other
"tricks" in our configure scipts are desireable as well, but
should be done with great care and good planning --- the
current setting is to make all (known) compilers as strick
as possible by default (at least for the development trunk)
in order to prevent non-portable code as much as possible.
Moving -Werror to conf/conf.bash is IMHO no option, since
conf/conf.bash is not "mandatory" and hence cannot help to
prevent non-portable code to "sneak-in"...
(Btw, the bug reported under
http://bugs.gentoo.org/show_bug.cgi?id=148230
could have been fixed in the MonetDB source, if it had been
reported as a MonetDB bug...)
## Comment 5921
Date: 2006-11-03 10:11:49 +0100
From: @njnes
Logged In: YES
user_id=43556
We added the --enable/disable-strict flag to solve this
issue. Can this be closed now...
## Comment 5922
Date: 2006-11-03 11:39:39 +0100
From: @grobian
Logged In: YES
user_id=963970
Yes the results look very nice. Thank you very much.
## Comment 5923
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1561978 at http://sourceforge.net/support/tracker.php?aid=1561978
| BUILD: MonetDB/* configure injects EVIL CFLAGS | https://api.github.com/repos/MonetDB/MonetDB/issues/1052/comments | 0 | 2020-11-30T09:18:09Z | 2024-06-27T11:19:53Z | https://github.com/MonetDB/MonetDB/issues/1052 | 753,302,588 | 1,052 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-15 04:15:59 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2007-02-20 03:36:26 +0100
## Comment 5912
Date: 2006-09-15 16:15:59 +0200
From: Maurice van Keulen <<mvankeulen>>
The query below gives a type error: "ERROR = !type
error: can't cast type 'node?' to type 'element { item* }'
! halted in milprint_summer.c (simplifyCoreTree), line
8956
declare function xmltopxml($node as node()?)
{
typeswitch($node)
case $n as element() return <foo>{$n}</foo>
default return <foo/>
};
xmltopxml(<a/>)
## Comment 5913
Date: 2006-09-27 19:37:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
test added in
pathfinder/tests/BugTracker/Tests/type_error_with_typeswitch.SF-1559355.xq
(correct/expected output needs to be provided by hand or
approved once the bug is fixed)
## Comment 5914
Date: 2007-02-19 15:55:47 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Jens, is this something for you? Feel free to assign to somebody else.
## Comment 5915
Date: 2007-02-20 15:36:26 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Originator: NO
This is another instance of the milprint_summer-wrongly-inspects-static-type-information-and-wrongly-interprets-Core-seqcast-nodes problem and there is probably no sensible way of fixing this.
In this query, the corresponding Core tree contains the explicit information that $n should be bound to the value of $node, but should have the *static* type element() (and the typeswitch clause ensures that this assumption on the static type is always valid). This should be a compile-time information only, but milprint_summer wrongly interprets it as a real cast and complains that it cannot cast to element {}. The "fix" would be to implement `seqcast' operators as no-ops in milprint_summer---a "fix" that would stir up a hornet's nest only.
## Comment 5916
Date: 2007-04-21 19:23:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Since this has been closed with "Won't fix",
shall we still keep the failing test (to remind us),
or should we rather disable the test (to reduce the "noise" in the TestWeb)?
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora6/tests_BugTracker/type_error_with_typeswitch.SF-1559355.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora6/tests_BugTracker/type_error_with_typeswitch.SF-1559355.err.00.html
## Comment 5917
Date: 2008-06-08 16:33:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Just for the records:
Appears to work fine with ALG:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/type_error_with_typeswitch.SF-1559355.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/type_error_with_typeswitch.SF-1559355.err.00.html
## Comment 5918
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1559355 at http://sourceforge.net/support/tracker.php?aid=1559355
| XQ: Type error with typeswitch-expression | https://api.github.com/repos/MonetDB/MonetDB/issues/1051/comments | 0 | 2020-11-30T09:18:05Z | 2024-06-28T13:33:05Z | https://github.com/MonetDB/MonetDB/issues/1051 | 753,302,550 | 1,051 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-12 10:51:41 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2006-11-13 12:28:43 +0100
## Comment 5906
Date: 2006-09-12 10:51:41 +0200
From: @drstmane
After yesterday's (Monday, Sep 11 2006) checkins,
test tests/by_Peter/Tests/tst_updatestr2.milM fails
with a segfault on almost all platforms; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/tests_by_Peter/tst_updatestr2.out.00.html
(Note, test tests/by_Peter/Tests/tst_updatestr2.milM
requires test tests/by_Peter/Tests/tst_updatestr.milM
to be run first (within the same Mtest call).)
## Comment 5907
Date: 2006-09-13 14:35:19 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Hmm. Running just tst_updatestr and tst_updatestr2 is not
enough. It does crash when you run all tests in the
directory, but not if you run just these two.
## Comment 5908
Date: 2006-11-07 06:31:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
before this info gets lost: the respective checkins are/were
===================================================================
2006/09/11 - boncz: conf/MonetDB.conf.in,1.26
src/common/monet_options.mx,1.5
src/common/monet_options.py.in,1.30
- changed gdk_mem_bigsize to 256KB
mem_bigsize is the minimal size for a mmapped-heap
it is also the size above which mallocs are redirected
from the
heap towards virtuall-alloc
the reason for the change is its former function: we want
to be able
to quickly profix in XQuery from mmapped heaps.
===================================================================
2006/09/11 - boncz: src/gdk/gdk_bbp.mx,1.178
src/gdk/gdk_tm.mx,1.39
fixed bug in subcommit: heap files could get lost
===================================================================
2006/09/11 - boncz: src/monet/monet_parse.mx,1.82
- bugfix in error printing in parser (big errors would
overrflow a buffer)
===================================================================
2006/09/11 - boncz: src/gdk/gdk_storage.mx,1.113
- more specific error reporting in GDKload
===================================================================
2006/09/11 - boncz: src/modules/plain/bat.mx,1.118
- we got one corner case wrong here in CMDremap
===================================================================
2006/09/11 - sjoerd: src/mapi/clients/C/Makefile.ag,1.11
src/mapi/clients/C/MapiClient.mx,1.143
src/mapi/clients/C/dump.c,1.1
src/mapi/clients/C/mprompt.h,1.1
src/mapi/clients/C/msqldump.c,1.1
src/mapi/clients/C/msqldump.h,1.1
src/mapi/clients/C/prompt.c,1.1
src/tools/Tests/usage,1.7 src/tools/Tests/usage.bat,1.8
src/tools/Tests/usage.stable.err,1.28
Created new tool msqldump to dump the SQL database.
Added code to dump SQL functions.
Put the dump code into a new file.
Put the code to prompt for a username/password into a new file.
Removed -D/--dump option from MapiClient (but left the \D
command
there--perhaps that should be removed as well?).
===================================================================
2006/09/11 - mr-meltdown: src/modules/plain/logger.mx,1.35
gcc (GCC) 4.1.1 (Gentoo 4.1.1-r1) detected a type-pun
(this actually convinced me that release tarballs should not
have -W
-Werror!)
===================================================================
## Comment 5909
Date: 2006-11-12 12:12:43 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU.64.64.d-Fedora4/tests_by_Peter/tst_updatestr2.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests03/GNU.64.64.d-Fedora4/tests_by_Peter/tst_updatestr2.out.00.html
## Comment 5910
Date: 2006-11-13 12:28:43 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed in src/gdk/gdk_bbp.mx by Niels:
reverted part of check of Sept 11 2006. We do not backup
(not committed)
heaps over committed heaps which allready are backed up.
(fixes http://sourceforge.net/support/tracker.php?aid=1556942, Summary: MIL: test
tests/by_Peter/Tests/tst_updatestr2.milM seqfaults)
## Comment 5911
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1556942 at http://sourceforge.net/support/tracker.php?aid=1556942
| MIL: test tests/by_Peter/Tests/tst_updatestr2.milM seqfaults | https://api.github.com/repos/MonetDB/MonetDB/issues/1050/comments | 0 | 2020-11-30T09:18:02Z | 2024-06-27T11:19:51Z | https://github.com/MonetDB/MonetDB/issues/1050 | 753,302,507 | 1,050 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-11 03:21:27 +0200
From: @grobian
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-09-13 10:15:54 +0200
## Comment 5898
Date: 2006-09-11 15:21:27 +0200
From: @grobian
After some lenghty debugging session with Stefan, the
following bug appears to be in MonetDB/XQuery with
regard to shredding documents from remote URLs:
(pegasus:~) fabian% echo
'count(doc("http://www.cwi.nl/~fabian/Teaching/JackTheRipper.xml"))'
| MapiClient -lx
MAPI = monetdb@localhost:50000
QUERY =
count(doc("http://www.cwi.nl/~fabian/Teaching/JackTheRipper.xml"))
ERROR = !ERROR: interpret_params: mirror(param 1):
invalid BAT.
!ERROR: interpret_params: [startsWith](param
2): evaluation error.
!ERROR: interpret_params: uselect(param 1):
evaluation error.
!ERROR: interpret_params: +(param 2):
evaluation error.
(the error message is least to say, a bit "misleading")
The document, however, is ok, when accessed through the
local file system:
(pegasus:~) fabian% echo
'count(doc("/cwi/www/homepages/fabian/WWW/Teaching/JackTheRipper.xml"))'
| MapiClient -lx
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>1</XQueryResult>
This fails for an arbitrary document, such as RSS feeds
and the like, as noted by Ludek Cigler.
## Comment 5899
Date: 2006-09-11 15:51:22 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Works for me:
15:47:12+ echo
'count(doc("http://www.cwi.nl/~fabian/Teaching/JackTheRipper.xml"))'
| MapiClient -lx
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>1</XQueryResult>
15:48:51+
## Comment 5900
Date: 2006-09-11 19:15:50 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
I think I had some similar problems after playing with the
caching rules. Have you checked the bat("uri_lifetime")?
This bat stores the caching rules and checks whether the
prefix of the requested url is in the list. It should be
an [str,lng] bat, perhaps empty it and see what happens.
## Comment 5901
Date: 2006-09-11 19:20:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
see
sigs("pathfinder");
for MIL commands to manage the database and the document cache.
## Comment 5902
Date: 2006-09-12 08:59:34 +0200
From: @Teggy
Logged In: YES
user_id=642632
I thought I'd throw in another ''works for me, too.''
Regards,
--Teggy
## Comment 5903
Date: 2006-09-12 13:03:42 +0200
From: @grobian
Logged In: YES
user_id=963970
It appears that (at least on stable) when trying on a clean
database, the error vanishes. Still, I don't understand why
students encounter it, as they shouldn't have a possibly old
dbfarm.
## Comment 5904
Date: 2006-09-13 10:15:54 +0200
From: @grobian
Logged In: YES
user_id=963970
The student reported that removing his dbfarm solved the
problem for him too. Hence, I consider this bug to be invalid.
## Comment 5905
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1556348 at http://sourceforge.net/support/tracker.php?aid=1556348
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQuery: shredding of urls fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1049/comments | 0 | 2020-11-30T09:17:58Z | 2024-06-28T13:33:05Z | https://github.com/MonetDB/MonetDB/issues/1049 | 753,302,469 | 1,049 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-05 11:10:02 +0200
From: @grobian
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-10-26 03:59:56 +0200
## Comment 5893
Date: 2006-09-05 11:10:02 +0200
From: @grobian
On the UvA workstations, with current CVS's head
optimised Pentium4 build (CFLAGS=-march=pentium4 -O3
-pipe) execute:
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit with 32bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(sql_server);
MonetDB>sql_server_start();
MonetDB>module(pathfinder);
!WARNING: BBPdecref: range error 724
!WARNING: interpret_params: range error 724
!ERROR: Myyclean: BAT 724 OVERWRITTEN (stamp -374 != 0)
MonetDB>xquery_server_start();
MonetDB>
On the client:
% echo 1+1 | MapiClient -lxquery
MAPI = monetdb@localhost:50000
QUERY = 1+1
ERROR = !ERROR: interpret: no matching MIL operator to
'destroy_ws(int)'.
Only without SQL, XQuery will work. Also note the
corruption on the DBfarm caused by XQuery.
The students will (have to) use this combination, so a
quick fix would be nice.
## Comment 5894
Date: 2006-09-05 12:59:50 +0200
From: @grobian
Logged In: YES
user_id=963970
this also doesn't work using stable MonetDB, SQL and XQuery:
Error: ERROR: interpret: no matching MIL operator to
'destroy_ws(void)'.
(note void iso int)
## Comment 5895
Date: 2006-09-05 13:41:57 +0200
From: @grobian
Logged In: YES
user_id=963970
Intermediate solution found:
changing the order of the statements to read as follows
solves the problems:
MonetDB>module(sql_server);
MonetDB>module(pathfinder);
MonetDB>sql_server_start();
MonetDB>xquery_server_start();
## Comment 5896
Date: 2006-10-26 15:59:56 +0200
From: @grobian
Logged In: YES
user_id=963970
just keep in mind to have the order correct in
init.d/monetdb start/stop scripts.
## Comment 5897
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1552491 at http://sourceforge.net/support/tracker.php?aid=1552491
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQ: XQuery refuses to work and corrupts DBFarm with SQL | https://api.github.com/repos/MonetDB/MonetDB/issues/1048/comments | 0 | 2020-11-30T09:17:55Z | 2024-06-28T13:33:04Z | https://github.com/MonetDB/MonetDB/issues/1048 | 753,302,424 | 1,048 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-04 11:31:51 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2006-09-07 05:33:48 +0200
## Comment 5890
Date: 2006-09-04 11:31:51 +0200
From: @drstmane
Since Sat Aug 26 2006, i.e., after checkins on Fri Aug
25 2006, the following pathfinder tests seem tp produce
no output when compiled with icc 9.1 on x86_64 (FC4 &
SuSE 9.3 on Athlon64; RHEL4WS in ia64 (Itanium2) works
fine):
pathfinder/runtime/Tests/printEmptySeq.milS
pathfinder/runtime/Tests/printTypedMode.milS
pathfinder/runtime/Tests/printTypedMode-soap.milS
pathfinder/runtime/Tests/serialization.milS
see e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/ntv.64.64.d-Fedora4/runtime/printEmptySeq.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/ntv.64.64.d-Fedora4/runtime/printTypedMode.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/ntv.64.64.d-Fedora4/runtime/printTypedMode-soap.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/ntv.64.64.d-Fedora4/runtime/serialization.out.00.html
Since there where no pathfinder checkins on Fri Aug 25
2006, I guess, that the problem might be related to
MonetDB checkins on that day, which were only Sjoerd's
VALconvert related changes.
I haven't checked, yet, whether compiler optimization
(--enable-optimize) plays a role, here.
## Comment 5891
Date: 2006-09-07 17:33:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
has been fixed in CVS by Sjoerd.
## Comment 5892
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1551847 at http://sourceforge.net/support/tracker.php?aid=1551847
| PF: serialization tests produce no output with icc on x86_64 | https://api.github.com/repos/MonetDB/MonetDB/issues/1047/comments | 0 | 2020-11-30T09:17:52Z | 2024-06-27T11:19:48Z | https://github.com/MonetDB/MonetDB/issues/1047 | 753,302,388 | 1,047 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-02 04:45:40 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2006-11-07 01:41:09 +0100
## Comment 5884
Date: 2006-09-02 16:45:40 +0200
From: @grobian
Being executed on my machine:
no -python
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/Mo
netDB
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/MonetDB
/common
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/Monet
DB/gdk
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/MonetD
B/monet
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/Monet
DB/plain
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/Mone
tDB/contrib
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/M
onetDB/mapi
-I/Volumes/Scratch/monetdb/current/program-Power_Macintosh/include/M
onetDB/C -outdir . -o monetdb.py.c
/Volumes/Scratch/monetdb/five/sql/src/tools/m
onetdb.py.i
make[4]: no: Command not found
make[4]: *** [monetdb.py.c] Error 127
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I have no clue what tool that should be, and the
Makefile jungle doesn't really make me wiser either.
I will attach configure's output
## Comment 5885
Date: 2006-09-03 11:10:54 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
That's swig that couldn't be found. I'll take a look at the
configure script one of these days.
## Comment 5886
Date: 2006-09-04 10:02:01 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Did you try to compile from CVS or from a source tar ball?
## Comment 5887
Date: 2006-09-04 10:04:03 +0200
From: @grobian
Logged In: YES
user_id=963970
From CVS
## Comment 5888
Date: 2006-11-07 13:41:09 +0100
From: @grobian
Logged In: YES
user_id=963970
Have to try this again, but it's probably not relevant any
more as my setup has greatly improved now.
## Comment 5889
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1551040 at http://sourceforge.net/support/tracker.php?aid=1551040
| SQL: build fails on OSX if some tool isn't there | https://api.github.com/repos/MonetDB/MonetDB/issues/1046/comments | 0 | 2020-11-30T09:17:48Z | 2024-06-27T11:19:47Z | https://github.com/MonetDB/MonetDB/issues/1046 | 753,302,348 | 1,046 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-09-01 11:39:19 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2006-09-02 09:47:08 +0200
## Comment 5881
Date: 2006-09-01 23:39:19 +0200
From: @mlkersten
The system permits the monetdb user to manipulate the
catalog tables directly. In particular, he can drop
schemas, _tables, etc... It results into errors in the
subsequent queries, but could also result in system
crashed when you restart the server.
It is a hard area to capture in a specific test, but it
seems that some protection against malicious/
existential updates of the catalog should be avoided.
Example gdb trace of a crash after removal of _tables
and a restart of the server:
(gdb) run
Starting program: /ufs/mk/monet5/Linux/bin/mserver5
[Thread debugging using libthread_db enabled]
[New Thread 46912507150400 (LWP 18450)]
[New Thread 1082132832 (LWP 18451)]
MonetDB Server v4.99.19
Copyright (c) 1993-2006 CWI, all rights reserved
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs dynamically linked
config:/ufs/mk/monet5/Linux/etc/MonetDB5.conf
dbfarm:/ufs/mk/monet5/Linux/var/MonetDB5/dbfarm
dbname:demo
Visit http://monetdb.cwi.nl/ for further information
[New Thread 1090525536 (LWP 18452)]
>include sql;
>sql.start();
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912507150400 (LWP 18450)]
0x00002aaab7a6fe64 in schema_get_table (s=0xc735d8,
id=11029)
at
/ufs/mk/opensource/sql/src/storage/bat/bat_store.mx:1178
1178 for (n=s->tables.set->h; n; n = n->next) {
(gdb) where
0 0x00002aaab7a6fe64 in schema_get_table (s=0xc735d8,
id=11029)
at
/ufs/mk/opensource/sql/src/storage/bat/bat_store.mx:1178
1 0x00002aaab7a7c936 in load_trans (bm=Variable "bm"
is not available.
)
at
/ufs/mk/opensource/sql/src/storage/bat/bat_store.mx:1208
2 0x00002aaab7a7d90f in store_init (debug=Variable
"debug" is not available.
)
at
/ufs/mk/opensource/sql/src/storage/bat/bat_store.mx:2247
3 0x00002aaab7a5fa67 in mvc_init (debug=0, stk=0)
at /ufs/mk/opensource/sql/src/server/sql_mvc.mx:209
4 0x00002aaab7a227c2 in SQLinit (c=Variable "c" is
not available.
## Comment 5882
Date: 2006-09-02 09:47:08 +0200
From: @grobian
Logged In: YES
user_id=963970
as root user you're on your own. (monetdb/monetdb)
## Comment 5883
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1550768 at http://sourceforge.net/support/tracker.php?aid=1550768
| M5/SQL: protection against catalog drops | https://api.github.com/repos/MonetDB/MonetDB/issues/1045/comments | 0 | 2020-11-30T09:17:45Z | 2024-06-28T13:33:03Z | https://github.com/MonetDB/MonetDB/issues/1045 | 753,302,308 | 1,045 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-31 03:36:06 +0200
From: @yzchang
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-08-31 04:22:13 +0200
## Comment 5877
Date: 2006-08-31 15:36:06 +0200
From: @yzchang
Compiling MonetDB failed with the following errors:
/ufs/zhang/scratch/monet/dev/program/bin/Mx -x m
../../../../src/modules/plain/algebra.mx
../../../../src/modules/plain/algebra.mx: ./algebra.m -
created
/ufs/zhang/scratch/monet/dev/program/bin/mel
-I../../../../src/modules/plain -I../../common
-I../../../../src/modules/plain/../../common
-I../../gdk -I../../../../src/modules/plain/../../gdk
-I../../monet
-I../../../../src/modules/plain/../../monet
-proto algebra.m > algebra.proto.h
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 37,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 37,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 37,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 154,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 154,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 517,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of bte.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of wrd.
/ufs/zhang/scratch/monet/dev/program/bin/mel:
"../../../../src/modules/plain/algebra.mx", line 541,
Atom not found at "3" of wrd.
Found 37 syntax errors.
make[6]: *** [algebra.proto.h] Error 1
make[6]: Leaving directory
`/ufs/zhang/src/monet/dev/MonetDB/build/src/modules/plain'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/ufs/zhang/src/monet/dev/MonetDB/build/src/modules'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/ufs/zhang/src/monet/dev/MonetDB/build/src/modules'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/ufs/zhang/src/monet/dev/MonetDB/build/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/ufs/zhang/src/monet/dev/MonetDB/build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/ufs/zhang/src/monet/dev/MonetDB/build'
make: *** [all] Error 2
## Comment 5878
Date: 2006-08-31 15:57:32 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Did you update the buildtools?
## Comment 5879
Date: 2006-08-31 16:22:13 +0200
From: @yzchang
Logged In: YES
user_id=341633
Ok, that's it. The changes require re-install the
buildtools. I have just done this and the errors are gone.
So the bug can be closed and marked as invalid.
## Comment 5880
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1549934 at http://sourceforge.net/support/tracker.php?aid=1549934
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| MonetDB: failed to compile MonetDB | https://api.github.com/repos/MonetDB/MonetDB/issues/1044/comments | 0 | 2020-11-30T09:17:42Z | 2024-06-28T13:33:02Z | https://github.com/MonetDB/MonetDB/issues/1044 | 753,302,279 | 1,044 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-30 05:19:07 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2006-08-31 01:40:13 +0200
## Comment 5874
Date: 2006-08-30 17:19:07 +0200
From: @drstmane
After yesterday's checkins, the following pathfinder
tests fail:
tests/Music/mod/MIL/*
tests/Music/mod/XQ/*
tests/Music/opt/MIL/
tests/Music/opt/XQ/*
tests/XMark/mod/MIL/q05
tests/XMark/mod/MIL/q20
tests/XMark/mod/XQ/q05
tests/XMark/mod/XQ/q20
tests/XMark/opt/MIL/q05
tests/XMark/opt/MIL/q20
tests/XMark/opt/XQ/q05
tests/XMark/opt/XQ/q20
tests/XRpc/xmark_queries/q05
tests/XRpc/xmark_queries/q20
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/index_short.html
for details.
## Comment 5875
Date: 2006-08-31 13:40:13 +0200
From: @yzchang
Logged In: YES
user_id=341633
fixed in cvs.
## Comment 5876
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1549367 at http://sourceforge.net/support/tracker.php?aid=1549367
| PF: various tests fail after yesterday's checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/1043/comments | 0 | 2020-11-30T09:17:39Z | 2024-06-27T11:19:44Z | https://github.com/MonetDB/MonetDB/issues/1043 | 753,302,231 | 1,043 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-30 03:39:05 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-09-14 12:47:00 +0200
## Comment 5869
Date: 2006-08-30 15:39:05 +0200
From: Maurice van Keulen <<mvankeulen>>
Associated query that contains a function to translate
month-names to numbers, returns duplicate results:
<XQueryResult>
<test>
<m n="apr">04</m>
<m n="apr">04</m>
<m n="apr">04</m>
<m n="dec">12</m>
<m n="dec">12</m>
<m n="dec">12</m>
<m n="jan">01</m>
<m n="jan">01</m>
<m n="jan">01</m>
</test>
</XQueryResult>
It should have returned
<XQueryResult>
<test>
<m n="apr">04</m>
<m n="dec">12</m>
<m n="jan">01</m>
</test>
</XQueryResult>
Probably some bug in loop-lifting user-defined functions.
## Comment 5870
Date: 2006-08-30 16:48:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
test added:
pathfinder/tests/BugTracker/Tests/wrong_result_duplication.SF-1549292.*
## Comment 5871
Date: 2006-09-13 11:40:41 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This bug is triggered by an incorrect translation of an
thetajoin ('[@n=$mon]') that does not take the iterations
into account.
Added small fix to milprint_summer.c that ensures that
thetajoins in UDF functions know that they may dependent on
some outer iterations.
I will close the bug if the testweb tomorrow is still green :)
## Comment 5872
Date: 2006-09-14 12:47:00 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
testweb is still green... - so the bug is now officially
closed :)
## Comment 5873
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1549292 at http://sourceforge.net/support/tracker.php?aid=1549292
| XQuery: Wrong duplication of results | https://api.github.com/repos/MonetDB/MonetDB/issues/1042/comments | 0 | 2020-11-30T09:17:35Z | 2024-06-27T11:19:43Z | https://github.com/MonetDB/MonetDB/issues/1042 | 753,302,182 | 1,042 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-29 04:54:44 +0200
From: Jens Teubner <<teubner>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-08-29 07:33:12 +0200
## Comment 5864
Date: 2006-08-29 16:54:44 +0200
From: Jens Teubner <<teubner>>
After recent checkins (?) MonetDB no longer compiles.
After a fresh checkout of buildtools and MonetDB I get
gcc -DHAVE_CONFIG_H -I. -I../../../src/gdk -I../.. -
I../../../src/gdk -I../common -I../../../src/gdk/../
common -DLIBGDK -g -O2 -std=c99 -Wall -W -fno-strict-
aliasing -Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -D_REENTRANT -c
gdk_value.c -fPIC -DPIC -o .libs/libbat_la-gdk_value.o
../../../src/gdk/gdk_value.mx: In function
`VALconvert2':
../../../src/gdk/gdk_value.mx:218: warning: comparison
is always false due to limited range of data type
../../../src/gdk/gdk_value.mx:218: warning: comparison
is always false due to limited range of data type
../../../src/gdk/gdk_value.mx:218: warning: comparison
is always false due to limited range of data type
make[5]: *** [libbat_la-gdk_value.lo] Error 1
make[5]: Leaving directory `/home/teubner/monet/devel/
build/src/gdk'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/teubner/monet/devel/
build/src/gdk'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/teubner/monet/devel/
build/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/teubner/monet/devel/
build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/teubner/monet/devel/
build'
make: *** [all] Error 2
## Comment 5865
Date: 2006-08-29 17:33:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jens,
what kind of system are you compiling on; in particular, 32-
or 64-bit?
## Comment 5866
Date: 2006-08-29 17:37:13 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Gentoo Linux, 32bit.
$ uname -a
Linux notekemper14 2.6.17-gentoo-r7 1 Tue Aug 29 10:28:30
CEST 2006 i686 Intel(R) Pentium(R) M processor 1.70GHz GNU/
Linux
$ gcc --version
gcc (GCC) 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
[...]
## Comment 5867
Date: 2006-08-29 19:33:12 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
- make sure that SIZEOF_SSIZE_T is defined
(we need it to define SIZEOF_WRD)
- avoid unnecessary comparisons in
src/gdk/gdk_value.mx's VALconvert2()
## Comment 5868
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1548629 at http://sourceforge.net/support/tracker.php?aid=1548629
| MonetDB does not compile | https://api.github.com/repos/MonetDB/MonetDB/issues/1041/comments | 0 | 2020-11-30T09:17:31Z | 2024-06-27T11:19:42Z | https://github.com/MonetDB/MonetDB/issues/1041 | 753,302,136 | 1,041 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-28 06:17:39 +0200
From: @Teggy
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-12-14 05:52:55 +0100
## Comment 5857
Date: 2006-08-28 18:17:39 +0200
From: @Teggy
Hi all,
compiled with the algebraic back-end, the query
element { "a" } { "42" }
fails with the following message during evaluation
(similarly for attribute constructors with computed
QNames):
ERROR: interpret: no matching MIL operator to
'leftfetchjoin(BAT[oid,str], BAT[oid,str])'.
MAYBE YOU MEAN:
leftfetchjoin(BAT[any::1,any::2],
BAT[any::2,any::3]) : BAT[any::1,any::3]
leftfetchjoin(any::1, BAT[any::1,any::2]) : any::2
leftfetchjoin(oid, any::1) : any::1
leftfetchjoin(BAT[void,oid], any::1) : any::1
leftfetchjoin(BAT[oid,oid], any::1) :
BAT[oid,any::1]
ERROR: interpret_params: [+](param 1): evaluation error.
ERROR: interpret_params: [+](param 1): evaluation error.
Cheers,
--Teggy
## Comment 5858
Date: 2006-09-12 18:42:24 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
It seems that the line 6051 in runtime/pf_support.mx
var missing :=
local.select(str(nil),str(nil)).kdiff(propIDs.tmark(0@0));
is incorrect.
Peter could you have a look whether a '.mirror()' in the end
is the correct solution.
## Comment 5859
Date: 2006-10-29 01:33:38 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Hi Jan,
sorry it took me so long to see this, but now that I look
into the code, this line has disappeared.
so, is this still al problem?
## Comment 5860
Date: 2006-10-29 09:27:35 +0100
From: @drstmane
Logged In: YES
user_id=572415
a simple test tells us:
$ echo 'element { "a" } { "42" }' | pf -A | Mserver
--dbinit='module(pathfinder);' --set monet_prompt=''
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!ERROR: interpret: unknown variable 'pref'.
!ERROR: interpret_params: [+](param 1): evaluation error.
!ERROR: interpret_params: [+](param 1): evaluation error.
!ERROR: interpret_params: [+](param 1): evaluation error.
!ERROR: interpret_params: [+](param 1): evaluation error.
hence, yes, it's still a problem, though possibly different
from the originally reported one.
(cetero censeo:
tests to monitor bug reports should be added to CVS; as
agreed, it's the responsibility of the developer/assignee
that fixes the bug to ensure that a proper test is in CVS
before the bug report is closed; the user/submitter may help
with designing a adding a test)
## Comment 5861
Date: 2006-11-05 18:33:50 +0100
From: @drstmane
Logged In: YES
user_id=572415
added tests in
pathfinder/tests/BugTracker/Tests/constructor_with_computed_QName.SF-1548043.{mps,alg}.*
milprint_summer (mps) version works fine
algebra (alg) version still fails, now with
!WARNING: BBPincref: range error 606348325
!ERROR: fetch(4371482138378311) illegal BAT at position 76.
!ERROR: CMDfetchConvert: operation failed.
!ERROR: interpret_params: find(param 1): evaluation error.
!ERROR: interpret_params: insert(param 1): evaluation error.
!ERROR: interpret_params: outerjoin(param 2): evaluation error.
!ERROR: interpret_params: tmark(param 1): evaluation error.
## Comment 5862
Date: 2006-12-14 17:52:55 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
fixed
## Comment 5863
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1548043 at http://sourceforge.net/support/tracker.php?aid=1548043
| PF/algebra: elem/attr constructor with computed QName fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1040/comments | 0 | 2020-11-30T09:17:28Z | 2024-06-27T11:19:41Z | https://github.com/MonetDB/MonetDB/issues/1040 | 753,302,088 | 1,040 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-22 02:25:09 +0200
From: @drstmane
To: Torsten Grust <<teggy>>
Version: -- development
Last updated: 2006-08-22 04:47:03 +0200
## Comment 5854
Date: 2006-08-22 14:25:09 +0200
From: @drstmane
After yesterday's checkins, XMark queries 8, 10, 11,
12, 20 trigger the following assertion in algebra version:
looking for att: item2, ty: 0x80
environment looks like:
att: iter1, type: 0x1, mvar->name: a0021
att: item2, type: 0x4, mvar->name: a0018
att: item1, type: 0x2, mvar->name: a0007
pf:
/var/tmp/monet.GNU.64.64.d.24503/pathfinder/compiler/mil/milgen.brg:461:
env_mvar: Assertion `0' failed.
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q08.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q10.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q11.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q20.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/compiler/pf-A_XMark.err.00.html
## Comment 5855
Date: 2006-08-22 16:47:03 +0200
From: @Teggy
Logged In: YES
user_id=642632
OK, here is the ''real fix'' for the text node construction
problem.
We now closely follow the XQuery Formal semantics:
(1) apply fn:data(),
(2) apply fs:item-sequence-to-untypedAtomic(),
(3) cast to xs:string?).
Reverted the associated change in the code generator (the
text node constructor accepts an item column of type
string/aat_str again).
## Comment 5856
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1544531 at http://sourceforge.net/support/tracker.php?aid=1544531
| PF/algebra: assertion fails in compiler/mil/milgen.brg | https://api.github.com/repos/MonetDB/MonetDB/issues/1039/comments | 0 | 2020-11-30T09:17:26Z | 2024-06-27T11:19:40Z | https://github.com/MonetDB/MonetDB/issues/1039 | 753,302,062 | 1,039 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-21 05:16:32 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2006-12-17 04:59:59 +0100
## Comment 5846
Date: 2006-08-21 17:16:32 +0200
From: @drstmane
Before this information gets lost:
The folloing pathfinder tests fail since Tuesday Aug 15
2006, i.e., after checkins on Monday Aug 14 2006:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.s-Fedora4/tests_BugDay_2005-10-06_0.9.3/shred_at_depth_258.SF-1174747.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/Entities.SF-1185932.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/empty.SF-1331808.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/SCJ_with_void_void_BATs.SF-1400473.out.00.html
## Comment 5847
Date: 2006-09-21 18:19:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.s-Fedora4/tests_BugDay_2005-10-06_0.9.3/shred_at_depth_258.SF-1174747.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/empty.SF-1331808.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/SCJ_with_void_void_BATs.SF-1400473.out.00.html
have been fixed with the introduction of the "new updates" code.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/Entities.SF-1185932.out.00.html
is still failing.
## Comment 5848
Date: 2006-11-12 12:11:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
for the test results with the latest "Stable" release branch
(via `make check` with debugmask 10) see
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/Entities.SF-1185932.out.00.html
for the test results with the latest "Current" development
trunk (via `Mtest.py -r -d0` with debugmask 0) see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/Entities.SF-1185932.out.00.html
## Comment 5849
Date: 2006-11-13 12:43:00 +0100
From: @drstmane
Logged In: YES
user_id=572415
see also BUG #1185932 "XML: Entities" at
http://sourceforge.net/tracker/index.php?func=detail&aid=1185932&group_id=56967&atid=482468
## Comment 5850
Date: 2006-12-02 01:15:17 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
two of these tests work again correctly
still failing:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/Entities.SF-1185932.out.00.html
not checked:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/SCJ_with_void_void_BATs.SF-1400473.out.00.html
## Comment 5851
Date: 2006-12-08 11:28:26 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/SCJ_with_void_void_BATs.SF-1400473.out.00.html
has been fixed some time ago (see my comment of 2006-09-21 18:19).
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-10-06_0.9.3/Entities.SF-1185932.out.00.html
is related to
http://sourceforge.net/tracker/index.php?func=detail&aid=1185932&group_id=56967&atid=482468
(see my comment of 2006-11-13 12:43).
## Comment 5852
Date: 2006-12-17 16:59:59 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
issues are fixed now
## Comment 5853
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1544002 at http://sourceforge.net/support/tracker.php?aid=1544002
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: several tests fail after recent checkins | https://api.github.com/repos/MonetDB/MonetDB/issues/1038/comments | 0 | 2020-11-30T09:17:23Z | 2024-06-27T11:19:39Z | https://github.com/MonetDB/MonetDB/issues/1038 | 753,302,025 | 1,038 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-21 05:12:12 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2006-08-24 01:38:19 +0200
## Comment 5842
Date: 2006-08-21 17:12:12 +0200
From: @drstmane
Before this information gets lost:
Test tests/XRpc/basic_queries/Tests/add_int.xq fails
since Thursday Aug 10 2006, i.e., after checkins on
Wednesday Aug 09 2006; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XRpc_basic_queries/add_int.out.00.html
## Comment 5843
Date: 2006-08-22 20:54:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jennie,
it was actually you who changed this test on Wednesday Aug
09 2006, without changing the stable output; hence, could
you please check, whether the stable output is still correct
(i.e., the test does indeed produce wrong output), or
whether the currect output is correct for the modified test,
and hence should be approved as stable output?
Thanks in advance!
## Comment 5844
Date: 2006-08-24 13:38:19 +0200
From: @yzchang
Logged In: YES
user_id=341633
Stefan,
Thanks for reminding me this. I did not notice that the
approved stable output was not committed together with the
modified test.
I have just committed the correct stable output.
## Comment 5845
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1543997 at http://sourceforge.net/support/tracker.php?aid=1543997
| PF/XRpc: tests/XRpc/basic_queries/Tests/add_int.xq fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1037/comments | 0 | 2020-11-30T09:17:20Z | 2024-06-27T11:19:38Z | https://github.com/MonetDB/MonetDB/issues/1037 | 753,301,984 | 1,037 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-21 01:13:56 +0200
From: @Teggy
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-12-18 10:18:42 +0100
## Comment 5835
Date: 2006-08-21 13:13:56 +0200
From: @Teggy
Hi all,
when translated with the algebraic compiler, the query
for $c in (1,2)
return
(<foo/>, "a", "b", "c", "d")
generates the following error during execution:
ERROR: merged_union: tail of second BAT must be sorted.
ERROR: CMDmerged_union: operation failed.
Running the MonetDB server with -d10 makes the error go
away and the query returns the correct result.
[Note that the very similar query (note the missing "d"
in the sequence) runs just fine with either -d setting:
for $c in (1,2)
return
(<foo/>, "a", "b", "c")
]
Cheers,
--Teggy
## Comment 5836
Date: 2006-11-05 18:22:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
added tests in
pathfinder/tests/BugTracker/Tests/item_sequence_creation.SF-1543871{a,b}.{mps,alg}{,0}.*
milprint_summer (mps) version works fine
algebra (alg) version fails as reported with debugmask 0, only
## Comment 5837
Date: 2006-12-17 17:13:23 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
this is MonetDB property trouble
in the translation of the example query the bat a0010 (second param to merge union) causes the error to be raised, because MonetDB does not have knowledge of the sorting of this column (merged union requires this).
a0010 was generated in a CTrefine (i.e. multi-column ordering) code block that derives an oid ordering in a table (on three columns). Then, it joins back to the first column, that becomes a0010. As this is the major ordering column, it must be ordered. However, the leftjoin() that does the joining back, has now way of knowing that (other than a runtime check which may be costly).
Thus, I advise in the code generator, when joining back the major ordering column, to insert an
assert_order()
call. This is a way the application can tell MonetDB about ordering knowledge (make sure not to make mistakes, though).
there is
## Comment 5838
Date: 2006-12-18 09:58:37 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This one already works in the head. I however think that propagating single changes for the algebra version to the stable branch is not needed as it won't be announced in the next release anyway.
## Comment 5839
Date: 2006-12-18 11:09:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Gents,
this bug report has ust been closed, although two of the respective tests (still) fail in the XQuery_0-14 release branch:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/item_sequence_creation.SF-1543871a.alg0.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugTracker/item_sequence_creation.SF-1543871b.alg0.out.00.html
while they indeed seems to work fine in the development trunk:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_BugTracker/item_sequence_creation.SF-1543871a.alg0.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests03/GNU.64.64.d-Fedora4/tests_BugTracker/item_sequence_creation.SF-1543871b.alg0.out.00.html
The tests had been added before the branch was forked-off, hence, they are in the branch, although the bug report refers to the Head, which was correct by the time the bug report was submitted.
My question is now, whether there are any plans to back-port the fixes to the XQuery_0-14 release branch?
If not, the two failing tests should be disabled in the release branch, only.
Just let me know.
Thanks!
## Comment 5840
Date: 2006-12-18 11:34:54 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hi Stefan,
As there is apparently no interest (yet) for stable algebra releases, I'd propose to indeed disregard algebra tests in the release for now. It means that algebra "users" (e.g. UvA, Konstanz) are supposed to follow the HEAD.
Peter
## Comment 5841
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1543871 at http://sourceforge.net/support/tracker.php?aid=1543871
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF/algebra: item sequence creation problem | https://api.github.com/repos/MonetDB/MonetDB/issues/1036/comments | 0 | 2020-11-30T09:17:16Z | 2024-06-27T11:19:37Z | https://github.com/MonetDB/MonetDB/issues/1036 | 753,301,933 | 1,036 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-19 10:04:31 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2006-09-10 11:32:44 +0200
## Comment 5831
Date: 2006-08-19 22:04:31 +0200
From: @mlkersten
Consider the following statements
create table t (id int);
create table s (id varchar(23));
select * from t union select * from s;
we don't get a type error. Instead, the code
produced attempts to coerce the varchar to an int
using the underlying cast operations.
Is this legal according to the standard?
create table f( id float);
create table b( id boolean);
select * from f union select * from b;
produces a casting error.
Besides, the result of these queries is different
on M4 and M5.
## Comment 5832
Date: 2006-08-20 15:08:51 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just out of pure curiosity (as far as I'm concerned; for
bugfixers such more detailed/precise information might even
help their debugging efforts):
What are the differences between M4 and M5?
Since you say both qureis do/try a coercion and fail, are it
"just" different error messages?
## Comment 5833
Date: 2006-09-10 11:32:44 +0200
From: @njnes
Logged In: YES
user_id=43556
SQL has more restrictive rules for coersion of union (and
other set operators). These are now enforced.
## Comment 5834
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1543216 at http://sourceforge.net/support/tracker.php?aid=1543216
| SQL: type checking unions | https://api.github.com/repos/MonetDB/MonetDB/issues/1035/comments | 0 | 2020-11-30T09:17:13Z | 2024-06-27T11:19:36Z | https://github.com/MonetDB/MonetDB/issues/1035 | 753,301,889 | 1,035 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-18 02:24:12 +0200
From: Arne D Halvorsen <<arne_d_h>>
To: @njnes
Version: -- development
Last updated: 2006-09-10 11:38:43 +0200
## Comment 5828
Date: 2006-08-18 14:24:12 +0200
From: Arne D Halvorsen <<arne_d_h>>
I am trying to create a sequence, based on what I could
find in the sql-2.12.0 download.
The command fails as follows:
MAPI = monetdb@localhost:50000
QUERY = CREATE SEQUENCE "test_seq" AS INTEGER;
ERROR = !ERROR: mvc_sql_wrap: operation failed.
MAPI = monetdb@localhost:50000
Variations in uppercase/lowercase, quoting/unquoting
test_seq, INTEGER or INT have been tried.
I am running this on Windows XP, having installed with
MonetDB-Installer-4.12.0.msi
## Comment 5829
Date: 2006-09-10 11:38:43 +0200
From: @njnes
Logged In: YES
user_id=43556
this bug doesn't exist on 4.13.1/2.13.1 (development line).
Also a sequence test is part of the test set.
## Comment 5830
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1542583 at http://sourceforge.net/support/tracker.php?aid=1542583
| sequence creation fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1034/comments | 0 | 2020-11-30T09:17:10Z | 2024-06-28T13:33:02Z | https://github.com/MonetDB/MonetDB/issues/1034 | 753,301,845 | 1,034 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-18 11:23:53 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-08-18 12:58:21 +0200
## Comment 5824
Date: 2006-08-18 11:23:53 +0200
From: @drstmane
since recent changes in PF's parser, tests
compiler/parser/Tests/good-003.xq
compiler/parser/Tests/good-015.xq
compiler/semantics/tests/normalize/Tests/good-003.xq
compiler/semantics/tests/normalize/Tests/good-015.xq
compiler/semantics/tests/varscope/Tests/good-003.xq
fail with
parse error: at ...: only XQueries in UTF-8 encoding
are supported, not in 'iso-8859-15' encoding
In case this behaviour is a bug, please fix it.
In case this behaviour is intended, please approve the
new output.
In fact, these seem to be the only tests that test the
parsing of the `encoding' keyword; hence, I'd suggest
to change these "good" tests to use the supported
`encoding "UTF-8"' and add the respective "bad"
siblings that use the unsupported `encoding "iso-8859-15"'.
[PS: I could help, once I not what the desired/intended
behaviour in case of `encoding "iso-8859-15"' is ...]
## Comment 5825
Date: 2006-08-18 11:55:44 +0200
From: @peterboncz
Logged In: YES
user_id=591107
I think these errors are OK. If the tests are functionally
useful, I'd suggest changing the encoding in the test,
otherwise approve the current input.
TUM should actually check whether PF truely supports UTF-8.
Not much needs to be done for this, but one may opt to
detect invalid UTF-8 strings and flag their use.
As far as XML data is concerned, we instruct libxml2 during
shredding to *deliver* all strings it reads in XML as UTF-8.
Serialization is UTF-8 only.
Changing this focus on UTF-8 at this stage is near
impossible, as our backend MonetDB only supports UTF-8. This
choice is core to its I18N strategy, originally developed by
Data Distilleries.
BTW the MonetDB str data type also works with ASCII (i.e.
only 128 codes), as this is a proper sub-set of UTF-8.
MonetDB does *not* work with iso-8859-15 or other encodings.
For instance, its string operations (e.g. substring) go
astray when encountering byte-values >= 128.
UTF-8 is great. It gives full Unicode support, and is by far
the most oftened encountered formatting of XML. It is easy
to support for systems that originally only thought about
ASCII. It works on top of zero-terminated character arrays
in C and all C-level string operations still work correctly
(e.g. strcmp) though one must always bear in mind that byte
positions in strings are not the same as character positions.
## Comment 5826
Date: 2006-08-18 12:58:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
"good" tests succeed with `encoding "UTF-8"'.
added `compiler/parser/Tests/bad-013' to trigger expected
error with `encoding "iso-8859-15"'.
## Comment 5827
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1542504 at http://sourceforge.net/support/tracker.php?aid=1542504
| PF: encoding 'iso-8859-15' no longer supported? | https://api.github.com/repos/MonetDB/MonetDB/issues/1033/comments | 0 | 2020-11-30T09:17:06Z | 2024-06-27T11:19:34Z | https://github.com/MonetDB/MonetDB/issues/1033 | 753,301,814 | 1,033 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-15 02:46:37 +0200
From: @sjoerdmullender
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2006-08-16 10:52:26 +0200
## Comment 5819
Date: 2006-08-15 14:46:37 +0200
From: @sjoerdmullender
I'm not sure this is a bug. It depends on what the
standard says, but I have no idea where to start looking.
XMark query 12 has the clause
where $p/profile/@income > 50000
In (one version of) the 110MB XMark document there is a
person with an income of 50000.48. This person is not
considered by Pathfinder, presumably because the income
is rounded or truncated to an integer before doing the
comparison, and then it is not greater than 50000. If
the query is changed to say
where $p/profile/@income > 50000.0
the person is considered and part of the result.
## Comment 5820
Date: 2006-08-16 10:52:26 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
This behavior is correct.
The specs say "The normalization rule for a general
comparison expression first atomizes each argument by
applying fn:data and then applies the existentially
quantified some expression to each sequence. The internal
function fs:convert-operand is applied to each pair of
atomic values. If the first argument to this function has
type xdt:untypedAtomic, then the first argument is cast to
type of the second argument."
Second argument here is of type integer. Hence, the first
argument is cast to an integer, with the observed effect.
## Comment 5821
Date: 2006-08-16 15:00:02 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Then another discrepancy that may or may not have the same
answer. What conversions take place in the clause
where $p/profile/@income > 5000 * exactly-one($i/text())
when the income attribute has the value "91891.75" and the
content of $i is "18.67". Note that 5000 * 18 = 90000 <
91891.75 and 5000 * 18.67 = 93350 > 91891.75.
Since the content of $i is also of unknown type, why should
it be converted to decimal and then multiplied by an int
instead of just being converted to int and working with ints
only?
## Comment 5822
Date: 2006-08-16 15:20:28 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
So you are experiencing now why it takes more than a couple
of days to develop a compliant XQuery engine...
What you observe is what the specs say (http://www.w3.org/
TR/2005/CR-xquery-semantics-20051103/sec_arithmetic): "If
the first argument to this function has type
xdt:untypedAtomic, then the first argument is cast to a
double, otherwise it is returned unchanged."
## Comment 5823
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1540605 at http://sourceforge.net/support/tracker.php?aid=1540605
| PF: improper int comparison? | https://api.github.com/repos/MonetDB/MonetDB/issues/1032/comments | 0 | 2020-11-30T09:17:03Z | 2024-06-28T13:33:01Z | https://github.com/MonetDB/MonetDB/issues/1032 | 753,301,762 | 1,032 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-15 12:28:18 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-08-15 12:48:50 +0200
## Comment 5815
Date: 2006-08-15 12:28:18 +0200
From: @drstmane
After last night's checkins, SQL fails to compile both
with gcc and with icc:
(see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.GNU.64.64.d-Fedora4/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.ntv.64.64.d-Fedora4/make-k.out
)
========
gcc -m64 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat
-I../../..
-I/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat
-I..
-I/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/..
-I../../include
-I/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/../../include
-I../../common
-I/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/../../common
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/common
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/gdk
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/monet
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/plain
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/contrib
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/mapi
-I/var/tmp/monet.GNU.64.64.d.8521/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/C
-DLIBBATSTORE -O2 -std=c99
-Wall -W -O6 -fomit-frame-pointer -finline-functions
-falign-loops=4 -falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-sign-compare -c bat_store.c -fPIC -DPIC -o
.libs/libbatstore_la-bat_store.o
/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/bat_store.mx:68:
error: invalid initializer
/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/bat_store.mx:
In function 'store_init':
/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/bat_store.mx:2230:
error: implicit declaration of function 'MT_create_lock'
/var/tmp/monet.GNU.64.64.d.8521/sql/src/storage/bat/bat_store.mx:2230:
error: incompatible types in assignment
make[7]: *** [libbatstore_la-bat_store.lo] Error 1
========
========
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat
-I../../..
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat
-I..
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat/..
-I../../include
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat/../../include
-I../../common
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat/../../common
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.8521/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-DLIBBATSTORE -we140
-wd1418 -c99 -Wall -w2 -mp1 -O3 -restrict -unroll -tpp7
-axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
bat_store.c -KPIC -DPIC -o
.libs/libbatstore_la-bat_store.o
/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat/bat_store.mx(68):
error: a value of type "long" cannot be used to
initialize an entity of type "MT_Lock"
static MT_Lock bs_lock = NULL;
^
/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat/bat_store.mx(2230):
error 266: function declared implicitly
bs_lock = MT_create_lock();
^
/export/scratch0/monet/monet.ntv.64.64.d.8521/sql/src/storage/bat/bat_store.mx(2230):
error: a value of type "int" cannot be assigned to an
entity of type "MT_Lock"
bs_lock = MT_create_lock();
^
compilation aborted for bat_store.c (code 2)
make[7]: *** [libbatstore_la-bat_store.lo] Error 1
========
## Comment 5816
Date: 2006-08-15 12:34:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Peter's checkin message actually contained some hint that
should help to fix this:
========
Removed a relic of SGI times when we had to do multi-threading
with processes and shared memory. Now we use pthreads
on all platforms.
The relic forced us to allocate a pool of locks in advance.
this automatically lead to a maximum on the number of locks.
That is undesirable sometimes (when this number is a run-time
phenomenon, and data/query dependent).
Instead of allocating them with GDKmalloc on-the-fly, we
just can have the lock,cond,sema objects declared on the stack.
Thus, we just need to initialize them.
the main change is that instead of doing:
MT_Lock l;
MT_Cond c;
MT_Sema s;
l = MT_create_lock(l)
c = MT_create_cond(c)
s = MT_create_sema(s)
we now have to write:
MT_Lock l;
MT_Cond c;
MT_Sema s;
MT_init_lock(l)
MT_init_cond(c)
MT_init_sema(s,0)
All other code remains the same.
M5 will have to port the changes in modules
- lock, enum, tcpip, alarm, qt, salgebra
========
## Comment 5817
Date: 2006-08-15 12:48:50 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I fixed this.
## Comment 5818
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1540527 at http://sourceforge.net/support/tracker.php?aid=1540527
| SQL failes to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/1031/comments | 0 | 2020-11-30T09:17:00Z | 2024-06-27T11:19:32Z | https://github.com/MonetDB/MonetDB/issues/1031 | 753,301,724 | 1,031 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-15 11:21:31 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-08-17 10:31:09 +0200
## Comment 5812
Date: 2006-08-15 11:21:31 +0200
From: @drstmane
After last night's checkins, MonetDB fails to compile
on Darwin:
(see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-Darwin8.6.0/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.32.32.d-Darwin8.7.0/make-k.out
)
gcc -m32 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk
-I../..
-I/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk
-I../common
-I/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk/../common
-DLIBGDK -O2 -std=c99 -Wall -W -O6 -fomit-frame-pointer
-finline-functions
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -D_REENTRANT -c gdk_scanselect.c
-fno-common -DPIC -o .libs/libbat_la-gdk_scanselect.o
In file included from gdk.h:93,
from
/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk/gdk_scanselect.mx:314:
gdk_system.h: In function 'pthread_sema_init':
gdk_system.h:141: error: storage class specified for
parameter 'pthread_sema_destroy'
gdk_system.h:141: error: parse error before 'extern'
gdk_system.h:168: error: storage class specified for
parameter 'MT_Cond'
cc1: warnings being treated as errors
In file included from gdk.h:94,
from
/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk/gdk_scanselect.mx:314:
gdk_posix.h:79: warning: empty declaration
gdk_posix.h:87: error: storage class specified for
parameter 'MT_mallinfo'
gdk_posix.h:95: error: storage class specified for
parameter 'MT_lockf'
gdk_posix.h:96: error: storage class specified for
parameter 'MT_sleep_ms'
In file included from gdk.h:94,
from
/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk/gdk_scanselect.mx:314:
gdk_posix.h:177: error: storage class specified for
parameter 'MT_heapbase'
gdk_posix.h:178: error: storage class specified for
parameter 'MT_heapcur'
gdk_posix.h:180: error: storage class specified for
parameter 'MT_init_posix'
gdk_posix.h:181: error: storage class specified for
parameter 'MT_getrss'
gdk_posix.h:183: error: storage class specified for
parameter 'MT_mmap'
gdk_posix.h:184: error: storage class specified for
parameter 'MT_munmap'
gdk_posix.h:185: error: storage class specified for
parameter 'MT_msync'
gdk_posix.h:186: error: storage class specified for
parameter 'MT_madvise'
gdk_posix.h:188: error: storage class specified for
parameter 'MT_mmap_trim'
gdk_posix.h:189: error: storage class specified for
parameter 'MT_mmap_pin'
gdk_posix.h:190: error: storage class specified for
parameter 'MT_mmap_unpin'
gdk_posix.h:192: error: storage class specified for
parameter 'MT_vmalloc'
gdk_posix.h:193: error: storage class specified for
parameter 'MT_vmfree'
gdk_posix.h:194: error: storage class specified for
parameter 'MT_vmrealloc'
gdk_posix.h:195: error: storage class specified for
parameter 'MT_path_absolute'
gdk_posix.h:257: error: storage class specified for
parameter 'win_errno'
In file included from gdk.h:95,
from
/var/tmp/monet.GNU.32.32.d.8521/MonetDB/src/gdk/gdk_scanselect.mx:314:
../common/stream.h:56: error: storage class specified
for parameter 'stream'
../common/stream.h:59: error: storage class specified
for parameter 'stream_init'
../common/stream.h:66: error: parse error before '*' token
../common/stream.h:66: error: storage class specified
for parameter 'stream_readSht'
../common/stream.h:67: error: parse error before '*' token
../common/stream.h:67: error: storage class specified
for parameter 'stream_writeSht'
../common/stream.h:68: error: parse error before '*' token
../common/stream.h:68: error: storage class specified
for parameter 'stream_readInt'
../common/stream.h:69: error: parse error before '*' token
../common/stream.h:69: error: storage class specified
for parameter 'stream_writeInt'
../common/stream.h:70: error: parse error before '*' token
../common/stream.h:70: error: storage class specified
for parameter 'stream_readLng'
../common/stream.h:71: error: parse error before '*' token
../common/stream.h:71: error: storage class specified
for parameter 'stream_writeLng'
../common/stream.h:73: error: parse error before '*' token
../common/stream.h:73: error: storage class specified
for parameter 'stream_readShtArray'
../common/stream.h:74: error: parse error before '*' token
../common/stream.h:74: error: storage class specified
for parameter 'stream_writeShtArray'
../common/stream.h:75: error: parse error before '*' token
../common/stream.h:75: error: storage class specified
for parameter 'stream_readIntArray'
../common/stream.h:76: error: parse error before '*' token
../common/stream.h:76: error: storage class specified
for parameter 'stream_writeIntArray'
../common/stream.h:77: error: parse error before '*' token
../common/stream.h:77: error: storage class specified
for parameter 'stream_readLngArray'
../common/stream.h:78: error: parse error before '*' token
../common/stream.h:78: error: storage class specified
for parameter 'stream_writeLngArray'
../common/stream.h:79: error: parse error before '*' token
../common/stream.h:79: error: storage class specified
for parameter 'stream_printf'
../common/stream.h:80: error: parse error before '*' token
../common/stream.h:80: error: storage class specified
for parameter 'stream_read'
../common/stream.h:81: error: parse error before '*' token
../common/stream.h:81: error: storage class specified
for parameter 'stream_readline'
../common/stream.h:82: error: parse error before '*' token
../common/stream.h:82: error: storage class specified
for parameter 'stream_write'
../common/stream.h:83: error: parse error before '*' token
../common/stream.h:83: error: storage class specified
for parameter 'stream_close'
../common/stream.h:84: error: parse error before '*' token
../common/stream.h:84: error: storage class specified
for parameter 'stream_destroy'
../common/stream.h:85: error: parse error before '*' token
../common/stream.h:85: error: storage class specified
for parameter 'stream_error'
../common/stream.h:86: error: parse error before '*' token
../common/stream.h:86: error: storage class specified
for parameter 'stream_flush'
../common/stream.h:87: error: parse error before '*' token
../common/stream.h:87: error: storage class specified
for parameter 'stream_fsync'
../common/stream.h:88: error: parse error before '*' token
../common/stream.h:88: error: storage class specified
for parameter 'stream_name'
../common/stream.h:89: error: parse error before '*' token
../common/stream.h:89: error: storage class specified
for parameter 'stream_errnr'
../common/stream.h:90: error: parse error before '*' token
../common/stream.h:90: error: storage class specified
for parameter 'stream_type'
../common/stream.h:91: error: parse error before '*' token
../common/stream.h:91: error: storage class specified
for parameter 'stream_byteorder'
../common/stream.h:92: warning: type defaults to 'int'
in declaration of 'stream'
../common/stream.h:92: error: storage class specified
for parameter 'stream'
../common/stream.h:92: error: conflicting types for
'stream'
../common/stream.h:56: error: previous definition of
'stream' was here
../common/stream.h:92: error: parse error before '*' token
../common/stream.h:92: error: old-style parameter
declarations in prototyped function definition
[...]
make[5]: *** [libbat_la-gdk_scanselect.lo] Error 1
## Comment 5813
Date: 2006-08-17 10:31:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by added missing ";" to prototype declarations an not
declaring exported functions "static" in src/gdk/gdk_system.mx .
## Comment 5814
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1540494 at http://sourceforge.net/support/tracker.php?aid=1540494
| MonetDB fails to compile on Darwin | https://api.github.com/repos/MonetDB/MonetDB/issues/1030/comments | 0 | 2020-11-30T09:16:56Z | 2024-06-27T11:19:31Z | https://github.com/MonetDB/MonetDB/issues/1030 | 753,301,675 | 1,030 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-14 04:35:55 +0200
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2006-08-14 04:58:25 +0200
## Comment 5809
Date: 2006-08-14 16:35:55 +0200
From: @sjoerdmullender
In the following code the seqbase of the result of the
multiplex is not set when it should:
var a :=
new(oid,oid).insert(0@0,0@0).insert(0@0,1@0).insert(1@0,1@0);
a.delete(0@0,1@0);
a := a.sort();
var b :=
new(void,str).seqbase(0@0).append("b").append("b");
var bb := a.join(b);
var aa := a.project("a");
aa.print();
bb.print();
[+](aa,bb).print();
The problem is that both operands are aligned and
marked sorted, but only the second one is marked dense.
A fix has been prepared, but I need a place for the
test script.
## Comment 5810
Date: 2006-08-14 16:58:25 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
## Comment 5811
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1540019 at http://sourceforge.net/support/tracker.php?aid=1540019
| multiplex sometimes looses seqbase | https://api.github.com/repos/MonetDB/MonetDB/issues/1029/comments | 0 | 2020-11-30T09:16:53Z | 2024-06-27T11:19:30Z | https://github.com/MonetDB/MonetDB/issues/1029 | 753,301,629 | 1,029 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-13 09:49:53 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-08-22 08:41:21 +0200
## Comment 5804
Date: 2006-08-13 21:49:53 +0200
From: Jan Rittinger <<jan.rittinger>>
A check is missing that prohibits the usage of flex
2.5.31. The compilation of Mel does not work with it
(on a Suse 10.1 version).
Only pathfinder which requires MonetDB (and thus the
buildtools) contains such a check.
## Comment 5805
Date: 2006-08-14 16:28:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just out of curiosity and for the records:
What exactly is the problem when attempting to compile MEL
with flex 2.5.31?
## Comment 5806
Date: 2006-08-15 11:22:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
I'll take care of this one.
## Comment 5807
Date: 2006-08-22 20:41:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Since we already refuse flex 2.5.31 for Pathfinder,
we now refuse it for all MonetDB code;
please install/use flex 2.5.4 or flex 2.5.33 instead.
## Comment 5808
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1539660 at http://sourceforge.net/support/tracker.php?aid=1539660
| Mel does not compile with flex 2.5.31 | https://api.github.com/repos/MonetDB/MonetDB/issues/1028/comments | 0 | 2020-11-30T09:16:50Z | 2024-06-27T11:19:29Z | https://github.com/MonetDB/MonetDB/issues/1028 | 753,301,594 | 1,028 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-09 06:21:10 +0200
From: @Teggy
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-01-22 03:24:43 +0100
## Comment 5794
Date: 2006-08-09 18:21:10 +0200
From: @Teggy
Hi all,
the (bogus) query
doc("foo.xml")/@a/text()
causes a MIL generator hiccup:
looking for att: item, ty: 0x200
environment looks like:
att: iter, type: 0x1, mvar->name: a0001
att: item, type: 0x800, mvar->name: a0004
att: item, type: 0x400, mvar->name: a0005
/Users/grust/sci/XQuery/pf/compiler/mil/milgen.brg:461:
failed assertion `0'
Abort trap
(For reference:
type 0x200 = pre
type 0x800 = attr
type 0x400 = attr fragment
)
Cheers,
--Teggy
## Comment 5795
Date: 2006-11-05 16:58:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
added tests in
pathfinder/tests/BugTracker/Tests/bogus_text_step.SF-1537500.{mps,alg}.*
milprint_summer (mps) version produces correct/expected
!ERROR: path steps are only supported starting from
non-attribute nodes
algebra (alg) version fails as reported
## Comment 5796
Date: 2007-02-19 15:57:18 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Jan is responsible for the algebra version.
## Comment 5797
Date: 2007-05-20 10:35:16 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
just to keep you posted:
after Peter's recent changes,
the MPS version simply produces an empty result and/but no error message any more;
cf.,
[ 1712449 ] PF: "bogus_text_step" test fails since 2007.03.08
http://sourceforge.net/tracker/index.php?func=detail&aid=1712449&group_id=56967&atid=482468
the algebra version still fails as initially reported;
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.alg.err.00.html
## Comment 5798
Date: 2007-06-05 22:38:18 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Lowered priority of algebra bug for this release.
The algebra version will be subject of the next release.
## Comment 5799
Date: 2007-07-25 17:58:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
With yesterday's (Tue Jul 24 2007) checkins, the error message in the MPS case is back, cf,:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.mps.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.mps.out.00.html
Is this intended?
If so, please (re-)approve the new (old) stable output.
If not, please fix the new code.
The algebra case (still?/now?) fails with
========
looking for att: item, ty: 0x200
environment looks like:
att: iter, type: 0x1, mvar->name: a0004
att: item, type: 0x800, mvar->name: a0005
att: item, type: 0x400, mvar->name: a0006
fatal error: attribute 'item' with type '0x200' not found in environment
========
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.alg.err.00.html
## Comment 5800
Date: 2007-09-12 11:31:33 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
This has been solved by a Core rewrite.
## Comment 5801
Date: 2008-01-22 14:54:09 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
re-opened as both the MPS & the ALG version fail (again), since 2007.12.08, i.e., after checkins on 2007.12.07, now with
pf: .../pathfinder/compiler/core/coreopt.brg:441: reduce: Assertion `rule' failed.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.mps.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.mps.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.alg.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugTracker/bogus_text_step.SF-1537500.alg.err.00.html
## Comment 5802
Date: 2008-01-22 15:24:42 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
taken over by new bug report
[ 1877300 ] XQ: reduce: Assertion `rule' failed
https://sourceforge.net/tracker/index.php?func=detail&aid=1877300&group_id=56967&atid=482468
## Comment 5803
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1537500 at http://sourceforge.net/support/tracker.php?aid=1537500
| PF/algebra: bogus text() location step break MIL generation | https://api.github.com/repos/MonetDB/MonetDB/issues/1027/comments | 0 | 2020-11-30T09:16:46Z | 2024-06-27T11:19:28Z | https://github.com/MonetDB/MonetDB/issues/1027 | 753,301,552 | 1,027 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-04 05:04:02 +0200
From: @drstmane
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2006-08-10 10:50:30 +0200
## Comment 5790
Date: 2006-08-04 17:04:02 +0200
From: @drstmane
pf:
/var/tmp/monet.GNU.64.64.d.20507/pathfinder/compiler/mil/mil_dce.c:137:
mil_dce_worker: Assertion `0' failed.
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q10.err.00.html
## Comment 5791
Date: 2006-08-05 12:21:19 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
The query works fine without mil dead code elimination. Thus
Samuel should have a look.
## Comment 5792
Date: 2006-08-10 10:50:30 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fixed in CVS (hopefully).
Samuel's code was correct (though not very explanatory).
Problem was that the MIL translation for MergedUnion
introduced a side-effect to both arguments, which the dead
code eliminator detected.
See also my commit message.
## Comment 5793
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1534621 at http://sourceforge.net/support/tracker.php?aid=1534621
| PF (Algebra): XMark q10 triggers assertion in compiler | https://api.github.com/repos/MonetDB/MonetDB/issues/1026/comments | 0 | 2020-11-30T09:16:43Z | 2024-06-27T11:19:28Z | https://github.com/MonetDB/MonetDB/issues/1026 | 753,301,515 | 1,026 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-04 03:17:24 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-08-16 11:48:35 +0200
## Comment 5787
Date: 2006-08-04 15:17:24 +0200
From: @drstmane
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal
-I../../..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal
-I../atoms
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/../atoms
-I../kernel
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/../kernel
-I../../mal
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/../../mal
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBMSERVER -g -we140 -wd1418 -c99 -Wall -w2 -we266
-Werror -wd1418,1419,279,981,810,193,111,1357,1572,1599
-D_REENTRANT -c mserver.c -KPIC -DPIC -o
.libs/lib_mserver_la-mserver.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/mserver.mx(603):
error 181: argument is incompatible with corresponding
format string conversion
((ntohl(addr.s_addr) >>
24) & 0xff),
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/mserver.mx(604):
error 181: argument is incompatible with corresponding
format string conversion
((ntohl(addr.s_addr) >>
16) & 0xff),
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/mserver.mx(605):
error 181: argument is incompatible with corresponding
format string conversion
((ntohl(addr.s_addr) >>
8) & 0xff),
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/monet5/src/modules/mal/mserver.mx(606):
error 181: argument is incompatible with corresponding
format string conversion
(ntohl(addr.s_addr) &
0xff));
^
compilation aborted for mserver.c (code 2)
make[7]: *** [lib_mserver_la-mserver.lo] Error 1
see also (e.g.)
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.ntv.64.64.d-Fedora4/make-k.out
## Comment 5788
Date: 2006-08-16 23:48:35 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Solved already by fabian on .
2006/08/07 12:45:10; author: fabian; state: Exp; lines: +5 -5
As Niels pointed out, ntohl returns unsigned ints, so just print
unsigned values.
## Comment 5789
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1534526 at http://sourceforge.net/support/tracker.php?aid=1534526
| MonetDB v5: compilation (still) fails with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1025/comments | 0 | 2020-11-30T09:16:40Z | 2024-06-27T11:19:27Z | https://github.com/MonetDB/MonetDB/issues/1025 | 753,301,472 | 1,025 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-04 03:08:16 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-08-04 04:00:45 +0200
## Comment 5783
Date: 2006-08-04 15:08:16 +0200
From: @drstmane
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/pathfinder/compiler/algebra/opt
-I../../..
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/pathfinder/compiler/algebra/opt
-I../../include
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/pathfinder/compiler/algebra/opt/../../include
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.20507/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-DLIBOPT -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599 -c
/export/scratch0/monet/monet.ntv.64.64.d.20507/pathfinder/compiler/algebra/opt/opt_key.c
-KPIC -DPIC -o .libs/libopt_la-opt_key.o
/export/scratch0/monet/monet.ntv.64.64.d.20507/pathfinder/compiler/algebra/opt/opt_key.c(162):
error 128: loop is not reachable from preceding code
for (unsigned int i = 0; i <
p->schema.count; i++)
^
compilation aborted for
/export/scratch0/monet/monet.ntv.64.64.d.20507/pathfinder/compiler/algebra/opt/opt_key.c
(code 2)
make[8]: *** [libopt_la-opt_key.lo] Error 1
see also (e.g.)
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/sql5/.ntv.64.64.d-Fedora4/make-k.out
## Comment 5784
Date: 2006-08-04 15:18:42 +0200
From: @drstmane
Logged In: YES
user_id=572415
Oops, wrong URL, sorry!
must be:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora4/make-k.out
## Comment 5785
Date: 2006-08-04 16:00:45 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
adding 'if 0' should fix this one...
## Comment 5786
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1534520 at http://sourceforge.net/support/tracker.php?aid=1534520
| PF: compiler/algebra fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1024/comments | 0 | 2020-11-30T09:16:37Z | 2024-06-27T11:19:26Z | https://github.com/MonetDB/MonetDB/issues/1024 | 753,301,439 | 1,024 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-03 12:18:34 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-08-03 12:30:52 +0200
## Comment 5780
Date: 2006-08-03 12:18:34 +0200
From: @drstmane
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/monet5/src/mal
-I../..
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/monet5/src/mal
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/MonetDB/.ntv.64.64.d-Fedora4/include/MonetDB/C
-I../optimizer
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/monet5/src/mal/../optimizer
-I../scheduler
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/monet5/src/mal/../scheduler
-I../modules/kernel
-I/export/scratch0/monet/monet.ntv.64.64.d.15624/monet5/src/mal/../modules/kernel
-DLIBMAL -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,981,810,193,111,1357,1572,1599
-D_REENTRANT -c mal_session.c -KPIC -DPIC -o
.libs/libmal_la-mal_session.o
/export/scratch0/monet/monet.ntv.64.64.d.15624/monet5/src/mal/mal_session.mx(232):
error 593: variable "len" was set but never used
int len;
^
compilation aborted for mal_session.c (code 2)
make[5]: *** [libmal_la-mal_session.lo] Error 1
cf.,
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.ntv.64.32.d-Fedora4/make.out
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.ntv.64.64.d-Fedora4/make.out
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.ntv.64.64.d-RedHat4WS/make.out
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.ntv.64.64.d-SuSE9.3/make.out
## Comment 5781
Date: 2006-08-03 12:30:52 +0200
From: @grobian
Logged In: YES
user_id=963970
icc is correct, I wanted to use "len" for properly
terminating a buffer, but forgot about that.
NO TEST/COMPILATION
## Comment 5782
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1533773 at http://sourceforge.net/support/tracker.php?aid=1533773
| MonetDB v5: compilation fails with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1023/comments | 0 | 2020-11-30T09:16:34Z | 2024-06-27T11:19:25Z | https://github.com/MonetDB/MonetDB/issues/1023 | 753,301,390 | 1,023 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-03 12:14:13 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-08-03 12:25:16 +0200
## Comment 5776
Date: 2006-08-03 12:14:13 +0200
From: @drstmane
On Darwin & Debian, MonetDB v5 fail to compile with:
gcc -m32 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal
-I../../..
-I/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal
-I../atoms
-I/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/../atoms
-I../kernel
-I/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/../kernel
-I../../mal
-I/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/../../mal
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.15624/MonetDB/.GNU.32.32.d-Darwin8.6.0/include/MonetDB/C
-I/Users/monet/soft/pcre-5.0/include -DLIBMSERVER -O2
-std=c99 -Wall -W -O6 -fomit-frame-pointer
-finline-functions
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -Wno-sign-compare -D_REENTRANT -c
mserver.c -fno-common -DPIC -o
.libs/lib_mserver_la-mserver.o
/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/mserver.mx:
In function 'SERVERannounce':
/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/mserver.mx:593:
error: 'HOST_NAME_MAX' undeclared (first use in this
function)
/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/mserver.mx:593:
error: (Each undeclared identifier is reported only once
/var/tmp/monet.GNU.32.32.d.15624/monet5/src/modules/mal/mserver.mx:593:
error: for each function it appears in.)
make[7]: *** [lib_mserver_la-mserver.lo] Error 1
cf.,
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.GNU.32.32.d-Darwin8.6.0/make.out
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.GNU.64.64.d-Debian3.1/make.out
## Comment 5777
Date: 2006-08-03 12:25:16 +0200
From: @grobian
Logged In: YES
user_id=963970
Linux manual said it was a POSIX thing. Anyway, replaced
with some probably sufficient value.
NO TEST/COMPILATION
## Comment 5778
Date: 2006-08-03 12:56:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for info:
Darwin:
========
$ find /usr/include/ -type f | xargs grep HOST_NAME_MAX
Binary file
/usr/include//gcc/darwin/4.0/c++/i686-apple-darwin8/bits/stdc++.h.gch/O0g.gch
matches
Binary file
/usr/include//gcc/darwin/4.0/c++/i686-apple-darwin8/bits/stdc++.h.gch/O2g.gch
matches
Binary file
/usr/include//gcc/darwin/4.0/c++/powerpc-apple-darwin8/bits/stdc++.h.gch/O0g.gch
matches
Binary file
/usr/include//gcc/darwin/4.0/c++/powerpc-apple-darwin8/bits/stdc++.h.gch/O2g.gch
matches
/usr/include//limits.h:define _POSIX_HOST_NAME_MAX 255
/usr/include//unistd.h:define _SC_HOST_NAME_MAX
72
Debian:
========
$ find /usr/include/ -type f | xargs grep HOST_NAME_MAX
/usr/include/x86_64-linux/bits/confname.h: _SC_HOST_NAME_MAX,
/usr/include/x86_64-linux/bits/confname.h:define
_SC_HOST_NAME_MAX _SC_HOST_NAME_MAX
/usr/include/i486-linux/bits/confname.h: _SC_HOST_NAME_MAX,
/usr/include/i486-linux/bits/confname.h:define
_SC_HOST_NAME_MAX _SC_HOST_NAME_MAX
Fedora Core:
============
$ find /usr/include/ -type f | xargs grep HOST_NAME_MAX
Binary file
/usr/include/c++/4.0.2/i386-redhat-linux/bits/stdc++.h.gch/O0g.gch
matches
Binary file
/usr/include/c++/4.0.2/i386-redhat-linux/bits/stdc++.h.gch/O2g.gch
matches
Binary file
/usr/include/c++/4.0.2/x86_64-redhat-linux/bits/stdc++.h.gch/O0g.gch
matches
Binary file
/usr/include/c++/4.0.2/x86_64-redhat-linux/bits/stdc++.h.gch/O2g.gch
matches
/usr/include/linuxthreads/bits/local_lim.h:define
HOST_NAME_MAX 64
/usr/include/bits/posix1_lim.h:define _POSIX_HOST_NAME_MAX
255
/usr/include/bits/local_lim.h:define HOST_NAME_MAX
64
/usr/include/bits/confname.h: _SC_HOST_NAME_MAX,
/usr/include/bits/confname.h:define _SC_HOST_NAME_MAX
_SC_HOST_NAME_MAX
/usr/include/gaim/internal.h:ifndef HOST_NAME_MAX
/usr/include/gaim/internal.h: define HOST_NAME_MAX 255
SunOS 5.10 / Solaris 10:
========================
$ find /usr/include/ -type f | xargs grep HOST_NAME_MAX
/usr/include/sys/unistd.h:define _SC_HOST_NAME_MAX
735
/usr/include/limits.h:define _POSIX_HOST_NAME_MAX
255
## Comment 5779
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1533771 at http://sourceforge.net/support/tracker.php?aid=1533771
| MonetDB v5: 'HOST_NAME_MAX' undeclared on Darwin and Debian | https://api.github.com/repos/MonetDB/MonetDB/issues/1022/comments | 0 | 2020-11-30T09:16:30Z | 2024-06-27T11:19:24Z | https://github.com/MonetDB/MonetDB/issues/1022 | 753,301,351 | 1,022 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-03 11:36:07 +0200
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2006-08-03 12:33:17 +0200
## Comment 5773
Date: 2006-08-03 11:36:07 +0200
From: @grobian
makeinfo --force --html sqlmanual.texi
--css-include=manual.css \
)
/net/pegasus.ins.cwi.nl/export/scratch1/fabian/monetdb/five/monetdb/doc/share/tmp/sqlmanual//Assets/About-this-manual.texi:88:
Cross reference to nonexistent node `SQL' (perhaps
incorrect sectioning?).
make[1]: *** [web] Error 1
make[1]: Leaving directory
`/net/pegasus.ins.cwi.nl/export/scratch1/fabian/monetdb/five/monetdb/doc/manual'
make: *** [webs] Error 2
## Comment 5774
Date: 2006-08-03 12:33:17 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Fixed by correcting reference.
## Comment 5775
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1533750 at http://sourceforge.net/support/tracker.php?aid=1533750
| M5: documentation generation fails on texi | https://api.github.com/repos/MonetDB/MonetDB/issues/1021/comments | 0 | 2020-11-30T09:16:27Z | 2024-06-27T11:19:23Z | https://github.com/MonetDB/MonetDB/issues/1021 | 753,301,303 | 1,021 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-02 07:04:53 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2006-08-16 11:43:54 +0200
## Comment 5767
Date: 2006-08-02 19:04:53 +0200
From: @drstmane
In MonetDB v5, to the best of my knowledge, there is no
way to enforce property checking and hence to support
debugging.
Given that MonetDB's performance AND correctness highly
depends on proper propagation of BAT properties ---
"lazy" propagation of properties such as sortedness,
key-/uniqueness, denseness will result in poor
performance; however, being "too eager" and setting
these incorrectly will result in incorrect results ---,
I indeed consider this a bug, rather than a missing
feature --- fell free to overrule in case you think
differently ;-)
GDK provides a convenient centrally located function
"BATpropcheck" that does extensive property checking.
In MonetDB v4, using debugmask 10 makes the MIL
interpreter check each intermediate BAT result.
In MonetDB v5, setting debugmask seems to have no
effect at all. In fact, the whole code base contains
only a single reference to BATpropcheck --- in the
implementation of bat.isaKey() ...
To show the impact, I made an "evil" version of
radix.uniform() that incorrectly claims that tail of
the results BAT was sorted. Here's what M4 and M5 say
about this:
========
$ cat /tmp/evil.mil
module(radix);
var a := uniform(9);
print(a);
a.ordered().print();
a.reverse().ordered().print();
debugmask(10);
var b := uniform(9);
print(b);
b.ordered().print();
b.reverse().ordered().print();
quit();
--------
$ Mserver --set monet_prompt='' < /tmp/evil.mil
Monet Database Server V4.13.1
Copyright (c) 1993-2006, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
-----------------
h t name
oid int type
-----------------
[ 0@0, 1 ]
[ 1@0, 6 ]
[ 2@0, 2 ]
[ 3@0, 0 ]
[ 4@0, 8 ]
[ 5@0, 3 ]
[ 6@0, 7 ]
[ 7@0, 4 ]
[ 8@0, 5 ]
[ true ]
[ true ]
!WARNING: BATpropcheck: BAT tmp_342 was incorrectly
marked sorted!
-----------------
h t name
oid int type
-----------------
[ 0@0, 1 ]
[ 1@0, 8 ]
[ 2@0, 5 ]
[ 3@0, 3 ]
[ 4@0, 0 ]
[ 5@0, 7 ]
[ 6@0, 2 ]
[ 7@0, 6 ]
[ 8@0, 4 ]
[ true ]
[ false ]
========
========
$ cat /tmp/evil.mal
include radix;
a := radix.uniform(9);
io.print(a);
o := bat.isSorted(a); io.print(o);
r := bat.reverse(a); o := bat.isSorted(r); io.print(o);
mdb.setDebug(10);
b := radix.uniform(9);
io.print(b);
o := bat.isSorted(b); io.print(o);
r := bat.reverse(b); o := bat.isSorted(r); io.print(o);
clients.quit();
--------
$ mserver5 --set monet_prompt='' < /tmp/evil.mal
MonetDB Server v4.99.19
Copyright (c) 1993-2006 CWI, all rights reserved
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs dynamically linked
config:/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONET5/etc/MonetDB5.conf
dbfarm:/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONET5/var/MonetDB5/dbfarm
dbname:demo
Visit http://monetdb.cwi.nl/ for further information
-----------------
h t name
oid int type
-----------------
[ 0@0, 1 ]
[ 1@0, 6 ]
[ 2@0, 2 ]
[ 3@0, 0 ]
[ 4@0, 8 ]
[ 5@0, 3 ]
[ 6@0, 7 ]
[ 7@0, 4 ]
[ 8@0, 5 ]
[ true ]
[ true ]
-----------------
h t name
oid int type
-----------------
[ 0@0, 1 ]
[ 1@0, 8 ]
[ 2@0, 5 ]
[ 3@0, 3 ]
[ 4@0, 0 ]
[ 5@0, 7 ]
[ 6@0, 2 ]
[ 7@0, 6 ]
[ 8@0, 4 ]
[ true ]
[ true ]
========
## Comment 5768
Date: 2006-08-02 19:33:20 +0200
From: @mlkersten
Logged In: YES
user_id=490798
- The GDKdebug flags can be set with mdb.setDebug(<int>)
or at the command line, e.g.
mserver5 --debug=3
- Only those debugging actions are affected that live at
the GDK/module code base and which are compiled in.
- The MAL debugger is the place to add support for more
extensive testing, either manually or automatic as part
of a trace.
- Upon request, I will add required specific tests there.
- Enforcement is a design issue and is a cost/benefit issue.
Basically, a function implementation should manage the
properties correctly. A property can only be enforced when
you call a routine performing this task.
## Comment 5769
Date: 2006-08-02 21:10:50 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Not waiting for the request, I have added the BATpropcheck
calls in the MALinterpreter. It is controlled by GDKdehttp://sourceforge.net/support/tracker.php?aid=10.
It can also be set when you are inside the debugger, e.g.
mdb>dehttp://sourceforge.net/support/tracker.php?aid=10
which returns the previous flag.
In debugging mode, inspection of a BAT variable triggers
the property check as well.
Testweb still shows around 15 errors after this change.
## Comment 5770
Date: 2006-08-03 08:35:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
I indeed meant the enforcement of the property CHECK for
DEBUGGING and code VERIFICATION (as Martin added it now),
not enforcement or (exhaustive) property PROPAGATION.
Indeed, it's the reponsibility of the functions'
implement(ation|or) to propagate properties correctly;
in case of doubt, a property should not be set;
not setting a property though it does/might hold is not
"incorrect", it just might not allow the use of the most
efficient implementation;
setting a property although it does NOT hold IS INCORRECT
and may/will lead to INCORRECT behaviour/results!
Setting a property is often done "implictly", e.g., by
inheriting it from the input, or by BATnew; in case they
know better AND in case of doubt, function implementations
need to explicitly UNSET properties that might/do not hold
(anymore)!
Especially lack of the latter in M5 code is now detected by
testing with property checking/verification enabled.
## Comment 5771
Date: 2006-08-16 23:43:54 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Close this bug, since a solution has been presented by
implementation of the property checks in the interpreter.
## Comment 5772
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1533311 at http://sourceforge.net/support/tracker.php?aid=1533311
| MonetDB v5: no means to do/enforce property checking | https://api.github.com/repos/MonetDB/MonetDB/issues/1020/comments | 0 | 2020-11-30T09:16:24Z | 2024-06-27T11:19:22Z | https://github.com/MonetDB/MonetDB/issues/1020 | 753,301,257 | 1,020 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-08-01 02:04:46 +0200
From: @swingbit
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-08-01 04:38:56 +0200
## Comment 5763
Date: 2006-08-01 14:04:46 +0200
From: @swingbit
The return data type of sum and prod aggregates is the
same as their input's data type.
I believe this is incorrect, because it returns
potentially unpredictable results.
Example:
mil>var a := new(void, sht).seqbase(0@0);
mil>a.append(sht(32000));
mil>a.append(sht(32000));
mil>var b := sum(a);
mil>b.print();
[ -1536 ]
Why shouldn't this sum be computable?
In my opinion, the correct behaviour (implemented in
x100) is that the result is always casted to the
largest data type available (lng in the example).
Then it can be casted back to smaller data types
manually, it depends on the application.
As it is now, many aggregates can compute a wrong
result. But what is worse, this behaviour is not
predictable, unless exact knowledge on the bat's
content is available.
## Comment 5764
Date: 2006-08-01 14:25:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
MonetDB>var a := new(void, sht).seqbase(0@0);
MonetDB>a.append(sht(32000));
MonetDB>a.append(sht(32000));
MonetDB>var b := sum(a);
MonetDB>b.print();
[ -1536 ]
MonetDB>var c := sum_int(a);
MonetDB>c.print();
[ 64000 ]
The default behaviour of sum and prod is indeed to maintain
the input's type, mainly to keep the result BAT small in
case of grouped aggregates ({sum}, {prod}), especially if
there happen to be many groups.
The decision was to have the default overrule be the
user/application just the the opposite way than you suggest,
i.e., not use the largest type by default, and cast-back by
hand, but use the original type by default (sum(), prod()),
and request larger types explicitely (e.g., sum_int() as
shown above.
Could you live with that?
The bug is indeed, that apparently none of the aggragation
functions does any (expensive!) overflow checking, and hence
returns "bogus" results (as opposed to errors or nil) in
case of overflows.
## Comment 5765
Date: 2006-08-01 16:38:56 +0200
From: @swingbit
Logged In: YES
user_id=883451
Oops, rrright.
I even new about sum_int() and sum_lng() at some point in
time, but apparently I forget things quickly...
Yes, I can live with that,
and I'll close the bug report marking it as Invalid.
## Comment 5766
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1532369 at http://sourceforge.net/support/tracker.php?aid=1532369
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| sum and prod should promote result type | https://api.github.com/repos/MonetDB/MonetDB/issues/1019/comments | 0 | 2020-11-30T09:16:21Z | 2024-06-28T13:33:00Z | https://github.com/MonetDB/MonetDB/issues/1019 | 753,301,216 | 1,019 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 06:21:05 +0200
From: @drstmane
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2006-07-31 07:29:58 +0200
## Comment 5760
Date: 2006-07-29 18:21:05 +0200
From: @drstmane
For the records:
Since 15.07.2006 (i.e., possibly due to checkins on
14.07.2006),
all XRpc tests fail apparently since a segfault occurs
in the compiler, crashing the Mserver, cf. e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XRpc_basic_queries/add_dbl.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XRpc_basic_queries/add_dbl.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XRpc_xmark_queries/q01.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XRpc_xmark_queries/q01.err.00.html
========
$ cat tests/XRpc/basic_queries/Tests/add_dbl.xq.in |
sed 's|$TSTSRCDIR|tests/XRpc/basic_queries/Tests|' | pf
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 3
We apologize for the inconvenience...
Segmentation fault
========
$ cat tests/XRpc/xmark_queries/Tests/q01.xq.in | sed
's|$TSTSRCDIR|tests/XRpc/xmark_queries/Tests|' | pf
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 3
We apologize for the inconvenience...
Segmentation fault
========
Most probably, this bug is related to (if not identical
with)
http://sourceforge.net/support/tracker.php?aid=1530852 "PF: compiling modularized queries (XMark,
Music) => segfault"
http://sourceforge.net/tracker/index.php?func=detail&aid=1530852&group_id=56967&atid=482468
## Comment 5761
Date: 2006-07-31 19:29:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed in CVS by Jens' fix for
http://sourceforge.net/support/tracker.php?aid=1530852 ] "PF: compiling modularized queries (XMark,
Music) => segfault".
Thanks, Jens!
## Comment 5762
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530930 at http://sourceforge.net/support/tracker.php?aid=1530930
| PF: compiling XRpc queries causes segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/1018/comments | 0 | 2020-11-30T09:16:17Z | 2024-06-27T11:19:20Z | https://github.com/MonetDB/MonetDB/issues/1018 | 753,301,173 | 1,018 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 05:15:09 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2006-07-30 09:00:31 +0200
## Comment 5757
Date: 2006-07-29 17:15:09 +0200
From: @drstmane
For tests src/mal/Tests/tst670.mal and
src/optimizer/Tests/CRexample.mal, no stable output has
been added/approved, yet.
## Comment 5758
Date: 2006-07-30 21:00:30 +0200
From: @mlkersten
Logged In: YES
user_id=490798
They have now.
## Comment 5759
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530910 at http://sourceforge.net/support/tracker.php?aid=1530910
| MonetDB v5: stable output missing for tests | https://api.github.com/repos/MonetDB/MonetDB/issues/1017/comments | 0 | 2020-11-30T09:16:14Z | 2024-06-27T11:19:19Z | https://github.com/MonetDB/MonetDB/issues/1017 | 753,301,142 | 1,017 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 05:03:16 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2006-07-29 05:28:36 +0200
## Comment 5754
Date: 2006-07-29 17:03:16 +0200
From: @drstmane
With gcc 4.2 (at least on Gentoo), compiling monet5
fails with:
========
make[7]: Entering directory
`/var/tmp/monet.GNU.32.32.d.24201/monet5/Gentoo1.6.15/src/modules/atoms'
/bin/sh ../../../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms
-I../../..
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms
-I../../mal
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/../../mal
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/C
-DLIBMTIME -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -Werror-implicit-function-declaration
-Werror -Wno-unused-function -Wno-unused-label
-Wno-sign-compare -D_REENTRANT -c -o
lib_mtime_la-mtime.lo `test -f 'mtime.c' || echo
'/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/'`mtime.c
gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms
-I../../..
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms
-I../../mal
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/../../mal
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/C
-DLIBMTIME -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-sign-compare -D_REENTRANT -c mtime.c -fPIC -DPIC
-o .libs/lib_mtime_la-mtime.o
cc1: warnings being treated as errors
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:
In function 'MTIMEprelude':
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2707:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
/var/tmp/monet.GNU.32.32.d.24201/monet5/src/modules/atoms/mtime.mx:2711:
warning: dereferencing type-punned pointer will break
strict-aliasing rules
make[7]: *** [lib_mtime_la-mtime.lo] Error 1
========
see also
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.Makes3/index_short.html
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/monet5/.GNU.32.32.d-Gentoo1.6.15/make-k.out
## Comment 5755
Date: 2006-07-29 17:28:36 +0200
From: @grobian
Logged In: YES
user_id=963970
I checked in a fix which should get around the type-pun with
a union.
NO TEST/COMPILATION
## Comment 5756
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530904 at http://sourceforge.net/support/tracker.php?aid=1530904
| MonetDB v5: Compilation fails with gcc 4.2 (on Gentoo) | https://api.github.com/repos/MonetDB/MonetDB/issues/1016/comments | 0 | 2020-11-30T09:16:10Z | 2024-06-27T11:19:18Z | https://github.com/MonetDB/MonetDB/issues/1016 | 753,301,089 | 1,016 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 04:31:19 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2006-07-29 05:00:20 +0200
## Comment 5751
Date: 2006-07-29 16:31:19 +0200
From: @grobian
make[7]: Entering directory
`/var/tmp/monet.GNU.32.32.d.24201/sql/Gentoo1.6.15/src/backends/monet5'
/bin/sh ../../../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5
-I../../..
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5
-I../../include
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../include
-I../../common
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../common
-I../../storage
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../storage
-I../../server
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../server
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/C
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/atoms
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/compiler
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/kernel
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/mal
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/mil
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/optimizer
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/C
-DLIBEMBEDDEDSQL5 -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -Werror-implicit-function-declaration
-Werror -Wno-unused-function -Wno-unused-label
-Wno-sign-compare -c -o
libembeddedsql5_la-embeddedclient.lo `test -f
'embeddedclient.c' || echo
'/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/'`embeddedclient.c
mkdir .libs
gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5
-I../../..
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5
-I../../include
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../include
-I../../common
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../common
-I../../storage
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../storage
-I../../server
-I/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/../../server
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/C
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/atoms
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/compiler
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/kernel
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/mal
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/mil
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5/optimizer
-I/var/tmp/monet.GNU.32.32.d.24201/monet5/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB5
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.24201/MonetDB/.GNU.32.32.d-Gentoo1.6.15/include/MonetDB/C
-DLIBEMBEDDEDSQL5 -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-sign-compare -c embeddedclient.c -fPIC -DPIC -o
.libs/libembeddedsql5_la-embeddedclient.o
In file included from
/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/embeddedclient.mx:74:
embeddedclient.h:35:21: error: mserver.h: No such file
or directory
I don't understand how other platforms do it, because
mserver.h is in modules/mal, which is indeed not in the
include path...
This problem leads most probably to the next error:
In file included from
/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/embeddedclient.mx:74:
embeddedclient.h:37: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'embedded_sql'
/var/tmp/monet.GNU.32.32.d.24201/sql/src/backends/monet5/embeddedclient.mx:190:
error: expected '=', ',', ';', 'asm' or '__attribute__'
before 'embedded_sql'
make[7]: *** [libembeddedsql5_la-embeddedclient.lo] Error 1
## Comment 5752
Date: 2006-07-29 17:00:20 +0200
From: @drstmane
Logged In: YES
user_id=572415
mserver.h gets installed to
$MONET5_PREFIX/include/MonetDB5/mal which is in
$(MONET5_INCS) and hence in the include path in
sql/src/backends/monet5/ .
However, on Gentoo, make (and hence make install) for monet5
fails (see next bug report), and hence mserver.h gets never
installed to $MONET5_PREFIX/include/MonetDB5/mal, and hence
not found when compiling sql/src/backends/monet5/ .
## Comment 5753
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530894 at http://sourceforge.net/support/tracker.php?aid=1530894
| SQL: Gentoo/GCC4.2 cannot find mserver.h for embedded.c | https://api.github.com/repos/MonetDB/MonetDB/issues/1015/comments | 0 | 2020-11-30T09:16:07Z | 2024-06-28T13:32:59Z | https://github.com/MonetDB/MonetDB/issues/1015 | 753,301,045 | 1,015 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 04:20:18 +0200
From: @drstmane
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2006-10-31 10:52:30 +0100
## Comment 5748
Date: 2006-07-29 16:20:18 +0200
From: @drstmane
In the CVS head, most StandOff tests fail, as StandOff
still seems to use the obsolete {KIND,PROP}_PRE indices:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_basic/test1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_basic/test2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_basic/lltest.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_video/scenes.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_video/songs.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_video/artists.out.00.html
The standoff code need to be ported to the new
update-enabled scenario --- probably only once the
update code is stabelized...
## Comment 5749
Date: 2006-10-31 22:52:30 +0100
From: @drstmane
Logged In: YES
user_id=572415
The StandOff tests have been working fine, again, for quite
some time.
## Comment 5750
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530888 at http://sourceforge.net/support/tracker.php?aid=1530888
| PF: StandOff still uses obsolete {KIND,PROP}_PRE indices | https://api.github.com/repos/MonetDB/MonetDB/issues/1014/comments | 0 | 2020-11-30T09:16:03Z | 2024-06-27T11:19:16Z | https://github.com/MonetDB/MonetDB/issues/1014 | 753,301,002 | 1,014 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 04:14:45 +0200
From: @drstmane
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2006-10-31 10:52:41 +0100
## Comment 5745
Date: 2006-07-29 16:14:45 +0200
From: @drstmane
When shredding documents with standoff annotation
enabled, the MonetDB/XQuery 0.12.0 release says
something like
[ " extracting regions...\n" ]
extracted ? regions
while the CVS head does not:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_basic/test1_import.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_basic/test2_import.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_basic/lltest_import.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_StandOff_video/import_doc.out.00.html
Does this indicate some bug in the CVS head, or is it
"just a feature"?
In case it's a feature, i.e., it is correct that the
above output does not occur in the CVS head (any more),
the respective tests' output should be fixed/approved.
## Comment 5746
Date: 2006-10-31 22:52:41 +0100
From: @drstmane
Logged In: YES
user_id=572415
The StandOff tests have been working fine, again, for quite
some time.
## Comment 5747
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530886 at http://sourceforge.net/support/tracker.php?aid=1530886
| PF: StandOff-enabled shredding differs 0.12.0 vs. CVS head | https://api.github.com/repos/MonetDB/MonetDB/issues/1013/comments | 0 | 2020-11-30T09:16:00Z | 2024-06-27T11:19:15Z | https://github.com/MonetDB/MonetDB/issues/1013 | 753,300,962 | 1,013 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 02:41:20 +0200
From: @drstmane
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2006-07-31 11:47:28 +0200
## Comment 5737
Date: 2006-07-29 14:41:20 +0200
From: @drstmane
For the records:
Since 15.07.2006 (i.e., possibly due to checkins on
14.07.2006),
compiling the modularized XQuery queries for both
Music (tests/Music/mod/XQ/Tests/music.xq,
tests/Music/opt/XQ/Tests/music.xq) and
XMark (tests/XMark/mod/XQ/Tests/xmark.xq,
tests/XMark/opt/XQ/Tests/xmark.xq)
causes pf to segfault:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Music_mod_MIL/xq2mil.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_Music_opt_MIL/xq2mil.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_mod_MIL/xq2mil.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_opt_MIL/xq2mil.err.00.html
## Comment 5738
Date: 2006-07-29 14:45:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
Actually, the segfault "only" occurs on all platforms except
Darwin/MacOS X (on PowerPC); hence, it *might* be
little-endian/big-endian related...
## Comment 5739
Date: 2006-07-29 14:55:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
However, also on Darwin, the generated .mil modules appears
to be corrupted (or simply empty?):
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Darwin8.6.0/tests_Music_mod_MIL/full_01.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Darwin8.6.0/tests_Music_opt_MIL/full_01.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Darwin8.6.0/tests_XMark_mod_MIL/q01.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Darwin8.6.0/tests_XMark_opt_MIL/q01.err.00.html
## Comment 5740
Date: 2006-07-29 15:57:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
Obviously, these problems crash all Music and XMark tests
(tests/{Music,XMark}/{mod,opt}/MIL/Tests/) that (try to)
use/import the generated {miusic,xmark}.mil modules.
Likewise, all Music and XMark tests that use the original
XQuery versions of the modularized queries
(tests/{Music,XMark}/{mod,opt}/XQ/Tests/) fail as well, as
the compilation crashes the Mserver.
## Comment 5741
Date: 2006-07-29 18:25:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Most probably, this bug is related to (if not identical
with)
http://sourceforge.net/support/tracker.php?aid=1530930 "PF: compiling XRpc queries causes segfault"
http://sourceforge.net/tracker/index.php?func=detail&aid=1530930&group_id=56967&atid=482468
More details:
========
$ pf tests/XMark/mod/XQ/Tests/xmark.xq
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 3
We apologize for the inconvenience...
Segmentation fault
--------
$ pf tests/XMark/opt/XQ/Tests/xmark.xq
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 3
We apologize for the inconvenience...
Segmentation fault
--------
$ pf tests/Music/mod/XQ/Tests/music.xq
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 3
We apologize for the inconvenience...
Segmentation fault
--------
$ pf tests/Music/opt/XQ/Tests/music.xq
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@pathfinder-xquery.org).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 3
We apologize for the inconvenience...
Segmentation fault
========
## Comment 5742
Date: 2006-07-29 18:52:12 +0200
From: @drstmane
Logged In: YES
user_id=572415
For info:
Simple debugging reveals the following:
========
$ cvs diff compiler/semantics/ns.c
Index: compiler/semantics/ns.c
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/compiler/semantics/ns.c,v
retrieving revision 1.23
diff -u -r1.23 ns.c
--- compiler/semantics/ns.c 26 Jul 2006 09:41:16 -0000
1.23
+++ compiler/semantics/ns.c 29 Jul 2006 16:46:05 -0000
@@ -256,10 +256,12 @@
{
assert (prefix);
- for (unsigned int i = PFarray_last (stat_known_ns); i; i--)
+ for (unsigned int i = PFarray_last (stat_known_ns); i;
i--) {
+ assert(((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix);
if (! strcmp (prefix,
((PFns_t *) PFarray_at
(stat_known_ns, i-1))->prefix))
return PFstrdup (((PFns_t *) PFarray_at
(stat_known_ns, i-1))->uri);
+ }
return NULL;
}
--------
$ pf tests/Music/mod/XQ/Tests/music.xq
pf:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/ns.c:260:
ns_lookup: Assertion `((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix' failed.
Aborted
--------
$ pf tests/Music/opt/XQ/Tests/music.xq
pf:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/ns.c:260:
ns_lookup: Assertion `((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix' failed.
Aborted
--------
$ pf tests/XMark/mod/XQ/Tests/xmark.xq
pf:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/ns.c:260:
ns_lookup: Assertion `((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix' failed.
Aborted
You have new mail in /ufs/manegold/Mail/manegold
--------
$ pf tests/XMark/opt/XQ/Tests/xmark.xq
pf:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/ns.c:260:
ns_lookup: Assertion `((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix' failed.
Aborted
--------
$ cat tests/XRpc/basic_queries/Tests/add_dbl.xq.in | sed
's|$TSTSRCDIR|tests/XRpc/basic_queries/Tests|' | pf
pf:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/ns.c:260:
ns_lookup: Assertion `((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix' failed.
Aborted
--------
$ cat tests/XRpc/xmark_queries/Tests/q01.xq.in | sed
's|$TSTSRCDIR|tests/XRpc/xmark_queries/Tests|' | pf
pf:
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/semantics/ns.c:260:
ns_lookup: Assertion `((PFns_t *) PFarray_at (stat_known_ns,
i-1))->prefix' failed.
Aborted
========
## Comment 5743
Date: 2006-07-31 11:47:28 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fix is now in CVS.
## Comment 5744
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530852 at http://sourceforge.net/support/tracker.php?aid=1530852
| PF: compiling modularized queries (XMark, Music) => segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/1012/comments | 0 | 2020-11-30T09:15:57Z | 2024-06-27T11:19:14Z | https://github.com/MonetDB/MonetDB/issues/1012 | 753,300,911 | 1,012 |
[
"MonetDB",
"MonetDB"
] | Date: 2006-07-29 02:17:27 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-08-04 04:01:22 +0200
## Comment 5735
Date: 2006-07-29 14:17:27 +0200
From: @drstmane
For the records:
Since 17.06.2006 (i.e., possible due to checkins on
16.06.2006), XMark q03 causes a segfault in the Algebra
version of the Pathfinder XQuery compiler:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/compiler/pf-A_XMark.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark_alg/q03.out.00.html
## Comment 5736
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1530839 at http://sourceforge.net/support/tracker.php?aid=1530839
| PF (Algebra): XMark q03 causes segfault in compiler | https://api.github.com/repos/MonetDB/MonetDB/issues/1011/comments | 0 | 2020-11-30T09:15:54Z | 2024-06-27T11:19:13Z | https://github.com/MonetDB/MonetDB/issues/1011 | 753,300,872 | 1,011 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.