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: 2005-06-10 04:46:49 +0200
From: Steffen Goeldner <<sgoeldner>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-06-14 04:17:37 +0200
## Comment 3392
Date: 2005-06-10 16:46:49 +0200
From: Steffen Goeldner <<sgoeldner>>
OS: Windows 2000
Compiler: MS VC++ Toolkit 2003
Parser tools: UnxUtils
After startup, Mserver uses 11 thread handles:
$handle -s -p Mserver
Handle v3.02
Copyright (C) 1997-2005 Mark Russinovich
Sysinternals - www.sysinternals.com
Handle type summary:
Desktop : 1
Directory : 2
Event : 21
File : 8
Key : 6
Port : 1
Section : 2
Semaphore : 44
Thread : 11
WindowStation : 2
After connect/disconnect a mapi client 999 times:
$FOR /L %i IN (1,1,999) DO bin\MapiClient.exe -c
etc\MonetDB.conf -s quit();
Mserver uses 1011 thread handles:
Desktop : 1
Directory : 2
Event : 1021
File : 8
Key : 6
Port : 1
Section : 2
Semaphore : 1043
Thread : 1011
WindowStation : 2
(Similar for Events and Semaphores.)
Can anybody confirm this?
## Comment 3393
Date: 2005-06-13 09:45:44 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
Various thread handle leaks are mentioned on
pthreads-win32@sources.redhat.com, e.g.
<http://sources.redhat.com/ml/pthreads-
win32/1999/msg00105.html>
They suggest to use PTHREAD_CREATE_DETACHED to
create the threads detached.
Indeed, this is implemented in gdk_system.mx:
ifdef PTHREAD_CREATE_DETACHED
pthread_attr_setdetachstate(&attr,
PTHREAD_CREATE_DETACHED);
endif
and ifdef'ed since 2001-03-14:
<http://cvs.sourceforge.net/viewcvs.py/monetdb/MonetDB/src/
gdk/gdk_system.mx?r1=1.27&r2=1.27.4.1>
Hovever, PTHREAD_CREATE_DETACHED isn't defined but
declared as an enum since 2001-07-01:
<http://sources.redhat.com/cgi-
bin/cvsweb.cgi/pthreads/pthread.h.diff?
r1=1.88&r2=1.89&cvsroot=pthreads-win32&f=h>
I don't know why this statement is protected by
an ifdef and if it's save to discard the ifdef
without substitution.
Dropping the ifdef fixes the leaks.
## Comment 3394
Date: 2005-06-14 15:24:54 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
After Sjoerd's checkin:
<http://cvs.sourceforge.net/viewcvs.py/monetdb/MonetDB/src/
gdk/gdk_system.mx?r1=1.80.2.2&r2=1.80.2.3>
the thread handle leak is fixed (999 x connect/disconnect):
Handle type summary:
Desktop : 1
Directory : 2
Event : 23
File : 8
Key : 6
Port : 1
Section : 2
Semaphore : 45
Thread : 13
WindowStation : 2
## Comment 3395
Date: 2005-06-14 16:17:37 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I guess we can now close this report.
## Comment 3396
Date: 2005-12-19 10:08:01 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / NO CLUE
## Comment 3397
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1218281 at http://sourceforge.net/support/tracker.php?aid=1218281
| Thread handle leak (Win32) | https://api.github.com/repos/MonetDB/MonetDB/issues/610/comments | 0 | 2020-11-30T08:45:07Z | 2024-06-27T11:04:48Z | https://github.com/MonetDB/MonetDB/issues/610 | 753,279,282 | 610 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-10 04:32:08 +0200
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2007-11-30 04:20:04 +0100
## Comment 3383
Date: 2005-06-10 16:32:08 +0200
From: Wouter Alink <<alink>>
When using an xml-document of size +-200MB, the
following query produces an "Bus error":
for $q in doc("result.xml")//folder
where not($q/ancestor::folder) and $q//*[contains(.,"aap")]
return $q/@name
The xml-document can be found here:
~alink/test-data/large.xml.gz
The query expresses (to my best knowledge) the most
shallow 'folder' element (without its descendant
'folder' elements) in which "aap" is found.
I think that the above query could be rewritten as:
for $q in doc("result.xml")//folder
except doc("result.xml")//folder//folder
where $q//*[contains(.,"aap")]
return $q/@name
which works fine... (and is almost solved in
interactive time)
So this bug is not really important important.
Program received signal SIGBUS, Bus error.
[Switching to Thread -1284027472 (LWP 9026)]
0x00e1438a in ll_descendant (result=0xb3770604,
iter_bat=0xa68ffc8, ctx_bat=0xa69f868,
pre_size=0x9a7ba000, cand_bat=0xa640838, height=19,
min_iter=1, max_iter=7847, self=1 '\001') at
ll_staircasejoin.mx:880
880 ll_staircasejoin.mx: No such file or directory.
in ll_staircasejoin.mx
(gdb) bt
0 0x00e1438a in ll_descendant (result=0xb3770604,
iter_bat=0xa68ffc8, ctx_bat=0xa69f868,
pre_size=0x9a7ba000, cand_bat=0xa640838,
height=19, min_iter=1, max_iter=7847, self=1
'\001') at ll_staircasejoin.mx:880
\1 0x00e1096b in PFll_descendant_or_self
(result=0xa67ff60, iter_bat=0xa68ffc8,
ctx_bat=0xa69f868, pre_size=0xa304150,
cand_bat=0xa640838, _height=0x1ea7,
_one_iter=0x1ea7 <Address 0x1ea7 out of bounds>,
_one_ctx=0x1ea7 <Address 0x1ea7 out of bounds>,
_min_iter=0x1ea7, _max_iter=0x1ea7) at
ll_staircasejoin.mx:366
2 0x00df56de in
PFll_descendant_or_self_unpack1036176909 (argc=10,
argv=0xa67ff60) at pf_support.glue.c:952
3 0x0066350e in interpret (stk=571, lt=0xa657028,
res=0xa0e8000) at monet_interpreter.mx:1147
4 0x00668b1a in interpret_assignment (stk=571,
lt=0xa656f40, res=0xa0e8000) at monet_interpreter.mx:1725
5 0x006625ab in interpret (stk=571, lt=0xa656f40,
res=0xa0e8000) at monet_interpreter.mx:748
6 0x00668e1c in interpret_seqblock (stk=571,
lt=0xa656ed8, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
7 0x00662600 in interpret (stk=583, lt=0xa656ed8,
res=0xa0e8000) at monet_interpreter.mx:755
8 0x006626f8 in interpret (stk=583, lt=0xa656ca0,
res=0xa0e8000) at monet_interpreter.mx:775
9 0x00668e1c in interpret_seqblock (stk=583,
lt=0xa646c00, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
10 0x00662600 in interpret (stk=582, lt=0xa6429a0,
res=0xa0e8000) at monet_interpreter.mx:755
11 0x00668e1c in interpret_seqblock (stk=582,
lt=0xa642180, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
12 0x00662600 in interpret (stk=594, lt=0xa642180,
res=0xa0e8000) at monet_interpreter.mx:755
13 0x00663938 in interpret (stk=594, lt=0xa5aa5c0,
res=0xa0e8000) at monet_interpreter.mx:1133
14 0x00668b1a in interpret_assignment (stk=594,
lt=0xa5aa4d8, res=0xa0e8000) at monet_interpreter.mx:1725
15 0x006649d5 in interpret_var (stk=594, lt=0xa5aa470,
res=0xa0e8000) at monet_interpreter.mx:1302
16 0x00662b09 in interpret (stk=594, lt=0xa5aa470,
res=0xa0e8000) at monet_interpreter.mx:817
17 0x00668e1c in interpret_seqblock (stk=594,
lt=0xa547830, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
18 0x00662600 in interpret (stk=601, lt=0xa547830,
res=0xa0e8000) at monet_interpreter.mx:755
19 0x006626f8 in interpret (stk=601, lt=0xa547488,
res=0xa0e8000) at monet_interpreter.mx:775
20 0x00668e1c in interpret_seqblock (stk=601,
lt=0xa5446f0, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
21 0x00662600 in interpret (stk=589, lt=0xa5446f0,
res=0xa0e8000) at monet_interpreter.mx:755
22 0x00668e1c in interpret_seqblock (stk=589,
lt=0xa543ed0, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
23 0x00662600 in interpret (stk=585, lt=0xa543ed0,
res=0xa0e8000) at monet_interpreter.mx:755
24 0x00663938 in interpret (stk=585, lt=0x9587f20,
res=0xa0e8000) at monet_interpreter.mx:1133
25 0x00668b1a in interpret_assignment (stk=585,
lt=0x9582070, res=0xa0e8000) at monet_interpreter.mx:1725
26 0x006649d5 in interpret_var (stk=585, lt=0x956fb58,
res=0xa0e8000) at monet_interpreter.mx:1302
27 0x00662b09 in interpret (stk=585, lt=0x956fb58,
res=0xa0e8000) at monet_interpreter.mx:817
28 0x00668e1c in interpret_seqblock (stk=585,
lt=0x9587e50, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
29 0x00662600 in interpret (stk=599, lt=0x9587e50,
res=0xa0e8000) at monet_interpreter.mx:755
30 0x006626f8 in interpret (stk=599, lt=0x978d278,
res=0xa0e8000) at monet_interpreter.mx:775
31 0x00668e1c in interpret_seqblock (stk=599,
lt=0x94a2938, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
32 0x00662600 in interpret (stk=591, lt=0x94a2938,
res=0xa0e8000) at monet_interpreter.mx:755
---Type <return> to continue, or q <return> to quit---\
33 0x00668e1c in interpret_seqblock (stk=591,
lt=0x9589e68, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
34 0x00662600 in interpret (stk=602, lt=0x9564d20,
res=0xa0e8000) at monet_interpreter.mx:755
35 0x006626f8 in interpret (stk=602, lt=0x97b5fb0,
res=0xa0e8000) at monet_interpreter.mx:775
36 0x00668e1c in interpret_seqblock (stk=602,
lt=0x95455c0, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
37 0x00662600 in interpret (stk=607, lt=0x95455c0,
res=0xa0e8000) at monet_interpreter.mx:755
38 0x00668e1c in interpret_seqblock (stk=607,
lt=0x96a5430, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
39 0x00662600 in interpret (stk=532, lt=0xa0fe680,
res=0xa0e8000) at monet_interpreter.mx:755
40 0x006626f8 in interpret (stk=532, lt=0x9b46ee8,
res=0xa0e8000) at monet_interpreter.mx:775
41 0x00668e1c in interpret_seqblock (stk=532,
lt=0xa0fe958, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
42 0x00662600 in interpret (stk=559, lt=0xa1037d0,
res=0xa0e8000) at monet_interpreter.mx:755
43 0x00668e1c in interpret_seqblock (stk=559,
lt=0x96f17e8, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
44 0x00662600 in interpret (stk=560, lt=0x9730628,
res=0xa0e8000) at monet_interpreter.mx:755
45 0x009f78c4 in CMDcatch (stk=560, lt=0x9c7aff0,
res=0xa0e8000) at builtin.mx:1050
46 0x00662bc0 in interpret (stk=560, lt=0x9c7aff0,
res=0xa0e8000) at monet_interpreter.mx:845
47 0x00668b1a in interpret_assignment (stk=560,
lt=0x9c7b070, res=0xa0e8000) at monet_interpreter.mx:1725
48 0x006625ab in interpret (stk=560, lt=0x9c7b070,
res=0xa0e8000) at monet_interpreter.mx:748
49 0x00668e1c in interpret_seqblock (stk=560,
lt=0x9c7b0e8, res=0xa0e8000, scope=1) at
monet_interpreter.mx:1775
50 0x00662600 in interpret (stk=3, lt=0x9c7b0e8,
res=0xa0e8000) at monet_interpreter.mx:755
51 0x00668e1c in interpret_seqblock (stk=3,
lt=0x9c7bb60, res=0xa0e8000, scope=0) at
monet_interpreter.mx:1775
52 0x00662600 in interpret (stk=3, lt=0x9c7bb60,
res=0xa0e8000) at monet_interpreter.mx:755
53 0x00661369 in interpret_str (stk=0,
buf=0xb2689008 "\n\n MAIN MIL QUERY\n\n{\n var
err, ws := int(nil);\n err := CATCH({ws :=
create_ws();\nvar loop000 :=
bat(void,oid,1).seqbase(0@0).insert(0@0,
1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\n"..., res=0xa0e8000) at
monet_interpreter.mx:245
54 0x0065fed7 in monet_eval (
mil_script=0xb2689008 "\n\n MAIN MIL QUERY\n\n{\n
var err, ws := int(nil);\n err := CATCH({ws :=
create_ws();\nvar loop000 :=
bat(void,oid,1).seqbase(0@0).insert(0@0,
1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\n"..., ret_type=0xb377488c)
at monet.mx:592
55 0x0065ffe7 in monet_exec (
mil_script=0xb2689008 "\n\n MAIN MIL QUERY\n\n{\n
var err, ws := int(nil);\n err := CATCH({ws :=
create_ws();\nvar loop000 :=
bat(void,oid,1).seqbase(0@0).insert(0@0,
1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\n"...) at monet.mx:627
56 0x0076601e in CMDxquery (mode=0x959a5d0 "dm-mapi",
xquery=0x0) at pathfinder.mx:828
57 0x00766664 in CMDxquery_server (stk=2,
lt=0x959a6a9, res=0xb3774a40) at pathfinder.mx:971
58 0x00662bc0 in interpret (stk=2, lt=0x9736cf8,
res=0xb3774a40) at monet_interpreter.mx:845
59 0x00675ed3 in handleRequest (t=0x140909c,
q=0x94d51b0, res=0xb3774a40) at monet_queue.mx:533
60 0x006762ae in doRequest (t=0x140909c,
preference=0x0) at monet_queue.mx:559
61 0x006ac54b in monetInterpreter (status=0x6b3fe8) at
monet_process.mx:111
---Type <return> to continue, or q <return> to quit---
62 0x0073698c in start_thread () from
/lib/tls/libpthread.so.0
63 0x001cf7da in clone () from /lib/tls/libc.so.6
(gdb)
## Comment 3384
Date: 2005-06-16 14:02:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Wouter,
I'm not sure, whether this will help, here, but you could try to
change the memory setting of MonetDB as described in bug
report 1221107 "XQuery: shred_doc does take too long for
1GB document"; you must execute these MIL commands
before calling `pfstart();`.
Stefan.
## Comment 3385
Date: 2005-06-16 14:46:28 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
The memory setting described in 1221107 did not solve the
problem.
I have lowered the priority of this bug, because the sample
query does not deserve a recommendation and i could not
reproduce with another query until now.
## Comment 3386
Date: 2005-11-25 01:09:47 +0100
From: @peterboncz
Logged In: YES
user_id=591107
wouter, can you supply me with this data file?
I can't find it; nor can I reproduce the bug.
## Comment 3387
Date: 2005-12-19 10:06:24 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / TOO LARGE
(and also not reproduced apparently, Wouter can you check
whether this bug can be closed?)
## Comment 3388
Date: 2006-11-25 04:20:02 +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 3389
Date: 2006-11-29 10:09:07 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
over-ruling "sf-robot":
re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet.
User (submitter) & developer (assignee),
please check, again.
## Comment 3390
Date: 2007-11-30 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 3391
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1218268 at http://sourceforge.net/support/tracker.php?aid=1218268
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: Bus Error | https://api.github.com/repos/MonetDB/MonetDB/issues/609/comments | 0 | 2020-11-30T08:45:03Z | 2024-06-28T13:35:21Z | https://github.com/MonetDB/MonetDB/issues/609 | 753,279,247 | 609 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-07 05:14:55 +0200
From: @MarcinZukowski
To: @njnes
Version: -- development
Last updated: 2007-02-20 10:29:46 +0100
## Comment 3376
Date: 2005-06-07 17:14:55 +0200
From: @MarcinZukowski
Take a look at this:
var x:=new(void,int).seqbase(0@0);
x.insert(nil,0).insert(nil,2).insert(nil,1);
var y:=new(int,chr);
y.insert(0,'0').insert(2,'2').insert(1,'1');
x.outerjoin(y).print();
h t name
oid chr type
-----------------
[ 0@0, 0 ]
[ 1@0, 2 ]
[ 2@0, 1 ]
As you can see, head in the outerjoin result is not
void-headed.
I'm pretty sure it used to be some time ago, so
something must have been changed.
If y's head is sorted, void is preserved, if that helps
## Comment 3377
Date: 2005-06-07 18:57:40 +0200
From: @njnes
Logged In: YES
user_id=43556
The outerjoin does keep void heads. But this requires
BAThkey(y). As this isn't kept in BUNins this fails. For
sorted heads this is checked, which explains why outerjoin
keeps voids when y's head is sorted.
## Comment 3378
Date: 2005-12-19 10:04:38 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / REJECTED
## Comment 3379
Date: 2005-12-19 18:09:45 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: POSTPONED / REMINDER:
although the bug report was rejected, we might want to add a
test to show/monitor the current behaviour (both, with y's
head sorted and unsorted)...
## Comment 3380
Date: 2006-12-20 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 3381
Date: 2006-12-20 14:53:55 +0100
From: @MarcinZukowski
Logged In: YES
user_id=607094
Originator: YES
Added a test, please close if appropriate.
## Comment 3382
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1216457 at http://sourceforge.net/support/tracker.php?aid=1216457
| outerjoin doesn\'t preserve void anymore | https://api.github.com/repos/MonetDB/MonetDB/issues/608/comments | 0 | 2020-11-30T08:44:59Z | 2024-06-28T13:35:20Z | https://github.com/MonetDB/MonetDB/issues/608 | 753,279,197 | 608 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-07 05:12:23 +0200
From: @njnes
To: @njnes
Version: -- development
Last updated: 2006-01-13 11:36:35 +0100
## Comment 3371
Date: 2005-06-07 17:12:23 +0200
From: @njnes
When a bats reverse gets named it is listed by
ls("substring") but not
by dir("substring"). Also the types are reverse in this
case.
(This is a follow up of the incorrect headers http://sourceforge.net/support/tracker.php?aid=1214372
## Comment 3372
Date: 2005-06-07 18:48:14 +0200
From: @njnes
Logged In: YES
user_id=43556
the ls/dir implementations did a like before the reverse
name bat replacement was done, ie they got lost.
For reverse bats the types are now also reversed
## Comment 3373
Date: 2005-12-19 10:03:24 +0100
From: @grobian
Logged In: YES
user_id=963970
https://sourceforge.net/tracker/index.php?func=detail&aid=1214372&group_id=56967&atid=482468
BugDay_2005-12-19, meltdown: TEST ADDED / NEED CHECK
MonetDB/tests/BugDay_2005-12-19_4.9.3/Tests/bat_reverse_named_ls_dir.SF-1216455.milS
I reopened this bug as a reminder that the output for the
added test should be checked. I don't have enough in-depth
knowledge to judge whether the output is correct (ls returns
nothing, dir returns all)
## Comment 3374
Date: 2006-01-13 23:36:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
Checked and approved by Niels:
"added reversed case and approved output"
## Comment 3375
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1216455 at http://sourceforge.net/support/tracker.php?aid=1216455
| bugs in ls/dir with reversed named bats | https://api.github.com/repos/MonetDB/MonetDB/issues/607/comments | 0 | 2020-11-30T08:44:56Z | 2024-06-27T11:04:45Z | https://github.com/MonetDB/MonetDB/issues/607 | 753,279,159 | 607 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-06 09:26:44 +0200
From: @yzchang
To: @sjoerdmullender
Version: -- development
Last updated: 2005-06-06 11:22:56 +0200
## Comment 3368
Date: 2005-06-06 09:26:44 +0200
From: @yzchang
Compilation of MonetDB failed after I have checked-out
the last version of all files. The following errors
have been given:
gcc -DHAVE_CONFIG_H -I. -I../../../../src/modules/plain
-I../../.. -I../../../../src/modules/plain
-I../../common -I../../gdk -I../../monet
-I/usr/src/linux-2.6.10-1.771_FC2/include
-I/usr/include/pcre -DLIBCOUNTERS -std=c99 -Wall -W -g
-DHWCOUNTERS -DHW_Linux -DHW_i686
-Werror-implicit-function-declaration -Werror
-Wno-format -Wno-unused-function -Wno-unused-label
-Wno-strict-aliasing -D_REENTRANT -c counters.c -fPIC
-DPIC -o .libs/lib_counters_la-counters.o
../../../../src/modules/plain/counters.mx:582:11:
invalid digit "8" in octal constant
../../../../src/modules/plain/counters.mx:582: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:582: error:
(near initialization for `P4_event[8].id0')
../../../../src/modules/plain/counters.mx:582:15:
invalid digit "8" in octal constant
../../../../src/modules/plain/counters.mx:582: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:582: error:
(near initialization for `P4_event[8].id1')
../../../../src/modules/plain/counters.mx:582: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:582: error:
(near initialization for `P4_event[8]')
../../../../src/modules/plain/counters.mx:583:11:
invalid digit "9" in octal constant
../../../../src/modules/plain/counters.mx:583: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:583: error:
(near initialization for `P4_event[9].id0')
../../../../src/modules/plain/counters.mx:583:15:
invalid digit "9" in octal constant
../../../../src/modules/plain/counters.mx:583: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:583: error:
(near initialization for `P4_event[9].id1')
../../../../src/modules/plain/counters.mx:583: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:583: error:
(near initialization for `P4_event[9]')
../../../../src/modules/plain/counters.mx:584: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:584: error:
(near initialization for `P4_event[10]')
../../../../src/modules/plain/counters.mx:585: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:585: error:
(near initialization for `P4_event[11]')
../../../../src/modules/plain/counters.mx:586: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:586: error:
(near initialization for `P4_event[12]')
../../../../src/modules/plain/counters.mx:587: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:587: error:
(near initialization for `P4_event[13]')
../../../../src/modules/plain/counters.mx:588: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:588: error:
(near initialization for `P4_event[14]')
../../../../src/modules/plain/counters.mx:589: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:589: error:
(near initialization for `P4_event[15]')
../../../../src/modules/plain/counters.mx:590: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:590: error:
(near initialization for `P4_event[16]')
../../../../src/modules/plain/counters.mx:591: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:591: error:
(near initialization for `P4_event[17]')
../../../../src/modules/plain/counters.mx:592: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:592: error:
(near initialization for `P4_event[18]')
../../../../src/modules/plain/counters.mx:593: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:593: error:
(near initialization for `P4_event[19]')
../../../../src/modules/plain/counters.mx:594: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:594: error:
(near initialization for `P4_event[20]')
../../../../src/modules/plain/counters.mx:595: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:595: error:
(near initialization for `P4_event[21]')
../../../../src/modules/plain/counters.mx:596: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:596: error:
(near initialization for `P4_event[22]')
../../../../src/modules/plain/counters.mx:597: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:597: error:
(near initialization for `P4_event[23]')
../../../../src/modules/plain/counters.mx:598: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:598: error:
(near initialization for `P4_event[24]')
../../../../src/modules/plain/counters.mx:599: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:599: error:
(near initialization for `P4_event[25]')
../../../../src/modules/plain/counters.mx:600: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:600: error:
(near initialization for `P4_event[26]')
../../../../src/modules/plain/counters.mx:601: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:601: error:
(near initialization for `P4_event[27]')
../../../../src/modules/plain/counters.mx:602: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:602: error:
(near initialization for `P4_event[28]')
../../../../src/modules/plain/counters.mx:603: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:603: error:
(near initialization for `P4_event[29]')
../../../../src/modules/plain/counters.mx:604: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:604: error:
(near initialization for `P4_event[30]')
../../../../src/modules/plain/counters.mx:605: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:605: error:
(near initialization for `P4_event[31]')
../../../../src/modules/plain/counters.mx:606: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:606: error:
(near initialization for `P4_event[32]')
../../../../src/modules/plain/counters.mx:607: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:607: error:
(near initialization for `P4_event[33]')
../../../../src/modules/plain/counters.mx:608: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:608: error:
(near initialization for `P4_event[34]')
../../../../src/modules/plain/counters.mx:609: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:609: error:
(near initialization for `P4_event[35]')
../../../../src/modules/plain/counters.mx:610: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:610: error:
(near initialization for `P4_event[36]')
../../../../src/modules/plain/counters.mx:611: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:611: error:
(near initialization for `P4_event[37]')
../../../../src/modules/plain/counters.mx:612: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:612: error:
(near initialization for `P4_event[38]')
../../../../src/modules/plain/counters.mx:613: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:613: error:
(near initialization for `P4_event[39]')
../../../../src/modules/plain/counters.mx:614: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:614: error:
(near initialization for `P4_event[40]')
../../../../src/modules/plain/counters.mx:615: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:615: error:
(near initialization for `P4_event[41]')
../../../../src/modules/plain/counters.mx:616: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:616: error:
(near initialization for `P4_event[42]')
../../../../src/modules/plain/counters.mx:617: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:617: error:
(near initialization for `P4_event[43]')
../../../../src/modules/plain/counters.mx:618: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:618: error:
(near initialization for `P4_event[44]')
../../../../src/modules/plain/counters.mx:619: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:619: error:
(near initialization for `P4_event[45]')
../../../../src/modules/plain/counters.mx:622: warning:
`struct perfctr_event_set' declared inside parameter list
../../../../src/modules/plain/counters.mx:622: warning:
its scope is only this definition or declaration, which
is probably not what you want
../../../../src/modules/plain/counters.mx: In function
`perfctr_event_set_count':
../../../../src/modules/plain/counters.mx:626: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:627: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:628: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx: At top level:
../../../../src/modules/plain/counters.mx:632: warning:
`struct perfctr_event_set' declared inside parameter list
../../../../src/modules/plain/counters.mx: In function
`perfctr_event_set_find':
../../../../src/modules/plain/counters.mx:634: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:635: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:636: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:637: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx: At top level:
../../../../src/modules/plain/counters.mx:717: warning:
`struct perfctr_cpu_control' declared inside parameter list
../../../../src/modules/plain/counters.mx: In function
`do_event_number':
../../../../src/modules/plain/counters.mx:719: error:
implicit declaration of function `perfctr_cpu_event_set'
../../../../src/modules/plain/counters.mx:719: error:
`PERFCTR_X86_INTEL_P4M3' undeclared (first use in this
function)
../../../../src/modules/plain/counters.mx:719: error:
(Each undeclared identifier is reported only once
../../../../src/modules/plain/counters.mx:719: error:
for each function it appears in.)
../../../../src/modules/plain/counters.mx:719: warning:
initialization makes pointer from integer without a cast
../../../../src/modules/plain/counters.mx:720: warning:
passing arg 1 of `perfctr_event_set_count' from
incompatible pointer type
../../../../src/modules/plain/counters.mx:721: warning:
passing arg 1 of `perfctr_event_set_find' from
incompatible pointer type
../../../../src/modules/plain/counters.mx:723: warning:
comparison between signed and unsigned
../../../../src/modules/plain/counters.mx:728: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:729: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:730: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:731: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:732: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:733: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:733: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:734: error:
dereferencing pointer to incomplete type
make[5]: *** [lib_counters_la-counters.lo] Error 1
make[5]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src/modules/plain'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src/modules/plain'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src/modules'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build'
make: *** [all] Error 2
## Comment 3369
Date: 2005-12-19 09:49:03 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / COMPILATION
## Comment 3370
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1215473 at http://sourceforge.net/support/tracker.php?aid=1215473
| Failed to compile MonetDB | https://api.github.com/repos/MonetDB/MonetDB/issues/606/comments | 0 | 2020-11-30T08:44:52Z | 2024-06-27T11:04:44Z | https://github.com/MonetDB/MonetDB/issues/606 | 753,279,109 | 606 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-04 07:33:00 +0200
From: @grobian
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-06-08 06:46:28 +0200
## Comment 3364
Date: 2005-06-04 19:33:00 +0200
From: @grobian
On Darwin 8.1.0 64-bits src/gdk/casts test fails
(significantly)
It seems it doesn't recognise nil values. See attached
html page from mTest.
## Comment 3365
Date: 2005-06-08 18:46:28 +0200
From: @njnes
Logged In: YES
user_id=43556
Seems this isn't a bug but a 64/32 bit MAX_int/lng etc
problem. The
test should probably be improved to not be dependend on MAX_*.
## Comment 3366
Date: 2005-12-19 09:48:20 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / ALREADY IN TESTWEB
MonetDB/src/gdk/casts
## Comment 3367
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1214885 at http://sourceforge.net/support/tracker.php?aid=1214885
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.
| Tests: MonetDB/src/gdk/casts on Darwin 8.1.0 | https://api.github.com/repos/MonetDB/MonetDB/issues/605/comments | 0 | 2020-11-30T08:44:50Z | 2024-06-28T07:36:41Z | https://github.com/MonetDB/MonetDB/issues/605 | 753,279,079 | 605 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-04 05:59:15 +0200
From: @grobian
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-06-07 01:37:12 +0200
## Comment 3360
Date: 2005-06-04 17:59:15 +0200
From: @grobian
/usr/bin/ld: warning -L: directory name (/sw/lib) does
not exist
ld: warning -L: directory name (/sw/lib) does not exist
ld: warning -L: directory name (/sw/lib) does not exist
libtool: install: warning: relinking `libstream.la'
ld: warning -L: directory name (/sw/lib) does not exist
this indicates somewhere the fink installation path for
binaries is hardcoded included. Since fink (debian for
OS X, with debian up-to-dateness) isn't needed at all
to compile MonetDB on OS X this (apparently harmless)
warning due to a hardcoded include should disappear.
## Comment 3361
Date: 2005-06-07 13:37:12 +0200
From: @njnes
Logged In: YES
user_id=43556
removed from monet.m4
## Comment 3362
Date: 2005-12-19 09:45:32 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / COMPILATION
## Comment 3363
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1214847 at http://sourceforge.net/support/tracker.php?aid=1214847
| ld warnings when compiling with Darwin 8.1.0 | https://api.github.com/repos/MonetDB/MonetDB/issues/604/comments | 0 | 2020-11-30T08:44:47Z | 2024-06-27T11:04:42Z | https://github.com/MonetDB/MonetDB/issues/604 | 753,279,054 | 604 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-04 05:06:28 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2005-06-08 11:38:37 +0200
## Comment 3348
Date: 2005-06-04 17:06:28 +0200
From: @grobian
It seems that DBD gets installed in the directory
/Network/Library/Perl/[version]/darwin-thread-multi-2level/DBD
This seems rather strange to me, as I wouldn't want to
install anything on the network. Instead I would like
to install it local, i.e. /Library for system-wide or
~/Library for user install.
The directory
/Library/Perl/[version]/darwin-thread-multi-2level
already exists on both Panther and Tiger OSX systems.
## Comment 3349
Date: 2005-06-06 17:11:30 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
The standard perl way to install a module is:
perl Makefile.PL
make
make test (optional)
make install
where it's up to ExtUtils::MakeMaker
<http://search.cpan.org/~mschwern/ExtUtils-MakeMaker/>
<http://search.cpan.org/~mschwern/ExtUtils-MakeMaker-
6.25/lib/ExtUtils/MakeMaker.pmmake_install>
to handle the complicated cases.
Dunno if the 'perl Makefile.PL && make && make install'
sequence is / could be integrated into one of the MonetDB
makefiles / install scripts, with a reasonable parameterised
make variable ($(MAKE) or - better - 'perl -V:make' if perl was
built with another make than MonetDB).
## Comment 3350
Date: 2005-06-06 23:25:51 +0200
From: @njnes
Logged In: YES
user_id=43556
The install directory is created using
PERL_LIBDIR=`"$PERL" -MConfig -e
'$x=$Config{installvendorarch}; $x =~
s|$Config{vendorprefix}/||; print $x;' 2>/dev/null`. On
drawin this is probably not the correct way.
## Comment 3351
Date: 2005-06-07 10:36:10 +0200
From: @njnes
Logged In: YES
user_id=43556
The problems seems to be on the perl end. The perl's
vendorprefix isn't a prefix for the perl installvendorarch
which I think it should. And also the configure scripts we
wrote expect this.
## Comment 3352
Date: 2005-06-07 10:43:26 +0200
From: @njnes
Logged In: YES
user_id=43556
Could this be a 32/64 bit problem. Ie are you compiling
MonetDB for 32bits and is the pcre lib in /usr/lib 32bits?
## Comment 3353
Date: 2005-06-07 15:54:48 +0200
From: @grobian
Logged In: YES
user_id=963970
I do not really see what pcre has to do with this, but with
64-bits configure apparently ignores my pcre and goes on.
With 32-bits it starts complaining on not being able to find
pcre. See other bug.
## Comment 3354
Date: 2005-06-07 16:01:10 +0200
From: @njnes
Logged In: YES
user_id=43556
So you are compiling for 32bits (as your 64 bit seems to
work). Could you do a file on /usr/lib/lib*pcre. Could also
send me the full configure output.
## Comment 3355
Date: 2005-06-07 16:07:22 +0200
From: @grobian
Logged In: YES
user_id=963970
I am NOT in this bug! This is bits-independent.
I'm just doing a make install and I see it installing files
in /Network, a place where it should *never* go.
Please refer to
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1214811&group_id=56967
for PCRE.
## Comment 3356
Date: 2005-06-07 16:36:35 +0200
From: @grobian
Logged In: YES
user_id=963970
I just noticed this in the configure output:
checking for perl... /usr/bin/perl
checking for /usr/bin/perl's include directory...
/System/Library/Perl/5.8.6/dar
win-thread-multi-2level/CORE
checking for /usr/bin/perl's library directory...
$prefix//Network/Library/Perl/
5.8.6/darwin-thread-multi-2level
Apart from that if the default prefix is /usr this doesn't
make any sense (/Network makes more sense) I am surprised by
this outcome. Observing the output of perl -V maybe someone
gets a clue (but it aparently is a Panther Perl on Tiger):
% perl -V
Summary of my perl5 (revision 5 version 8 subversion 6)
configuration:
Platform:
osname=darwin, osvers=8.0,
archname=darwin-thread-multi-2level
uname='darwin b28.apple.com 8.0 darwin kernel version
7.5.0: thu mar 3 18:48:46 pst 2005;
root:xnuxnu-517.99.13.obj~1release_ppc power macintosh powerpc '
config_args='-ds -e -Dprefix=/usr -Dccflags=-g -pipe
-Dldflags=-Dman3ext=3pm -Duseithreads -Duseshrplib'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef
useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define
usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cc', ccflags ='-g -pipe -fno-common -DPERL_DARWIN
-no-cpp-precomp -fno-strict-aliasing -I/usr/local/include',
optimize='-Os',
cppflags='-no-cpp-precomp -g -pipe -fno-common
-DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing
-I/usr/local/include'
ccversion='', gccversion='3.3 20030304 (Apple Computer,
Inc. build 1809)', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8,
byteorder=4321
d_longlong=define, longlongsize=8, d_longdbl=define,
longdblsize=8
ivtype='long', ivsize=4, nvtype='double', nvsize=8,
Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags
='-L/usr/local/lib'
libpth=/usr/local/lib /usr/lib
libs=-ldbm -ldl -lm -lc
perllibs=-ldl -lm -lc
libc=/usr/lib/libc.dylib, so=dylib, useshrplib=true,
libperl=libperl.dylib
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef,
ccdlflags=' '
cccdlflags=' ', lddlflags='-bundle -undefined
dynamic_lookup -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY USE_ITHREADS
USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
Locally applied patches:
23953 - fix for File::Path::rmtree CAN-2004-0452
security issue
33990 - fix for setuid perl security issues
Built under darwin
Compiled at Mar 20 2005 16:34:19
@INC:
/System/Library/Perl/5.8.6/darwin-thread-multi-2level
/System/Library/Perl/5.8.6
/Library/Perl/5.8.6/darwin-thread-multi-2level
/Library/Perl/5.8.6
/Library/Perl
/Network/Library/Perl/5.8.6/darwin-thread-multi-2level
/Network/Library/Perl/5.8.6
/Network/Library/Perl
/System/Library/Perl/Extras/5.8.6/darwin-thread-multi-2level
/System/Library/Perl/Extras/5.8.6
/Library/Perl/5.8.1
.
## Comment 3357
Date: 2005-06-08 23:38:37 +0200
From: @njnes
Logged In: YES
user_id=43556
We use the perls variable installvendorarch and
vendorprefix. Which is the default location for
distributions to put the addon for perl. The vendor* values
are used correctly so the observed install is correctly
going into the $prefix/$installvendorarch-$vendorprefix.
We could change to installsitearch and siteprefix which is
supposed to be the place were cpan (local
downloaded/installed) modules go. For now this isn't all
very important (as normally perl gets installed using the
steps described by steffen). So lets close this bug.
## Comment 3358
Date: 2005-12-19 09:44:52 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / INSTALLATION
## Comment 3359
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1214826 at http://sourceforge.net/support/tracker.php?aid=1214826
| DBD: installation path wrong on OSX Pather and Tiger | https://api.github.com/repos/MonetDB/MonetDB/issues/603/comments | 0 | 2020-11-30T08:44:44Z | 2024-06-28T07:36:41Z | https://github.com/MonetDB/MonetDB/issues/603 | 753,279,021 | 603 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-04 04:11:21 +0200
From: @grobian
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-06-07 10:46:23 +0200
## Comment 3342
Date: 2005-06-04 16:11:21 +0200
From: @grobian
when compiling MonetDB on a Mac OS X Tiger 10.4.1
system with libpcre installed, the following error occurs:
powerpc-apple-darwin8-gcc-4.0.0: /usr/lib/libpcre: No
such file or directory
make[5]: *** [lib_pcre.la] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
% /usr/lib/libpcr
libpcre.0.0.1.dylib* libpcre.la*
libpcreposix.dylib@
libpcre.0.dylib@ libpcreposix.0.0.0.dylib*
libpcreposix.la*
libpcre.dylib@ libpcreposix.0.dylib@
% ./bootstrap
using /usr/bin/glibtool and /usr/bin/glibtoolize.
automake 1.6.3 is 1.5 or newer. Good.
autoconf 2.59 is 2.57 or newer. Good.
libtool 1.5 is 1.4 or newer. Good.
Python 2.3.5 is 2.0.0 or newer. Good.
excerpt from configure:
checking for pcre-config... /usr/bin/pcre-config
checking for pcre >= 4.5... yes (found 5.0)
checking pcre.h usability... yes
checking pcre.h presence... yes
checking for pcre.h... yes
checking for pcre_compile in -lpcre... yes
## Comment 3343
Date: 2005-06-07 16:12:48 +0200
From: @njnes
Logged In: YES
user_id=43556
so your compiling for 32bits. Could you attach the full
output of your configure run and of file /usr/lib/libpcre*?
## Comment 3344
Date: 2005-06-07 16:37:49 +0200
From: @grobian
Logged In: YES
user_id=963970
% la /usr/lib/libpcre*
-rwxr-xr-x 1 root portage 65092 May 13 20:39
/usr/lib/libpcre.0.0.1.dylib
lrwxrwxrwx 1 root wheel 19 May 13 20:39
/usr/lib/libpcre.0.dylib -> libpcre.0.0.1.dylib
-rw-r--r-- 1 root wheel 88680 May 13 20:39
/usr/lib/libpcre.a
lrwxrwxrwx 1 root wheel 19 May 13 20:39
/usr/lib/libpcre.dylib -> libpcre.0.0.1.dylib
-rwxr-xr-x 1 root wheel 765 May 13 20:39
/usr/lib/libpcre.la
-rwxr-xr-x 1 root portage 14332 May 13 20:39
/usr/lib/libpcreposix.0.0.0.dylib
lrwxrwxrwx 1 root wheel 24 May 13 20:39
/usr/lib/libpcreposix.0.dylib -> libpcreposix.0.0.0.dylib
-rw-r--r-- 1 root wheel 6544 May 13 20:39
/usr/lib/libpcreposix.a
lrwxrwxrwx 1 root wheel 24 May 13 20:39
/usr/lib/libpcreposix.dylib -> libpcreposix.0.0.0.dylib
-rwxr-xr-x 1 root wheel 820 May 13 20:39
/usr/lib/libpcreposix.la
see configure.out.bz as attach for configure output
## Comment 3345
Date: 2005-06-07 22:46:23 +0200
From: @grobian
Logged In: YES
user_id=963970
It seemed that the installation of libpcre was not correct,
and as such not a MonetDB specific problem.
## Comment 3346
Date: 2005-12-19 09:43:36 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / COMPILATION
## Comment 3347
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1214811 at http://sourceforge.net/support/tracker.php?aid=1214811
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.
| Compilation on Darwin 8.1.0 with libpcre | https://api.github.com/repos/MonetDB/MonetDB/issues/602/comments | 0 | 2020-11-30T08:44:41Z | 2024-06-28T07:36:40Z | https://github.com/MonetDB/MonetDB/issues/602 | 753,278,989 | 602 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-03 06:47:21 +0200
From: @swingbit
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-06-07 01:56:46 +0200
## Comment 3332
Date: 2005-06-03 18:47:21 +0200
From: @swingbit
Consider the following join:
[oid,void] <join> [void,int]
they are void aligned and the result is a [oid,int] bat.
Here is the code, using the normal "join" and the
"leftjoin" from malalgebra.
module(malalgebra);
var id:=new(void,oid).seqbase(0@0).insert(nil,
0@0).insert(nil, 2@0);
var aa:=new(void,int).seqbase(0@0).insert(nil,
0).insert(nil, 2);
these two joins should be equivalent
var j:=join(id.reverse(), aa).rename("T_join");
var lj:=leftjoin(id.reverse(), aa).rename("T_leftjoin");
Now, look at the headers of the two results:
j.print();
-----------------
t h name
oid int type
-----------------
[ 0@0, 0 ]
[ 2@0, 2 ]
lj.print();
-----------------
h t name
oid int type
-----------------
[ 0@0, 0 ]
[ 2@0, 2 ]
It seems that the result of the "leftjoin" is correct,
whereas the result of the "join" has "h" and "t" swapped.
Now look at dir():
-----------------------------------------------------------------------------------------------------------------
name t t t heat
dirty status kind refcnt lrefcnt
name
str str str lng int
str str str int int
type
-----------------------------------------------------------------------------------------------------------------
[ "T_join", "int", "oid", 2, 0,
"dirty", "load", "tran", 0, 1
]
[ "T_leftjoin", "oid", "int", 2, 0,
"dirty", "load", "tran", 0, 1
]
First, the header labels: name, t, t, t, heat ...
Second, here the result of the join actually has the
types swapped!
## Comment 3333
Date: 2005-06-07 13:56:46 +0200
From: @njnes
Logged In: YES
user_id=43556
Indeed the header of the dir/ls output is incorrect. But the
rest is all fine. A rename doesn't change the hident/tident
of the bat. As sometimes a join is implemented as follows
(join (l,r) == reverse(r.reverse,l.reverse), which explain
the strange default hident/tident.
## Comment 3334
Date: 2005-06-07 16:09:23 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
I have to disagree with that decision.
I also have this problem and it is annoying.
And I believe end-users might be confused as well.
## Comment 3335
Date: 2005-06-07 16:16:31 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Even worse.
BATs with this 'strange' structure do not appear in
dir("string");
This caused me to waste two hours, since I couldn't find a
BAT and I thought it disappeared on the way, while
dir("enum") simply didn't show it.
## Comment 3336
Date: 2005-06-07 16:17:44 +0200
From: @njnes
Logged In: YES
user_id=43556
The hident and tident are logical names for the bat's head
and tail and can be set using roles and col_name ( sets the
tail). The default is h/t and if a bat is create and
reversed before its returned you get this t/h result, which
I think make perfect sense. Conclusion should be if you want
proper names above your bat prints you need to call roles or
col_name.
## Comment 3337
Date: 2005-06-07 16:26:32 +0200
From: @swingbit
Logged In: YES
user_id=883451
Niels,
I don't know if I understood correctly. Are you saying that
the following makes sense in a ls()?
[ "T_join", "int", "oid", ...]
[ "T_leftjoin", "oid", "int", ...]
To me the first line does not make sense at all, as it is a
[oid,int] bat, if I print it.
## Comment 3338
Date: 2005-06-07 16:33:15 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
One more thing:
dir("string") doesn't work for these 'strange' bats.
ls("string") however, does.
Maybe that helps.
## Comment 3339
Date: 2005-06-07 17:43:56 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Anothere amusing thing:
var x:=new(void,int).seqbase(0@0);
x.insert(nil,0).insert(nil,2).insert(nil,1);
x.print();
h t name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 2 ]
[ 2@0, 1 ]
x:=x.reverse().mark(0@0).reverse();
x.print();
t h name
void int type
-----------------
[ 0@0, 0 ]
[ 1@0, 2 ]
[ 2@0, 1 ]
Notice the subtle change in the 'name' row :)
## Comment 3340
Date: 2005-12-19 09:42:46 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: NO TEST / WONT FIX
## Comment 3341
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1214372 at http://sourceforge.net/support/tracker.php?aid=1214372
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.
| wrong BAT headers printing? | https://api.github.com/repos/MonetDB/MonetDB/issues/601/comments | 0 | 2020-11-30T08:44:38Z | 2024-06-28T07:36:40Z | https://github.com/MonetDB/MonetDB/issues/601 | 753,278,955 | 601 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-03 05:40:08 +0200
From: @yzchang
To: @njnes
Version: -- development
Last updated: 2005-06-03 07:27:02 +0200
## Comment 3325
Date: 2005-06-03 17:40:08 +0200
From: @yzchang
Compilation of MonetDB failed after I have checked-out
the last version of all files. The following errors
have been given:
gcc -DHAVE_CONFIG_H -I. -I../../../../src/modules/plain
-I../../.. -I../../../../src/modules/plain
-I../../common -I../../gdk -I../../monet
-I/usr/src/linux-2.6.10-1.771_FC2/include
-I/usr/include/pcre -DLIBCOUNTERS -std=c99 -Wall -W -g
-DHWCOUNTERS -DHW_Linux -DHW_i686
-Werror-implicit-function-declaration -Werror
-Wno-format -Wno-unused-function -Wno-unused-label
-Wno-strict-aliasing -D_REENTRANT -c counters.c -fPIC
-DPIC -o .libs/lib_counters_la-counters.o
../../../../src/modules/plain/counters.mx:582:11:
invalid digit "8" in octal constant
../../../../src/modules/plain/counters.mx:582: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:582: error:
(near initialization for `P4_event[8].id0')
../../../../src/modules/plain/counters.mx:582:15:
invalid digit "8" in octal constant
../../../../src/modules/plain/counters.mx:582: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:582: error:
(near initialization for `P4_event[8].id1')
../../../../src/modules/plain/counters.mx:582: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:582: error:
(near initialization for `P4_event[8]')
../../../../src/modules/plain/counters.mx:583:11:
invalid digit "9" in octal constant
../../../../src/modules/plain/counters.mx:583: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:583: error:
(near initialization for `P4_event[9].id0')
../../../../src/modules/plain/counters.mx:583:15:
invalid digit "9" in octal constant
../../../../src/modules/plain/counters.mx:583: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:583: error:
(near initialization for `P4_event[9].id1')
../../../../src/modules/plain/counters.mx:583: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:583: error:
(near initialization for `P4_event[9]')
../../../../src/modules/plain/counters.mx:584: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:584: error:
(near initialization for `P4_event[10]')
../../../../src/modules/plain/counters.mx:585: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:585: error:
(near initialization for `P4_event[11]')
../../../../src/modules/plain/counters.mx:586: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:586: error:
(near initialization for `P4_event[12]')
../../../../src/modules/plain/counters.mx:587: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:587: error:
(near initialization for `P4_event[13]')
../../../../src/modules/plain/counters.mx:588: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:588: error:
(near initialization for `P4_event[14]')
../../../../src/modules/plain/counters.mx:589: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:589: error:
(near initialization for `P4_event[15]')
../../../../src/modules/plain/counters.mx:590: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:590: error:
(near initialization for `P4_event[16]')
../../../../src/modules/plain/counters.mx:591: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:591: error:
(near initialization for `P4_event[17]')
../../../../src/modules/plain/counters.mx:592: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:592: error:
(near initialization for `P4_event[18]')
../../../../src/modules/plain/counters.mx:593: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:593: error:
(near initialization for `P4_event[19]')
../../../../src/modules/plain/counters.mx:594: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:594: error:
(near initialization for `P4_event[20]')
../../../../src/modules/plain/counters.mx:595: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:595: error:
(near initialization for `P4_event[21]')
../../../../src/modules/plain/counters.mx:596: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:596: error:
(near initialization for `P4_event[22]')
../../../../src/modules/plain/counters.mx:597: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:597: error:
(near initialization for `P4_event[23]')
../../../../src/modules/plain/counters.mx:598: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:598: error:
(near initialization for `P4_event[24]')
../../../../src/modules/plain/counters.mx:599: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:599: error:
(near initialization for `P4_event[25]')
../../../../src/modules/plain/counters.mx:600: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:600: error:
(near initialization for `P4_event[26]')
../../../../src/modules/plain/counters.mx:601: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:601: error:
(near initialization for `P4_event[27]')
../../../../src/modules/plain/counters.mx:602: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:602: error:
(near initialization for `P4_event[28]')
../../../../src/modules/plain/counters.mx:603: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:603: error:
(near initialization for `P4_event[29]')
../../../../src/modules/plain/counters.mx:604: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:604: error:
(near initialization for `P4_event[30]')
../../../../src/modules/plain/counters.mx:605: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:605: error:
(near initialization for `P4_event[31]')
../../../../src/modules/plain/counters.mx:606: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:606: error:
(near initialization for `P4_event[32]')
../../../../src/modules/plain/counters.mx:607: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:607: error:
(near initialization for `P4_event[33]')
../../../../src/modules/plain/counters.mx:608: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:608: error:
(near initialization for `P4_event[34]')
../../../../src/modules/plain/counters.mx:609: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:609: error:
(near initialization for `P4_event[35]')
../../../../src/modules/plain/counters.mx:610: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:610: error:
(near initialization for `P4_event[36]')
../../../../src/modules/plain/counters.mx:611: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:611: error:
(near initialization for `P4_event[37]')
../../../../src/modules/plain/counters.mx:612: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:612: error:
(near initialization for `P4_event[38]')
../../../../src/modules/plain/counters.mx:613: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:613: error:
(near initialization for `P4_event[39]')
../../../../src/modules/plain/counters.mx:614: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:614: error:
(near initialization for `P4_event[40]')
../../../../src/modules/plain/counters.mx:615: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:615: error:
(near initialization for `P4_event[41]')
../../../../src/modules/plain/counters.mx:616: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:616: error:
(near initialization for `P4_event[42]')
../../../../src/modules/plain/counters.mx:617: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:617: error:
(near initialization for `P4_event[43]')
../../../../src/modules/plain/counters.mx:618: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:618: error:
(near initialization for `P4_event[44]')
../../../../src/modules/plain/counters.mx:619: error:
initializer element is not constant
../../../../src/modules/plain/counters.mx:619: error:
(near initialization for `P4_event[45]')
../../../../src/modules/plain/counters.mx:622: warning:
`struct perfctr_event_set' declared inside parameter list
../../../../src/modules/plain/counters.mx:622: warning:
its scope is only this definition or declaration, which
is probably not what you want
../../../../src/modules/plain/counters.mx: In function
`perfctr_event_set_count':
../../../../src/modules/plain/counters.mx:626: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:627: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:628: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx: At top level:
../../../../src/modules/plain/counters.mx:632: warning:
`struct perfctr_event_set' declared inside parameter list
../../../../src/modules/plain/counters.mx: In function
`perfctr_event_set_find':
../../../../src/modules/plain/counters.mx:634: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:635: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:636: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:637: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx: At top level:
../../../../src/modules/plain/counters.mx:717: warning:
`struct perfctr_cpu_control' declared inside parameter list
../../../../src/modules/plain/counters.mx: In function
`do_event_number':
../../../../src/modules/plain/counters.mx:719: error:
implicit declaration of function `perfctr_cpu_event_set'
../../../../src/modules/plain/counters.mx:719: error:
`PERFCTR_X86_INTEL_P4M3' undeclared (first use in this
function)
../../../../src/modules/plain/counters.mx:719: error:
(Each undeclared identifier is reported only once
../../../../src/modules/plain/counters.mx:719: error:
for each function it appears in.)
../../../../src/modules/plain/counters.mx:719: warning:
initialization makes pointer from integer without a cast
../../../../src/modules/plain/counters.mx:720: warning:
passing arg 1 of `perfctr_event_set_count' from
incompatible pointer type
../../../../src/modules/plain/counters.mx:721: warning:
passing arg 1 of `perfctr_event_set_find' from
incompatible pointer type
../../../../src/modules/plain/counters.mx:723: warning:
comparison between signed and unsigned
../../../../src/modules/plain/counters.mx:728: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:729: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:730: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:731: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:732: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:733: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:733: error:
dereferencing pointer to incomplete type
../../../../src/modules/plain/counters.mx:734: error:
dereferencing pointer to incomplete type
make[5]: *** [lib_counters_la-counters.lo] Error 1
make[5]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src/modules/plain'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src/modules/plain'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src/modules'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export/scratch1/zhang/monetdb/MonetDB/build'
make: *** [all] Error 2
## Comment 3326
Date: 2005-06-03 17:47:18 +0200
From: @grobian
Logged In: YES
user_id=963970
I can confirm this.
/ufs/fabian/scratch/monet-current/MonetDB/src/modules/plain/counters.mx:582:4:
invalid digit "8" in octal constant
this I could "fix", but the rest was too much. It looks
like there is a file missing or something.
b.t.w. made a clean compile on this one, ie. rm -R
build-dir, de-bootstrap, cvs update, bootstrap, configure,
make install
## Comment 3327
Date: 2005-06-03 18:07:27 +0200
From: @grobian
Logged In: YES
user_id=963970
/ufs/fabian/scratch/monet-current/MonetDB/src/modules/plain/counters.mx:622:
warning: "struct perfctr_event_set" declared inside
parameter list
/ufs/fabian/scratch/monet-current/MonetDB/src/modules/plain/counters.mx:622:
warning: its scope is only this definition or declaration,
which is probably not what you want
## Comment 3328
Date: 2005-06-03 18:11:24 +0200
From: @grobian
Logged In: YES
user_id=963970
oops
## Comment 3329
Date: 2005-06-03 18:12:54 +0200
From: @grobian
Logged In: YES
user_id=963970
so. See two posts below. It still does not compile for me.
## Comment 3330
Date: 2005-12-19 11:48:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 3331
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1214335 at http://sourceforge.net/support/tracker.php?aid=1214335
| Failed to compile MonetDB | https://api.github.com/repos/MonetDB/MonetDB/issues/600/comments | 0 | 2020-11-30T08:44:34Z | 2024-06-27T11:04:38Z | https://github.com/MonetDB/MonetDB/issues/600 | 753,278,919 | 600 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-01 03:04:12 +0200
From: Steffen Goeldner <<sgoeldner>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-06-08 12:52:34 +0200
## Comment 3319
Date: 2005-06-01 15:04:12 +0200
From: Steffen Goeldner <<sgoeldner>>
Module pqueue is missing from the Windows binary
package (MonetDB-Installer-4.8.0.msi).
BTW: Why does sourceforge list it as .bin (MacBinary)?
## Comment 3320
Date: 2005-06-01 18:58:06 +0200
From: @grobian
Logged In: YES
user_id=963970
probably because that file type was entered (by accident).
An admin should change it to something else. Would it match
if it would be set to windows executable (.exe) or something?
## Comment 3321
Date: 2005-06-01 22:57:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Thanks for notifying the from file type info,. I just fixed
it: .msi (Windows installer).
The missing pqueue needs to be treated by Sjoerd once he's
back next week.
## Comment 3322
Date: 2005-06-08 12:52:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I have uploaded a new Windows installer (same version
number) with the two missing files (lib_pqueue.dll and
pqueue.mil) added. These are the only differences.
## Comment 3323
Date: 2005-12-19 11:48:12 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / PACKAGING
## Comment 3324
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1212701 at http://sourceforge.net/support/tracker.php?aid=1212701
| pqueue missing from MonetDB-Installer-4.8.0.msi | https://api.github.com/repos/MonetDB/MonetDB/issues/599/comments | 0 | 2020-11-30T08:44:32Z | 2024-06-27T11:04:37Z | https://github.com/MonetDB/MonetDB/issues/599 | 753,278,889 | 599 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-06-01 11:59:23 +0200
From: Steffen Goeldner <<sgoeldner>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2006-12-04 09:13:32 +0100
## Comment 3308
Date: 2005-06-01 11:59:23 +0200
From: Steffen Goeldner <<sgoeldner>>
OS: Windows 2000
Compiler: MS VC++ Toolkit 2003
Parser tools: UnxUtils
After startup, Mserver uses 7 file handles:
>handle -s -p Mserver
Handle v3.02
Copyright (C) 1997-2005 Mark Russinovich
Sysinternals - www.sysinternals.com
Handle type summary:
Desktop : 1
Directory : 2
Event : 21
File : 7
Key : 6
Port : 1
Section : 2
Semaphore : 44
Thread : 11
WindowStation : 2
After connect/disconnect a mapi client, Mserver
uses 9 file handles:
Desktop : 1
Directory : 2
Event : 23
File : 9
Key : 6
Port : 1
Section : 2
Semaphore : 45
Thread : 12
WindowStation : 2
Additional file handles are:
270: File \Device\Tcp
274: File \Device\Afd\Endpoint
## Comment 3309
Date: 2005-06-01 15:59:41 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
By the way: Often, I can cross the magic limit of 256 handles
(in sum), but sometimes not. If not, then Mserver stops with:
!FATAL: Your disk seems to be full, exiting ...
## Comment 3310
Date: 2005-06-03 14:20:45 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
Evidence suggests that we have to use closesocket()
instead of close() on Windows:
<http://www.google.de/search?
as_epq=closesocket+instead+of+close>
<http://msdn.microsoft.com/library/en-
us/winsock/winsock/renamed_functions_2.asp?frame=no>
Using closesocket() in socket_close() (stream.mx)
seems to fix the leak.
Of course, we'll need an ifdef and I found one in
/src/mapi/mapi.mx:
ifdef NATIVE_WIN32
define s_close(s) closesocket(s)
else
define s_close(s) close(s)
endif
(whereas s_close() is never used).
## Comment 3311
Date: 2005-06-06 16:55:48 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
The socket leak is fixed after Niels' checkin:
Desktop : 1
Directory : 2
Event : 23
File : 7
Key : 6
Port : 1
Section : 2
Semaphore : 45
Thread : 13
WindowStation : 2
Event, Semaphore and Thread handles still increase, but
that's another story.
## Comment 3312
Date: 2005-06-07 23:29:47 +0200
From: @njnes
Logged In: YES
user_id=43556
The new mapi api starts a fixed set op client interpreter
threads. So it is indeed very strang that the number of
threads increases with each mapi client connect. Could you
verify that after some large number (say 256) clients indeed
the number of threads is some constant + 256 or do the
threads get reused?
## Comment 3313
Date: 2005-06-08 11:16:17 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
FOR /L %i IN (1,1,1100) DO bin\MapiClient.exe -c
etc\MonetDB.conf -s quit();
Handle type summary:
Desktop : 1
Directory : 2
Event : 1122
File : 7
Key : 6
Port : 1
Section : 2
Semaphore : 1144
Thread : 1112
WindowStation : 2
## Comment 3314
Date: 2005-06-10 15:56:01 +0200
From: Steffen Goeldner <<sgoeldner>>
Logged In: YES
user_id=1174087
I think, this bug can be closed.
I'll submit a separate bug report for the thread handle leak.
## Comment 3315
Date: 2005-12-19 11:47:24 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / POSTPONED
Windows specific issue that's hard to reproduce via Mtest...
## Comment 3316
Date: 2006-12-04 21:13:32 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Socket leak bug is fixed (long time ago) and tested by the smack tests.
there are no thread tests. We close this bug as its to windows specific and no new reports about
this problem exist.
## Comment 3317
Date: 2006-12-04 21:18:19 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Socket leak bug is fixed (long time ago) and tested by the smack tests.
there are no thread tests. We close this bug as its to windows specific and no new reports about
this problem exist.
## Comment 3318
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1212599 at http://sourceforge.net/support/tracker.php?aid=1212599
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.
| Socket handle leak (Win32) | https://api.github.com/repos/MonetDB/MonetDB/issues/598/comments | 0 | 2020-11-30T08:44:28Z | 2024-06-27T11:04:36Z | https://github.com/MonetDB/MonetDB/issues/598 | 753,278,858 | 598 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-31 01:04:57 +0200
From: Arjen van der Meijden <<arjenm>>
To: @njnes
Version: -- development
Last updated: 2005-05-31 07:39:59 +0200
## Comment 3303
Date: 2005-05-31 13:04:57 +0200
From: Arjen van der Meijden <<arjenm>>
This minimal-testcase illustrates the failure I
encountered in a select ... from ... where ID IN
(select ID from ...):
QUERY = select 1 in ('1', '2', '3');
ERROR = !ERROR: interpret: no matching MIL operator to
'[exist](BAT[sht,void], sht)'.
!MAYBE YOU MEAN:
! exist(BAT[any::1,any::2], any::1,
any::2) : bit
! exist(BAT[any::1,any], any::1) : bit
On a related note:
QUERY = select 1 IN ((select 1 union select 2));
ERROR = !syntax error, unexpected UNION, expecting ')'
in: "select 1 in ((select 1 union select"
Isn't that correct SQL?
And:
MAPI = monetdb@localhost:45123
QUERY = select 1 IN ((select * from (select 1 union
select 2) as data));
ERROR = !ERROR: interpret: no matching MIL operator to
'append(BAT[void,sht], BAT[void,oid])'.
!MAYBE YOU MEAN:
! append(BAT[oid,void], BAT[oid,void]) :
BAT[oid,void]
! append(BAT[void,any::1],
BAT[oid,any::1]) : BAT[void,any::1]
! append(BAT[void,any::1],
BAT[void,any::1]) : BAT[void,any::1]
! append(BAT[void,any::1], any::1) :
BAT[void,any::1]
! append(BAT[oid,any::1],
BAT[oid,any::1]) : BAT[oid,any::1]
! append(BAT[oid,any::1], any::1) :
BAT[oid,any::1]
## Comment 3304
Date: 2005-05-31 13:37:04 +0200
From: @grobian
Logged In: YES
user_id=963970
monetdb-> select 1 in (select * from (select 1 union select
2) as a);
Error: ERROR: interpret: no matching MIL operator to
'outerjoin(sht, BAT[oid,void])'.
MAYBE YOU MEAN:
outerjoin(BAT[any::1,any::2], BAT[any::2,any::3]) :
BAT[any::1,any::3]
outerjoin(BAT[any::1,any::2], BAT[any::2,any::3],
lng) : BAT[any::1,any::3]
strange that I get a different error message...
## Comment 3305
Date: 2005-05-31 19:39:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Fixed both bugs. The code for select * in (selec *) was very
wrong.
Your second query fails indeed correctly because SQL
requires you to name the subquery.
## Comment 3306
Date: 2005-12-19 11:45:39 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/in_operator.SF-1211925.*
## Comment 3307
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1211925 at http://sourceforge.net/support/tracker.php?aid=1211925
| IN-operator fails with MIL-errors | https://api.github.com/repos/MonetDB/MonetDB/issues/597/comments | 0 | 2020-11-30T08:44:25Z | 2024-06-27T11:04:35Z | https://github.com/MonetDB/MonetDB/issues/597 | 753,278,816 | 597 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-31 12:37:40 +0200
From: Arjen van der Meijden <<arjenm>>
To: @njnes
Version: -- development
Last updated: 2005-07-15 11:24:53 +0200
## Comment 3298
Date: 2005-05-31 12:37:40 +0200
From: Arjen van der Meijden <<arjenm>>
These works ok and result in an integer with the value
1117422000:
select cast(1117422000 as integer);
select cast('1117422000' as integer);
This one however fails:
select cast(cast(1117422000 as bigint) as integer);
ERROR = !ERROR: lng_2_int: too many digits (10 > 9)
!ERROR: lng_2_int: operation failed.
The maximum value of int (2^32 - 1) is a 10-digit
number starting with a 2. So the 9-digit limit is a
somewhat incorrect.
## Comment 3299
Date: 2005-05-31 13:32:42 +0200
From: @grobian
Logged In: YES
user_id=963970
You are somewhat correct here, however the SQL standard does
not prescribe any minimums for numeric types. The only real
requirement is that smallint <= integer <= bigint (which
actually means they can all be of the same size!)
There is a legacy reason why the precision is still used
here. This behaviour is indeed undesirable, but not incorrect.
## Comment 3300
Date: 2005-07-15 11:24:53 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed in cvs head version
## Comment 3301
Date: 2005-12-19 11:41:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/cast_bigint_to_int.SF-1211903.*
## Comment 3302
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1211903 at http://sourceforge.net/support/tracker.php?aid=1211903
| Cannot cast a bigint to integer if it should fit | https://api.github.com/repos/MonetDB/MonetDB/issues/596/comments | 0 | 2020-11-30T08:44:22Z | 2024-06-27T11:04:34Z | https://github.com/MonetDB/MonetDB/issues/596 | 753,278,787 | 596 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-30 04:38:51 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-01-19 11:45:14 +0100
## Comment 3293
Date: 2005-05-30 16:38:51 +0200
From: Wouter Alink <<alink>>
When typing (using the Windows Build pf-0.8.0):
shred_doc("c:\\Documents and
Settings\does_not_exist.xml","does_not_exist.xml");
in a MIL session, Mserver crashes.
I guess this has something to do with escaping,
because typing:
shred_doc("c:\\n.xml","n.xml");
returns:
I/O warning : failed to load external
entity "file:///cA/n.xml"
shred:xmlCreateURLParserCtxt("c:\n.xml") failed
MAPI = anonymous@localhost:50000
QUERY = shred_doc("c:\\n.xml","n.xml");
ERROR = !ERROR: CMDshred2bats: operation failed.
## Comment 3294
Date: 2005-12-19 11:35:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / FAILURE
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/shred_doc_with_space.SF-1211372.*
spaces and/or '\' in shred_doc's pathname make Mserver crash
also on Linux
## Comment 3295
Date: 2006-01-19 23:45:12 +0100
From: @drstmane
Logged In: YES
user_id=572415
This appears to be a bug in xmlCreateFileParserCtxt() &
xmlCreateURLParserCtxt() of libxml2 < 2.6.22: I occurs on
all out testing platform (with libxml2 between 2.6.7 ans
2.6.20), except on Gentoo 1.6.14 which has libxml2 2.6.22:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Gentoo1.6.14/tests_BugDay_2005-12-19_0.9.3/shred_doc_with_space.SF-1211372.out.00.html
Hence, we just wait until the other platform get a newer
libxml2 as well...
## Comment 3296
Date: 2006-01-21 13:15:52 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Not invalid. This was really a bug in our code.
The problem was, the error message generated by xmllib
contains the %-escaped (url-ified) file name. So,
"Documents and Settings" becomes
"Documents%20and%20Settings". This string is given
unaltered to stream_printf and is interpreted as format
string. %20a and %20S happen to mean something (look it up).
## Comment 3297
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1211372 at http://sourceforge.net/support/tracker.php?aid=1211372
| PF: Mserver crashes on space and/or '\' in shred_doc path | https://api.github.com/repos/MonetDB/MonetDB/issues/595/comments | 0 | 2020-11-30T08:44:19Z | 2024-06-27T11:04:33Z | https://github.com/MonetDB/MonetDB/issues/595 | 753,278,766 | 595 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-30 03:34:53 +0200
From: Arjen van der Meijden <<arjenm>>
To: @njnes
Version: -- development
Last updated: 2005-12-21 10:43:28 +0100
## Comment 3286
Date: 2005-05-30 15:34:53 +0200
From: Arjen van der Meijden <<arjenm>>
When executing this query:
select CASE WHEN 1=1 THEN 1 ELSE NULL END;
I get the error:
ERROR = !syntax error, unexpected NULLX in: "select
case when 1=1 then null"
Of course this testcase is not very useful, but the
general case is used as "more advanced NULLIF()".
Workaround is to return something (-1 orso) and to wrap
NULLIF around the CASE.
## Comment 3287
Date: 2005-05-30 16:02:01 +0200
From: @grobian
Logged In: YES
user_id=963970
miraculously enough this does work:
monetdb-> select CASE WHEN 1=1 THEN 1 else cast(null as
char) end;
+---------------------------+
| ifthenelse_=_single_value |
+===========================+
| 1 |
+---------------------------+
1 row
while the more 'what you would expect one' fails:
monetdb-> select CASE WHEN 1=1 THEN 1 else cast(null as int)
end;
Error: operator: ifthenelse unknown
## Comment 3288
Date: 2005-05-31 19:55:12 +0200
From: @njnes
Logged In: YES
user_id=43556
Fixed the 'else NULL' bug. The last case fails because there
are no implicite
conversions for the types 1(smallint) and int cast(null as
int) (int).
## Comment 3289
Date: 2005-12-19 11:09:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / PLEASE CHECK OUTPUT!
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/NULL_in_CASE.SF-1211335.*
Niels, Fabian,
could (one of) you please check, whether the error messages
are indeed correct/expected?
## Comment 3290
Date: 2005-12-19 11:16:50 +0100
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-12-19, meltdown: TEST MODIFIED / FAILED
reopened this bug.
## Comment 3291
Date: 2005-12-21 22:42:27 +0100
From: @njnes
Logged In: YES
user_id=43556
fixed, added missing type check
## Comment 3292
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1211335 at http://sourceforge.net/support/tracker.php?aid=1211335
| NULL is not allowed in CASE | https://api.github.com/repos/MonetDB/MonetDB/issues/594/comments | 0 | 2020-11-30T08:44:16Z | 2024-06-27T11:04:32Z | https://github.com/MonetDB/MonetDB/issues/594 | 753,278,729 | 594 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-29 03:48:46 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-29 10:01:00 +0200
## Comment 3282
Date: 2005-05-29 15:48:46 +0200
From: Wouter Alink <<alink>>
The following error occurs:
ERROR: merged_union: tail of first BAT must be sorted.
when running the query:
for $t in doc("voc.xml")//voyage
let $p := zero-or-one($t/rightpage/particulars/text())
where (contains($p,"wrecked") or contains($p,"sunk"))
return $t/leftpage/boatname
if i leave out one of the where clauses or use "and"
instead of "or", it works fine
## Comment 3283
Date: 2005-05-29 22:01:00 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
added missing check_order()
-- now fixed
## Comment 3284
Date: 2005-12-19 09:32:40 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / SUCCESS
tests/WebSite/Tests/contains_or_bug.SF-1210791.xq
## Comment 3285
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210791 at http://sourceforge.net/support/tracker.php?aid=1210791
| XQuery: "contains" and "or" | https://api.github.com/repos/MonetDB/MonetDB/issues/593/comments | 0 | 2020-11-30T08:44:13Z | 2024-06-27T11:04:31Z | https://github.com/MonetDB/MonetDB/issues/593 | 753,278,699 | 593 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-29 02:44:18 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-29 10:00:54 +0200
## Comment 3278
Date: 2005-05-29 14:44:18 +0200
From: Wouter Alink <<alink>>
Another merge_union thingy...
The script below causes the error:
ERROR: merged_union: BAT 6 must have the same size as
BAT 2.
if i either leave out the 'distinct-values' or the
'text { ", " }', the error does not appear.
<ship>
<harbours> {
distinct-values(
doc("voc.xml")//voyage[leftpage/boatname="ZEELANDIA"]//harbour
)
} </harbours>
<voyages> {
for $t in
doc("voc.xml")//voyage[leftpage/boatname="ZEELANDIA"]
return
<voyage> {
$t/leftpage/departure/text(), text { ", " },
$t/leftpage/harbour/text()
} </voyage>
} </voyages>
</ship>
## Comment 3279
Date: 2005-05-29 22:00:54 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
same problem as http://sourceforge.net/support/tracker.php?aid=1210748
-- now fixed
## Comment 3280
Date: 2005-12-19 09:24:50 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / REDUNDANT
A test for it exists,
tests/WebSite/Tests/distinct_values_bug.SF-1210748
## Comment 3281
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210767 at http://sourceforge.net/support/tracker.php?aid=1210767
| XQuery: merge_union again | https://api.github.com/repos/MonetDB/MonetDB/issues/592/comments | 0 | 2020-11-30T08:44:10Z | 2024-06-27T11:04:30Z | https://github.com/MonetDB/MonetDB/issues/592 | 753,278,668 | 592 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-29 02:18:58 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-06-13 04:14:30 +0200
## Comment 3273
Date: 2005-05-29 14:18:58 +0200
From: Wouter Alink <<alink>>
i seem to not be able to sort the result when i'm using
a 'where' clause.
for $t in <a>
<b>Cees</b>
<b>Beer</b>
<b>Aap</b>
</a>//b
where $t = "Cees" or $t = "Aap"
order by $t
return $t
returns:
<b>Cees</b>,
<b>Aap</b>
if i leave out the where clause, it'll return the expected:
<b>Aap</b>,
<b>Beer</b>,
<b>Cees</b>
## Comment 3274
Date: 2005-05-29 21:56:48 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Here the reason is the 'where' clause in between the 'for'
and the 'order by' clause. The problem occurs, since 'where'
clauses are internally translated into 'if-then-else'
expression, which created a new scope. The 'order by'
clause then uses the wrong scope.
This problem can be avoided, if the query is reformulated in
such a way, that the 'order by' directly follows the 'for'
expression. E.g.:
for $t in <a>
<b>Cees</b>
<b>Beer</b>
<b>Aap</b>
</a>//b
order by $t
return if ($t = "Cees" or $t = "Aap") then $t else ()
## Comment 3275
Date: 2005-05-29 22:40:51 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
for $t in doc("voc.xml")//voyage
let $p := zero-or-one($t/rightpage/particulars/text())
where not($t//destination/arrival)
and (contains($p,"wrecked")
or contains($p,"sunk"))
order by $t/leftpage/boatname/text()
return
element { "boat" } {
element { "name" } { $t/leftpage/boatname/text() },
text { ": " },
element { "description" } {
$t/rightpage/particulars/text() }
}
## Comment 3276
Date: 2005-12-19 09:18:59 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / SUCCESS
tests/BugDay_2005-12-19_0.9.3/Tests/where_orderby.SF-1210757.xq
## Comment 3277
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210757 at http://sourceforge.net/support/tracker.php?aid=1210757
| XQuery: order awareness + 'WHERE' clause | https://api.github.com/repos/MonetDB/MonetDB/issues/591/comments | 0 | 2020-11-30T08:44:08Z | 2024-06-27T11:04:29Z | https://github.com/MonetDB/MonetDB/issues/591 | 753,278,637 | 591 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-29 01:45:25 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-29 10:00:47 +0200
## Comment 3269
Date: 2005-05-29 13:45:25 +0200
From: Wouter Alink <<alink>>
i'm still running into error-messages:
When querying:
distinct-values(doc("voc.xml")//master[starts-with(./string(),"A")])
it returns the following error:
ERROR: CTrefine: both BATs must have the same
cardinality and their heads must form a 1-1 match.
when i omit "distinct-values" the error does not
appear, it also doesn't appear when using the following
query:
distinct-values(
<a><b><master>Aap</master>
<master>Beer</master></b></a>//master
[starts-with(./string(),"A")]
)
i attached the voc.xml dataset (gzipped)
## Comment 3270
Date: 2005-05-29 22:00:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
forgot to cope with multiple results in iteration (in typed-value
())
-- now fixed
## Comment 3271
Date: 2005-12-19 09:10:02 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / SUCCESS
Added a test script to
tests/WebSite/Tests/distinct_values_bug.SF-1210748.xq (in this
test directory the voc data is allready loaded)
## Comment 3272
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210748 at http://sourceforge.net/support/tracker.php?aid=1210748
| XQuery: distinct-values | https://api.github.com/repos/MonetDB/MonetDB/issues/590/comments | 0 | 2020-11-30T08:44:04Z | 2024-06-27T11:04:28Z | https://github.com/MonetDB/MonetDB/issues/590 | 753,278,594 | 590 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-29 01:33:51 +0200
From: Wouter Alink <<alink>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-06-06 11:33:04 +0200
## Comment 3265
Date: 2005-05-29 13:33:51 +0200
From: Wouter Alink <<alink>>
The parser complains about:
<x> {
element { "a" } { "aap" }
} </x>
with:
syntax error, unexpected "/", expecting QName on line 3
(next token is `/')
while it doesn't complain about the query:
<x> {
text { "aap" }
} </x>
## Comment 3266
Date: 2005-06-06 11:33:04 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
This was a bit a tricky one. I was hoping I'd never need to touch the lexer's
state machine again after I had written it...
I hope that my fix actually (just) fixes the problem and doesn't break the
code otherwise. But all tests ran fine here.
Thanks for the report.
## Comment 3267
Date: 2005-11-09 17:02:31 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
tests/BugDay_2005-11-09_0.9.3/Tests/element_creation.SF-1210743.xq
## Comment 3268
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210743 at http://sourceforge.net/support/tracker.php?aid=1210743
| XQuery: parser error when creating elements | https://api.github.com/repos/MonetDB/MonetDB/issues/589/comments | 0 | 2020-11-30T08:44:01Z | 2024-06-27T11:04:27Z | https://github.com/MonetDB/MonetDB/issues/589 | 753,278,565 | 589 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-27 11:18:44 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-28 10:59:40 +0200
## Comment 3260
Date: 2005-05-27 23:18:44 +0200
From: Wouter Alink <<alink>>
I get the following error:
ERROR: child(4): tail of item must be sorted!
when i try to run:
let $f := doc("HelloWorld.xml")/doc
for $g in $f/greet/text()
for $l in $f/location/text()
return
<sentence> {
$g,$l
} </sentence>
in which HelloWorld.xml:
<?xml version="1.0" encoding="utf-8"?>
<doc>
<greet kind="informal">Hi</greet>
<greet kind="casual">Hello</greet>
<location kind="global">World</location>
<location kind="local">Amsterdam</location>
</doc>
i am not sure if the bug is in my query or in pathfinder...
by the way; the error is not raised when the query is
rewritten as:
let $f := doc("HelloWorld.xml")/doc
for $g in $f/greet
for $l in $f/location
return
<sentence> {
$g/text(),$l/text()
} </sentence>
## Comment 3261
Date: 2005-05-28 10:27:04 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This one is fixed and already checked in
## Comment 3262
Date: 2005-05-28 10:59:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed/finished JanR'\''s fix in CVS:
order needs to be or-ed with 1 to set the lowest bit
without touching the other bits.
## Comment 3263
Date: 2005-11-09 16:49:40 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
./tests/BugsViaSourgeforce/Tests/ID.1210173-1.xq
## Comment 3264
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210173 at http://sourceforge.net/support/tracker.php?aid=1210173
| XQuery: child(4): tail of item must be sorted! | https://api.github.com/repos/MonetDB/MonetDB/issues/588/comments | 0 | 2020-11-30T08:43:58Z | 2024-06-27T11:04:26Z | https://github.com/MonetDB/MonetDB/issues/588 | 753,278,519 | 588 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-27 08:55:14 +0200
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2005-05-28 02:04:26 +0200
## Comment 3254
Date: 2005-05-27 20:55:14 +0200
From: @drstmane
Since today's (Friday, May 27 2005) changes,
this query:
<doc>
!this is a test
</doc>
results in this (incorrect) output (with MapiClient
-lxquer -sxml):
stdout:
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<doc>
</doc>
</XQueryResult>
stderr:
this is a test
Apparently, the text line staring with a '!' is treated
as an error message somewhere in the process.
Is there a '='-prefix missing somewhere in the output
that is sent via MAPI?
See also the outcome of test
tests/BugsViaSourgeforce/Tests/ID.1206985.xq .
I assign this to JanF, but everybody else who sees this
before Sunday evening is welcome to have a look and fix
it if possible!
## Comment 3255
Date: 2005-05-27 21:12:25 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
This is a regression. Before Jan F's fix for escaping < and
& with entities this worked. It worked because I had fixed
handle_characters to emit an '=' after each newline when
mapiMode is set. That code is now gone.
## Comment 3256
Date: 2005-05-28 00:12:40 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I already said this Mapi stuff was a major headache for me
when concerning escapes. I'm currently working at home and
cannot check-in updates from here. I'm not allowed into the
INF building in the weekend either.
The fix for this problem which works with me is to add an
extra condition on line 553 in runtime/serialize.mx (the line
above start--; ....
&& (src[end]!='\n')
This ensures the extra '='is printed in Mapi mode.
Hope this works. Otherwise I could try to show up at the
porters office on sunday with my passport and try to get into
the building.
## Comment 3257
Date: 2005-05-28 02:04:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
Indeed, this patch seems to fix the problem.
Fabian's checkin was just to late for the automatic nightly
testing,
but I just ran Mtest by hand, and test work as expected.
Hence, no need for JanF to "break into" UTwente on Sunday ;-)
## Comment 3258
Date: 2005-11-09 16:48:16 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
./tests/BugsViaSourgeforce/Tests/ID.1210086.xq
## Comment 3259
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1210086 at http://sourceforge.net/support/tracker.php?aid=1210086
| XQuery: text staring with '!' is treated as error message | https://api.github.com/repos/MonetDB/MonetDB/issues/587/comments | 0 | 2020-11-30T08:43:55Z | 2024-06-27T11:04:26Z | https://github.com/MonetDB/MonetDB/issues/587 | 753,278,478 | 587 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-27 12:49:06 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-05-27 01:36:40 +0200
## Comment 3249
Date: 2005-05-27 12:49:06 +0200
From: Jan Rittinger <<jan.rittinger>>
This is probably a little bit harder to fix, since it probably
needs modification in the rules of the parser -- if so we
should mark this bug invalid :)
> pf
<gt>></gt>,
<gt>></gt>
parse error, unexpected invalid_character, expecting "</"
on line 1 (next token is `>')
parse error: XQuery parsing failed
## Comment 3250
Date: 2005-05-27 12:52:32 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
The same problem arises in attribute construction code:
attribute gt {">"}
works while the following doesn't
> pf
<attributes gt="10 > 1"/>
parse error, unexpected invalid_character, expecting """ on
line 1 (next token is `>')
parse error: XQuery parsing failed
## Comment 3251
Date: 2005-05-27 13:36:40 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fix will be in CVS in a minute.
## Comment 3252
Date: 2005-11-09 16:41:18 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
tests/BugDay_2005-11-09_0.9.3/Tests/gt.SF-1209749.xq
## Comment 3253
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1209749 at http://sourceforge.net/support/tracker.php?aid=1209749
| XQuery: parser doesn't accept '>' in element content | https://api.github.com/repos/MonetDB/MonetDB/issues/586/comments | 0 | 2020-11-30T08:43:53Z | 2024-06-27T11:04:25Z | https://github.com/MonetDB/MonetDB/issues/586 | 753,278,447 | 586 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-27 12:44:50 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-05-27 01:36:07 +0200
## Comment 3245
Date: 2005-05-27 12:44:50 +0200
From: Jan Rittinger <<jan.rittinger>>
> pf
"'"
parse error: error in entity reference: `'"'
## Comment 3246
Date: 2005-05-27 13:36:07 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fix will be in CVS in a minute.
## Comment 3247
Date: 2005-11-09 16:28:28 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
BugsViaSourgeforce/Tests/ID.1209497.xq
## Comment 3248
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1209747 at http://sourceforge.net/support/tracker.php?aid=1209747
| XQuery: parser doesn't accept "'" | https://api.github.com/repos/MonetDB/MonetDB/issues/585/comments | 0 | 2020-11-30T08:43:50Z | 2024-06-27T11:04:24Z | https://github.com/MonetDB/MonetDB/issues/585 | 753,278,409 | 585 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-27 12:40:26 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-05-27 01:35:28 +0200
## Comment 3241
Date: 2005-05-27 12:40:26 +0200
From: Jan Rittinger <<jan.rittinger>>
>pf
"&"
parse error, unexpected invalid_character on line 1 (next
token is `"')
parse error: XQuery parsing failed
## Comment 3242
Date: 2005-05-27 13:35:24 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
This is correct behavior.
Note that the & character introduces character references also in literal
strings. (This is actually what Torsten had pointed out with his mail: There
are no \n, \t, etc. escape sequences in XQuery, only the &...; character
references.)
## Comment 3243
Date: 2005-11-09 16:24:54 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: RELEASED
reassign to wouter
## Comment 3244
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1209745 at http://sourceforge.net/support/tracker.php?aid=1209745
| XQuery: parser doesn't accept '&' in string | https://api.github.com/repos/MonetDB/MonetDB/issues/584/comments | 0 | 2020-11-30T08:43:48Z | 2024-06-28T07:36:40Z | https://github.com/MonetDB/MonetDB/issues/584 | 753,278,373 | 584 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-27 12:04:34 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2005-05-28 05:31:40 +0200
## Comment 3230
Date: 2005-05-27 00:04:34 +0200
From: Jan Rittinger <<jan.rittinger>>
<a><</a>
returns
<XQueryResult>
<a><</a>
</XQueryResult>
I think with the XML return mode we should again escape
such characters into entities - otherwise our output is not
wellformed anymore.
< <
> >
& &
" "
' '
## Comment 3231
Date: 2005-05-27 00:08:46 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Addition: The extension of this bug is of course Teggy's
remark about serializing non printable characters using char
refs.
## Comment 3232
Date: 2005-05-27 09:34:57 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I had a quick look at this one and this looks a bit hairy
because we need a different character escape function. I
used our regular escape routine but this one does too much.
For instance the query:
<a><
>
</a>
ends up as:
<XQueryResult>
<a><\n>\n</a>
</XQueryResult>
Furthermore Peter made a lot of Mapi adaptions in the escape
routines which make them quite trickey. I will try to
implement an extra flag in the escape routines which
indicate ONLY ENTITIES sould be escaped and
all other special chars should be ontouched.
## Comment 3233
Date: 2005-05-27 09:55:17 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I think for the release - like Stefan said - the char refs are not
that important.
The entities on the other side seem important to me since
otherwise our xml mode is no real xml mode anymore...
In my opinion it's enough if you fix only the entities until the
release (of course only if it's possible) -- meaning ID.1209497.
xq runs without errors.
## Comment 3234
Date: 2005-05-27 10:17:44 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Of course, strictly speaking, only & and < need to be
escaped. And in attribute values you need to escape the
quote that was used to quote the value. The others are
optional.
I.e. the two attributes have the same value:
<tag attr1=' "' ' attr2=" "' "/>
The test currently only tests for < (<) but should also
test for & (&).
Char refs are not important, as long as the character
encoding is correct: UTF-8.
## Comment 3235
Date: 2005-05-27 11:05:54 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Implemented the JUST-ENTITIES approach for node text and it
seems to work OK. Looks like a lot of ' are generated
in a lot of unexpected places. So I think an extra 20 tests
have to be approved. But I will not do this so you can have
a look if this is the desired output!
## Comment 3236
Date: 2005-05-27 12:56:43 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
In my opinion Sjoerd's suggestion sounds best - however it
won't hurt if we escape all entities.
MUST: " should be escaped in attributes
the current result of <attribute quot='"'/> is
<attribute quot="""/>, which is not wellformed XML
## Comment 3237
Date: 2005-05-27 14:36:39 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Made some new fixes and changed the following:
- Within node text only entities < > and & are
escaped.
- Text inside attribute-value quotes is now fully
escaped. Next improvement
would be to escape only the type of quotes which are
used as value quotes.
Hope this adresses the comments made by all. If this all
works I would consider the bug closed for now. For me the
broader entity char problem should be adressed after the
first release.
## Comment 3238
Date: 2005-05-27 21:03:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
Shall we consider the current situation (see also "my"
stable output for test
tests/BugsViaSourgeforce/Tests/ID.1209497.xq) as "OK" for
the release, and postpone the rest til after the release?
## Comment 3239
Date: 2005-11-09 16:23:38 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
./tests/BugsViaSourgeforce/Tests/ID.1209497.xq
## Comment 3240
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1209497 at http://sourceforge.net/support/tracker.php?aid=1209497
| XQuery: '<' should be escaped in xml mode | https://api.github.com/repos/MonetDB/MonetDB/issues/583/comments | 0 | 2020-11-30T08:43:45Z | 2024-06-27T11:04:22Z | https://github.com/MonetDB/MonetDB/issues/583 | 753,278,336 | 583 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-25 08:25:26 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-28 06:24:57 +0200
## Comment 3220
Date: 2005-05-25 20:25:26 +0200
From: Wouter Alink <<alink>>
The following XQuery:
<doc>\;</doc>
Produces the following output:
<doc>;</doc>
As you can see, it swallows the \, which it should not
have done.
According to Jan R, MIL consumes the \.
## Comment 3221
Date: 2005-05-25 20:34:50 +0200
From: @grobian
Logged In: YES
user_id=963970
Jan R is right, and if I recall correctly, this is hardly
fixeable.
## Comment 3222
Date: 2005-05-25 20:50:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This happens only at the translation of string constants.
Escape characters are ignored there -- see example:
MonetDB>bat(void,str).insert(nil," \;").print();
-----------------
h t name
void str type
-----------------
[ nil, " ;" ]
## Comment 3223
Date: 2005-05-25 20:55:24 +0200
From: @grobian
Logged In: YES
user_id=963970
" \;"
this is of course an invalid string, because '\;' is not a
valid escape sequence. It should read '\\;' to achieve the
effect you desire. The decision made here is to drop the
escape and as such ignore it + continue processing.
I think you should make sure you properly escape a string
before giving it to MIL. There are some routines for that
in GDK I think.
## Comment 3224
Date: 2005-05-25 20:57:30 +0200
From: @grobian
Logged In: YES
user_id=963970
please note: in the mail sourceforge has eliminated my
double slash on the second line. The webpage better
reflects my true intentions behind my post ;)
## Comment 3225
Date: 2005-05-25 21:01:43 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
as you can see from the email's subject line... more
software has difficulty with backslash.
## Comment 3226
Date: 2005-05-26 11:55:48 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I added another case in PFesc_string() which replaces every
occurrence of '\\' by '\\''\\'.
As long as no other characters appear, which get swallowed
or treated in a wrong way this bug is fixed :)
## Comment 3227
Date: 2005-05-28 18:24:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
JanR sais: Fixed! ... ;-)
## Comment 3228
Date: 2005-11-09 16:02:50 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
./tests/BugsViaSourgeforce/Tests/ID.1208667.xq
## Comment 3229
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1208667 at http://sourceforge.net/support/tracker.php?aid=1208667
| XQuery: swallowing \ | https://api.github.com/repos/MonetDB/MonetDB/issues/582/comments | 0 | 2020-11-30T08:43:42Z | 2024-06-27T11:04:21Z | https://github.com/MonetDB/MonetDB/issues/582 | 753,278,298 | 582 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-25 07:07:10 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-05-25 08:57:01 +0200
## Comment 3211
Date: 2005-05-25 19:07:10 +0200
From: Jan Rittinger <<jan.rittinger>>
If I misuse the '&' character or have a typo in my query
the pf command prints the character instead of producing
an error...
this one works:
19:02:47 rittinge@titan03:
/local_tmp/rittinge/pathfinder/Linux> pf | head
<a><</a>
MODULE DECLARATIONS
module("pathfinder");
module("pf_support");
module("aggrX3");
module("xtables");
module("malalgebra");
module("mmath");
while this one produces an runtime error (see first
character):
MIL-PROCS GENERATED FROM XQUERY
FUNCTIONS
19:03:00 rittinge@titan03:
/local_tmp/rittinge/pathfinder/Linux> pf | head
<a>&l;</a>
& MODULE DECLARATIONS
module("pathfinder");
module("pf_support");
module("aggrX3");
module("xtables");
module("malalgebra");
module("mmath");
## Comment 3212
Date: 2005-05-25 19:13:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
just discovered that this happens somewhere in milprintf()
since changing the milprintf into an fprintf(stderr,... moves the
& character to the next milprintf block
but I still have no clue what happens here...
## Comment 3213
Date: 2005-05-25 19:23:33 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
ok now I'm really puzzled ...
with a fprintf(stdout, ...) the & is the first character again
## Comment 3214
Date: 2005-05-25 20:34:44 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Jan,
thanks for the report. You found a parser bug. I already prepared the fix
and will check it in as soon as Mtest has completed.
flex' default behavior when a character is seen that does not match any
pattern, is to echo the character to stdout. This is why pf prints out the `&'.
In a few lexer states, the catch-all rule was missing, so the single `&' was
not caught and thus printed to stdout.
What you are writing about stdout, stderr, milprintf() etc. is probably a
buffering issue. It has nothing to do with the bug you discovered, but can
be quite confusing.
## Comment 3215
Date: 2005-05-25 20:44:23 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
It seems like my first guess was the best
## Comment 3216
Date: 2005-05-25 20:57:01 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fix is now in CVS.
## Comment 3217
Date: 2005-11-09 15:58:41 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
./tests/BugsViaSourgeforce/Tests/ID.1208620-1.xq
./tests/BugsViaSourgeforce/Tests/ID.1208620-2.xq
## Comment 3218
Date: 2005-11-09 17:04:09 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
test added in CVS (strange_ampersand.SF-1208620.xq)
## Comment 3219
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1208620 at http://sourceforge.net/support/tracker.php?aid=1208620
| XQuery: strange behaviour with '&' | https://api.github.com/repos/MonetDB/MonetDB/issues/581/comments | 0 | 2020-11-30T08:43:39Z | 2024-06-27T11:04:20Z | https://github.com/MonetDB/MonetDB/issues/581 | 753,278,268 | 581 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-25 06:45:49 +0200
From: Arjen van der Meijden <<arjenm>>
To: @njnes
Version: -- development
Last updated: 2005-05-26 12:05:57 +0200
## Comment 3207
Date: 2005-05-25 18:45:49 +0200
From: Arjen van der Meijden <<arjenm>>
I have this table and execute the following query on it:
CREATE TABLE "sys"."pwprijs" (
"id" int NOT NULL,
"pid" int NOT NULL,
"lid" int NOT NULL,
"prijs" real NOT NULL,
"Time" bigint NOT NULL,
"recordtimestamp" bigint NOT NULL,
CONSTRAINT "pwprijs_id_recordtimestamp_pkey"
PRIMARY KEY ("id", "recordtimestamp")
);
CREATE INDEX "pwprijs_lid_idx" ON "pwprijs" ("lid");
CREATE INDEX "pwprijs_pid_idx" ON "pwprijs" ("pid");
CREATE INDEX "pwprijs_recordtimestamp_idx" ON "pwprijs"
("recordtimestamp");
It basically is a set of historical prices for products
provided by suppliers.
Trying to find some trends in pricing and latest
prices, this query came to mind:
SELECT lid,
AVG(Prijs) as avg_prijs,
AVG(CASE WHEN RecordTimestamp =
(SELECT
MAX(i.RecordTimestamp)
FROM pwprijs i
WHERE i.pid = 117097
AND i.lid = o.lid)
THEN Prijs END) as current_prijs
FROM pwprijs o
WHER pid = 117097
GROUP BY lid
This query makes the Mserver stop with the following
message:
Mserver: ../../../sql/src/server/sql_select.mx:371:
find_pivot: Assertion `0' failed.
When the join in the subquery (i.lid = o.lid) is
removed, the query is accepted, although its of coure
not entirely the same query. Replacing the second AVG
with MIN or MAX yields the same result and the same error.
Its a cvs-checkout from this morning (Northern/Western
european time)
## Comment 3208
Date: 2005-05-26 00:05:57 +0200
From: @njnes
Logged In: YES
user_id=43556
the case of subqueries inside a case wasn't handled. Added
the missing code.
## Comment 3209
Date: 2005-11-09 15:42:03 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bugs/selectlist_subquery-sf-1208599.sql
## Comment 3210
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1208599 at http://sourceforge.net/support/tracker.php?aid=1208599
| Assertion failure with complex subquery in selectlist | https://api.github.com/repos/MonetDB/MonetDB/issues/580/comments | 0 | 2020-11-30T08:43:36Z | 2024-06-27T11:04:19Z | https://github.com/MonetDB/MonetDB/issues/580 | 753,278,234 | 580 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 11:03:29 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-28 05:34:44 +0200
## Comment 3203
Date: 2005-05-24 23:03:29 +0200
From: Jan Rittinger <<jan.rittinger>>
delete_doc("name"); only works after a shred_doc
function call.
The reason is the variable doc_sema, which is not
initialized. An assignment only appears in init_doc(),
which is indirectly called over shred_doc.
Since I'm not sure what the job of this variable is, I ask
somebody else to fix this bug. My solution would be to
add a 'doc_init()' function call in delete_doc_locked().
## Comment 3204
Date: 2005-05-28 17:34:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed in CVS:
delete_doc now first checks, whether the "doc_name" BAT and
the requested document do exist, and otherwise gives a
proper error message.
## Comment 3205
Date: 2005-11-09 16:23:29 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: TEST ADDED / SUCCESS
pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/delete_doc.SF-1208129.milC
## Comment 3206
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1208129 at http://sourceforge.net/support/tracker.php?aid=1208129
| XQuery: delete_doc only works after shred_doc | https://api.github.com/repos/MonetDB/MonetDB/issues/579/comments | 0 | 2020-11-30T08:43:33Z | 2024-06-27T11:04:18Z | https://github.com/MonetDB/MonetDB/issues/579 | 753,278,207 | 579 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 06:05:00 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2005-05-24 07:21:25 +0200
## Comment 3199
Date: 2005-05-24 18:05:00 +0200
From: @drstmane
The latest MonetDB (MonetDB_4-8 branch as of Tuesday
May 24 2005, 18:00:00 MEST) causes a SegFault in the
following tests:
scripts/gold/Tests/tst100
scripts/gold/Tests/tstvoid
src/modules/plain/Tests/enum
tests/BugReports/Tests/no.107
tests/suite_00/Tests/test_70
## Comment 3200
Date: 2005-05-24 19:21:24 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed typo (theap vs hheap)
## Comment 3201
Date: 2005-11-09 16:08:25 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST / REDUNDANT
## Comment 3202
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207924 at http://sourceforge.net/support/tracker.php?aid=1207924
| latest MonetDB causes SegFault in various tests | https://api.github.com/repos/MonetDB/MonetDB/issues/578/comments | 0 | 2020-11-30T08:43:30Z | 2024-06-27T11:04:17Z | https://github.com/MonetDB/MonetDB/issues/578 | 753,278,179 | 578 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 05:22:47 +0200
From: Arjen van der Meijden <<arjenm>>
To: @njnes
Version: -- development
Last updated: 2005-05-24 07:35:31 +0200
## Comment 3195
Date: 2005-05-24 17:22:47 +0200
From: Arjen van der Meijden <<arjenm>>
I noticed a weird result from AVG when doing one of my
queries; -1.7976931348623158e+307
Appearantly it happens with this minimal testcase:
monetdb-> create table emptyone (field decimal(3,1));
Operation successful
monetdb-> select avg(field) from emptyone;
+------------------------+
| scale_down_avg_field |
+========================+
| -1.7976931348623158E307 |
+------------------------+
1 row
The result should afaik be NULL, not this value. With a
decimal(3) it works correctly by the way. The same
behaviour is seen with numeric(3,1) vs numeric(3).
Compilation was with default options although with
assertions turned off. Gentoo 2005.0, gcc 3.3.5 on x86-32
## Comment 3196
Date: 2005-05-24 19:35:31 +0200
From: @njnes
Logged In: YES
user_id=43556
the rounding function didn't check for NULLs
## Comment 3197
Date: 2005-11-09 16:07:23 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-11-09_2.9.3/Tests/empty_avg.SF-1207887.sql
## Comment 3198
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207887 at http://sourceforge.net/support/tracker.php?aid=1207887
| Empty AVG(decimal(3,1)) returns -1.7976931348623158E307 | https://api.github.com/repos/MonetDB/MonetDB/issues/577/comments | 0 | 2020-11-30T08:43:27Z | 2024-06-27T11:04:16Z | https://github.com/MonetDB/MonetDB/issues/577 | 753,278,141 | 577 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 05:13:28 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-11-30 04:20:04 +0100
## Comment 3187
Date: 2005-05-24 17:13:28 +0200
From: Wouter Alink <<alink>>
I found a phenomenon similar to "[1207112] merged_union
fails" and "[1204965] XQuery: Example from W3C fails
, but i'm not sure if it is related to "[1207243]
handling of property reverse-sortedness is absolutely
bogus" as it does not complain about the size, but
about the hseqbase.
Therefore this separate bug-report.
the query:
MapiClient -lx slashdot2.xq
ERROR: merged_union: BAT 9 must have the same hseqbase
as BAT 1.
## Comment 3188
Date: 2005-05-25 13:14:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
The attached MIL script should help to locate the BUG:
The merged_union fails, as argument "_attr_own003" has
seqbase "0@0", while all other arguments
("_attr_iter003","_attr_qn003","_attr_prop003","_attr_frag003")
have seqbase "10@0".
As the trace from the attached MIL script shows, the latter
get their segbase set between "00000000" and "11111111",
while the former does not (see below).
Jan,
would you have any idea, why this happens?
========
Mserver /tmp/ID.1207880.MIL
--------
Monet Database Server V4.8.0_rc1
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
[ "---" ]
[ 10@0 ]
[ "00000000" ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
[ "11111111" ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
[ "22222222" ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
[ "33333333" ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 10@0 ]
-----------------
h t name
void oid type
-----------------
[ 0@0 ]
!ERROR: merged_union: BAT 9:0@0 must have the same hseqbase
as BAT 1:10@0.
!ERROR: CMDmerged_union: operation failed.
MonetDB>
========
## Comment 3189
Date: 2005-05-25 14:29:14 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This was a nice one :)
By using the seqbase command the underlying BATs of
multiple variables were changed. At one place a reverse().
mark(seqb).reverse() was used instead (only for one BAT
instead of all four), which triggered differing seqbases...
## Comment 3190
Date: 2005-11-09 15:59:09 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: REASSIGN wouter
Either come up with a test that is not dependent on external
and changeable data, or don't test this.
## Comment 3191
Date: 2006-11-10 04:20:01 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
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 3192
Date: 2006-11-29 10:04:53 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
over-ruling "sf-robot":
re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet.
User (submitter) & developer (assignee),
please check, again.
## Comment 3193
Date: 2007-11-30 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 3194
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207880 at http://sourceforge.net/support/tracker.php?aid=1207880
| XQuery: merged_union fails on hseqbase | https://api.github.com/repos/MonetDB/MonetDB/issues/576/comments | 0 | 2020-11-30T08:43:24Z | 2024-06-27T11:04:15Z | https://github.com/MonetDB/MonetDB/issues/576 | 753,278,108 | 576 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 05:00:57 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-25 12:45:24 +0200
## Comment 3183
Date: 2005-05-24 17:00:57 +0200
From: Wouter Alink <<alink>>
The following query returns an empty result:
doc("http://slashdot.org/rss/index.rss")//title
While this one returns the expected title elements:
for $t in doc("http://slashdot.org/rss/index.rss")//*
where name($t) = 'title'
return $t
## Comment 3184
Date: 2005-05-24 22:41:06 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This bug is invalid :-)
In your specified file there is a standard namespace (xmlns
attribute). Your first query asks for a title element with an
empty namespace uri (standard if you don't set any default
namespace), while the second one makes a string
comparison (discarding the uri).
So the solution would be a path step with the correct
nametest:
doc("http://slashdot.org/rss/index.rss")//*:title
## Comment 3185
Date: 2005-11-09 15:41:50 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST / INVALID
## Comment 3186
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207868 at http://sourceforge.net/support/tracker.php?aid=1207868
| XQuery: incorrect name-test in url-docs | https://api.github.com/repos/MonetDB/MonetDB/issues/575/comments | 0 | 2020-11-30T08:43:21Z | 2024-06-28T07:36:39Z | https://github.com/MonetDB/MonetDB/issues/575 | 753,278,081 | 575 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 04:50:57 +0200
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2010-05-04 11:08:16 +0200
## Comment 3180
Date: 2005-05-24 16:50:57 +0200
From: Wouter Alink <<alink>>
The following query returns an empty result:
doc("http://slashdot.org/rss/index.rss")//title
While this one returns the expected title elements:
for $t in doc("http://slashdot.org/rss/index.rss")//*
where name($t) = 'title'
return $t
## Comment 3181
Date: 2005-11-09 15:40:13 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST / REDUNDANT
## Comment 3182
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207858 at http://sourceforge.net/support/tracker.php?aid=1207858
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.
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
| XQuery: incorrect name-test in url-docs | https://api.github.com/repos/MonetDB/MonetDB/issues/574/comments | 0 | 2020-11-30T08:43:18Z | 2024-06-27T11:04:13Z | https://github.com/MonetDB/MonetDB/issues/574 | 753,278,058 | 574 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 04:45:00 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-24 05:23:36 +0200
## Comment 3176
Date: 2005-05-24 16:45:00 +0200
From: Wouter Alink <<alink>>
when running 'make' for pathfinder the following
warnings appear:
lex.yy.c: In function `pflex':
lex.yy.c:3411: warning: label `find_rule' defined but
not used
../../../compiler/parser/scanner.l: At top level:
lex.yy.c:5912: warning: `yy_flex_realloc' defined but
not used
../../../compiler/algebra/algebra.c: In function
`PFalg_scjoin':
../../../compiler/algebra/algebra.c:677: warning:
unused variable `i'
## Comment 3177
Date: 2005-05-24 17:23:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
I just fixe the last one.
The first two are in [f]lex-generated code, hence beyond our
control.
## Comment 3178
Date: 2005-11-09 15:38:42 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST / COMPILATION
## Comment 3179
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207854 at http://sourceforge.net/support/tracker.php?aid=1207854
| XQuery: make warnings | https://api.github.com/repos/MonetDB/MonetDB/issues/573/comments | 0 | 2020-11-30T08:43:14Z | 2024-06-27T11:04:13Z | https://github.com/MonetDB/MonetDB/issues/573 | 753,278,017 | 573 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 01:29:32 +0200
From: Wouter Alink <<alink>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2005-08-11 11:48:44 +0200
## Comment 3164
Date: 2005-05-24 13:29:32 +0200
From: Wouter Alink <<alink>>
i guess this is a feature rather than a bug, but i'll
post it anyway
shredding 2 documents:
- both contain the same amount of nodes (+-150000)
- doc1.xml is 15MB in size and contains some text
- doc2.xml is 10MB in size and contains less text (but
does have a numerous amount of attributes (+- 500000))
MonetDB>shred_doc("/ufs/alink/test-data/doc1.xml","doc1.xml");
Shredded XML doc("doc1.xml"), total time after
commit=1.405s
MonetDB>shred_doc("/ufs/alink/test-data/doc2.xml","doc2.xml");
Shredded XML doc("doc2.xml"), total time after
commit=29.230s
## Comment 3165
Date: 2005-05-24 16:10:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Did you configure (and hence compile) MonetDB & pathfinder with
a) default settings (results in "-g -O2" with gcc)
b) debugging (i.e., "configure --enable-debug"; results in "-g")
c) optimization (i.e., "configure --enable-optimize";
results in "-O6 ..." with gcc)
?
Are your documents and your database (dbfarm) on local or on
NFS-mounted filesystems?
## Comment 3166
Date: 2005-05-24 16:17:28 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
- i compiled using default settings (a)
- dbfarm is local (/ufs/alink/local/var/dbfarm)
hereby the links to the example files:
/ufs/alink/test-data/doc1.xml
/ufs/alink/test-data/doc2.xml
## Comment 3167
Date: 2005-08-02 13:28:56 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Jan F, do you maybe have any clue, as in where to look, to
find a solution to this bug? The bug is getting more and
more annoying to me, for documents less than a GB, it takes
hours to shred.
## Comment 3168
Date: 2005-08-02 14:15:40 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
To be sure libxml2 is the main cause of these figures I made
a version of the shredder which does no processing at all.
It just returns all libxml calls immediately. I would like
to run both exmaples with this version. Where can I ftp
these documents, I have a CWI account but do not know where
to login.
## Comment 3169
Date: 2005-08-02 14:49:15 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
OK. Got the files from ssh.cwi.nl. and I ran the experiments
and got these times
ALL ONLY_XML
doc.1 0.75s 0.24s
doc.2 10s 0.27s
It looks indeed something is very very slow in our part of
the attribute handling because 9.7 seconds of the 10 seconds
of doc.2 are spend in this code. I will have a look at it!!!
## Comment 3170
Date: 2005-08-02 15:23:34 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
FOUND IT!!!! The problem is caused by the duplicate check of
the attribute values. For every attribute value one string
is inserted in the PROP_VAL table. I switched on duplicate
checking for this table because the original code had this
compression feature implemented too.
When I switch off the duplicate checking for PROP_VAL in the
shredbatdef[] table the response time drops from 10 seconds
to 0.88 seconds!!!!!!!!!!
Wouter can do this experiment himself by just changing the
last 1 entry after PROP_VAL in the shredbatdef[] table into 0.
CONCLUSION: because this duplicate checking has such an
impact on the performance of shredding xml files with lots
of attributes I propose to switch it off by default. I hope
this does not have an effect on our benchmarks! Does anybody
have any objections?????
## Comment 3171
Date: 2005-08-02 15:44:17 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Thanks! saves me lots of time... ;)
but, can't the elimination of duplicate values be done after
the shredding? Should probably not take to much time to
compute...
Or maybe leave the PROP_VAL out and just have an
ATTR_VAL-bat or PROP_VAL=BAT[void,void].
I think MonetDB's stringheap already filters out duplicate
strings? am i right?
## Comment 3172
Date: 2005-08-02 16:00:52 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
When this duplicate elimination is so easy afterwards the
big question is why it takes soo much time when you do it on
the fly. I have a very naive implementation with a
BAT[void,str] where I create a BAThash() on the tail. Before
every BUNins() I do a BUNfnd() to check if the string is
already in the table.
## Comment 3173
Date: 2005-08-11 11:48:43 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
The duplicate removal is now handled after the entire
document is shred. This has a much better performance and I
consider the bug close now!
## Comment 3174
Date: 2005-11-09 15:37:30 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST
## Comment 3175
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207707 at http://sourceforge.net/support/tracker.php?aid=1207707
| XQuery: shredding attributes takes time | https://api.github.com/repos/MonetDB/MonetDB/issues/572/comments | 0 | 2020-11-30T08:43:11Z | 2024-06-27T11:04:12Z | https://github.com/MonetDB/MonetDB/issues/572 | 753,277,985 | 572 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 12:46:25 +0200
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-24 05:32:39 +0200
## Comment 3160
Date: 2005-05-24 12:46:25 +0200
From: Wouter Alink <<alink>>
when using MapiClient first for XQuery and then for
MIL, MapiClient does not come with a prompt:
MapiClient -lx script.xq
MapiClient -lmil
## Comment 3161
Date: 2005-05-24 17:32:38 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed in revision 1.82.2.1 of monet_client.mx.
## Comment 3162
Date: 2005-11-09 15:12:13 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST
## Comment 3163
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207664 at http://sourceforge.net/support/tracker.php?aid=1207664
| XQuery: MIL after XQuery | https://api.github.com/repos/MonetDB/MonetDB/issues/571/comments | 0 | 2020-11-30T08:43:08Z | 2024-06-27T11:04:11Z | https://github.com/MonetDB/MonetDB/issues/571 | 753,277,953 | 571 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 11:32:34 +0200
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2005-05-27 09:43:42 +0200
## Comment 3154
Date: 2005-05-24 11:32:34 +0200
From: Wouter Alink <<alink>>
When removing the source code, there appear to be some
write-protected files... i don't know if this is a bug,
but i assume they should not be write-protected.
[alink@volans src]$ rm -r pathfinder
rm: remove write-protected regular file
`pathfinder/Linux/compiler/semantics/normalize.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/semantics/typecheck.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/core/simplify.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/core/fs.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/core/coreopt.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/mil/ma_opt.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/mil/ma_gen.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/mil/milgen.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/algebra/algopt.c'? y
rm: remove write-protected regular file
`pathfinder/Linux/compiler/algebra/core2alg.c'? y
## Comment 3155
Date: 2005-05-24 13:38:59 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
We set those files read-only on purpose. Those are generated source
files, and we want to avoid that we accidentally edit generated files during
development.
## Comment 3156
Date: 2005-05-27 21:39:51 +0200
From: @grobian
Logged In: YES
user_id=963970
Just my € 0.02:
If there is a reason (like Jens says – sounds plausible)
then this bug should be closed and made invalid. The
solution is simply to use "rm -Rf".
## Comment 3157
Date: 2005-05-27 21:43:41 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
totally agree
## Comment 3158
Date: 2005-11-09 15:07:19 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST
## Comment 3159
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207625 at http://sourceforge.net/support/tracker.php?aid=1207625
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: write-protected files | https://api.github.com/repos/MonetDB/MonetDB/issues/570/comments | 0 | 2020-11-30T08:43:04Z | 2024-06-28T07:36:39Z | https://github.com/MonetDB/MonetDB/issues/570 | 753,277,912 | 570 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-24 07:18:50 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-25 10:59:29 +0200
## Comment 3149
Date: 2005-05-24 07:18:50 +0200
From: @drstmane
After yesterdays changes, most MAPI tests seem to fail
on SuSE 9.1 (32-bit); cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/index_short.html
I have no idea, whether this is actually related to
useterdays (MAPI-) code changes, or whether the system
(in Konstanz) has changed...
## Comment 3150
Date: 2005-05-24 16:13:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Might be fixed by my eaerlier chnages in
MonetDB/src/testing/Mtest.py.in --- testing will tell us by
tomorrow morning.
## Comment 3151
Date: 2005-05-25 10:59:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
Lates changes to Mtest.py.in did solve the problem.
## Comment 3152
Date: 2005-11-09 15:33:54 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
## Comment 3153
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207516 at http://sourceforge.net/support/tracker.php?aid=1207516
| Mapi tests fail on SuSE 9.1 (32 bit; in KN) | https://api.github.com/repos/MonetDB/MonetDB/issues/569/comments | 0 | 2020-11-30T08:43:02Z | 2024-06-27T11:04:09Z | https://github.com/MonetDB/MonetDB/issues/569 | 753,277,879 | 569 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 08:05:40 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-11-02 05:34:20 +0100
## Comment 3141
Date: 2005-05-23 20:05:40 +0200
From: @drstmane
Some time ago, handling of reverse-sortedness (aka.
GDK_SORTED_REV) has been added, but the implementation
handling is far from complete!
Only functions BATorderd[_rev], BATsort[_rev] and
BATorder[_rev] do use and set this property, but no
other operations are aware of it.
Especially all operations that modify BATs (insert,
delete, etc.) do only check for normal sortedness
([BAT][ht]sorted&1), but completely ignore
reverse-sortedness ([BAT][ht]sorted&GDK_SORTED_REV).
Hence, if a BAT happens to be reverse-sorted, and the
property is set (e.g., each time BATsort[_rev] is
called on this BAT, as this triggers the call of
BATorderd[_rev], which in turn (since recently) scans
for [reverse-]sortedness, and set the property if it
holds), subsequent updates to this BAT might destroy
the reverse-sortedness, but none of the update
operations does unset the respective property.
Unfortunately, property checking is also completely
unaware of the reverse-sortedness, and hence cannot not
detect the resulting inconsistency.
This actually causes bugs [1204965 ] "XQuery: Example
from W3C fails" & [ 1207112 ] "XQuery: merged_union fails".
Solution: We need to check and fix ALL places where
BATs are modified and the reverse-osrtedness might be
destroy --- these are at least all places where
"[BAT][ht]sorted&1" is used...
After spending several hours on locating this bug, I
now don't have any time left to (start) fix(ing) this
today --- most probabaly I won't have time to look at
it before tomorrow evening...
## Comment 3142
Date: 2005-05-23 20:08:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
... obviously, also BATpropcheck needs to be made aware of
the reverse-sortedness...
## Comment 3143
Date: 2005-05-25 04:17:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
627 days after it was born on Friday Sep 05 2003:
Fixed implementation of reverse sorting.
Now, update operations also unset the reverse sortedness
property,
in case the updates do destroy the sort order!
Fixed some more places so that checking for sortedness looks
only
at the lowest bit of [ht]sorted, and setting sortedness assigns
GDK_SORTED instead of 1 to [ht]sorted.
These changes fix the BUGs
1204965 "XQuery: Example from W3C fails"
1207112 "XQuery: merged_union fails"
TODO:
Make BATpropcheck aware of reverse sortedness!
## Comment 3144
Date: 2005-11-09 15:40:36 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: RELEASED
REASSIGN to Stefan.
Don't know how to make test script for this bug.
## Comment 3145
Date: 2005-11-09 15:58:43 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / CODE
there is no (reasonable) way to make a test script for this one;
instead, the code would have to be checked by hand...
## Comment 3146
Date: 2005-11-24 23:56:00 +0100
From: @peterboncz
Logged In: YES
user_id=591107
sorry, why is this bug open?
## Comment 3147
Date: 2006-11-02 17:34:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
no further problems related to reverse sorting have occured
for almost a year, hence, we consider this a purely
"academic" issue.
## Comment 3148
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207243 at http://sourceforge.net/support/tracker.php?aid=1207243
| handling of property reverse-sortedness is absolutely bogus | https://api.github.com/repos/MonetDB/MonetDB/issues/568/comments | 0 | 2020-11-30T08:42:59Z | 2024-06-28T07:36:39Z | https://github.com/MonetDB/MonetDB/issues/568 | 753,277,856 | 568 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 04:33:14 +0200
From: @MarcinZukowski
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-05-24 05:00:07 +0200
## Comment 3133
Date: 2005-05-23 16:33:14 +0200
From: @MarcinZukowski
for $x at $i in (1,2)
return <li>{$i}-{$x}</li>
=>
<li>1-1</li>,
<li>2-2</li>
but
for $x at $i in (1)
return <li>{$i}-{$x}</li>
=>
<li>-1</li>
Again, I'm not sure it's an error, but looks suspicious
## Comment 3134
Date: 2005-05-23 17:02:36 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
The problem here is the missing typing in core/coreopt.brg line
735 (lit_int(1) has type none).
Marcin you discovered a bug :-)
Could you please assign it to Jens Teubner.
## Comment 3135
Date: 2005-05-23 17:08:45 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I think I solved this bug, but I'm not completely sure
-- Jens could have a look
## Comment 3136
Date: 2005-05-23 17:10:09 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Assigning to Jens.
Wow, the first day with XQuery and yes, I found an error! :)
## Comment 3137
Date: 2005-05-24 13:45:36 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Congrats Marcin for your first bug :-)
I just checked in a slightly different fix that should be slightly more efficient
than Jan's. I consider this bug now as fixed.
Thanks for the report!
## Comment 3138
Date: 2005-05-24 17:00:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just added a test that "confirms" the correctness.
Closing this bug report.
## Comment 3139
Date: 2005-11-09 15:32:16 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207124-1.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207124-2.*
## Comment 3140
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207124 at http://sourceforge.net/support/tracker.php?aid=1207124
| XQuery: wrong numbering with single item lists | https://api.github.com/repos/MonetDB/MonetDB/issues/567/comments | 0 | 2020-11-30T08:42:55Z | 2024-06-27T11:04:07Z | https://github.com/MonetDB/MonetDB/issues/567 | 753,277,827 | 567 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 04:20:43 +0200
From: @MarcinZukowski
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-25 04:19:05 +0200
## Comment 3126
Date: 2005-05-23 16:20:43 +0200
From: @MarcinZukowski
Using tests/XQuery/Tests/book.xml
for $x at $i in doc("book.xml")/bib/book[price<=49.95]
return <li>{$i}. {data($x/title)}. {data($x/price)}</li>
=>
ERROR: !ERROR: merged_union: BAT 3 must have the same
size as BAT 1.
## Comment 3127
Date: 2005-05-23 16:24:51 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
for $x at $i in doc("book.xml")/bib/book[price<60]
return <li>{$i}. {data($x/title)}. {data($x/price)}</li>
=>
ERROR: !ERROR: merged_union: BAT 3 must have the same size
as BAT 1.
but
for $x at $i in doc("book.xml")/bib/book[price<70]
return <li>{$i}. {data($x/title)}. {data($x/price)}</li>
=>
<li>1. TCP/IP Illustrated. 65.95</li>,
<li>2. Advanced Programming in the Unix environment. 65.95</li>,
<li>3. Data on the Web. 39.95</li>
## Comment 3128
Date: 2005-05-23 16:36:56 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
see also bug [ 1204965 ] XQuery: Example from W3C fails
## Comment 3129
Date: 2005-05-23 20:06:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
This bug is most probably caused by bug
[ 1207243 ] "handling of property reverse-sortedness is
absolutely bogus".
## Comment 3130
Date: 2005-05-25 04:19:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
627 days after it was born on Friday Sep 05 2003:
Fixed implementation of reverse sorting.
Now, update operations also unset the reverse sortedness
property,
in case the updates do destroy the sort order!
Fixed some more places so that checking for sortedness looks
only
at the lowest bit of [ht]sorted, and setting sortedness assigns
GDK_SORTED instead of 1 to [ht]sorted.
These changes fix the BUGs
1204965 "XQuery: Example from W3C fails"
1207112 "XQuery: merged_union fails"
TODO:
Make BATpropcheck aware of reverse sortedness!
## Comment 3131
Date: 2005-11-09 15:31:26 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207112_run.*
## Comment 3132
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207112 at http://sourceforge.net/support/tracker.php?aid=1207112
| XQuery: merged_union fails | https://api.github.com/repos/MonetDB/MonetDB/issues/566/comments | 0 | 2020-11-30T08:42:53Z | 2024-06-27T11:04:06Z | https://github.com/MonetDB/MonetDB/issues/566 | 753,277,803 | 566 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 04:02:15 +0200
From: @MarcinZukowski
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-24 07:16:19 +0200
## Comment 3121
Date: 2005-05-23 16:02:15 +0200
From: @MarcinZukowski
Using tests/XQuery/Tests/book.xml
The following query:
for $x in doc("book.xml")/bib/book
where $x/price < 100
return $x/price
=>
<price> 65.95</price>,
<price>65.95</price>,
<price>39.95</price>
while this one:
for $x in doc("book.xml")/bib/book
where $x/price < 50
return $x/price
=>
<price>39.95</price>
This suggests, the node ' 65.95' (with a space at the
beginning) is treated as a number.
However, if I do this:
for $x in doc("book.xml")/bib/book
order by $x/price
return $x/price
=>
<price> 65.95</price>,
<price>129.95</price>,
<price>39.95</price>,
<price>65.95</price>
Perhaps during sorting the whitespace SHOULD be taken
into account, then this bug report is incorrect.
## Comment 3122
Date: 2005-05-23 16:35:00 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Before a comparison the text values are casted to a number,
which is why the whitespaces are ignored. During the order by
you compare the text, which explains the resulting order.
So I think the inconsistencies are more or less correct.
You're expected result would need an additional cast:
for $x in doc("book.xml")/bib/book
order by exactly-one($x/price/text()) cast as xs:decimal
return $x/price
## Comment 3123
Date: 2005-05-24 17:05:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
From your discussion, I understand that this bug report is
actually "invalid", as the current behavior if compliant
with the XQuerysemantics, right?
I just added the respective test scripts
(tests/BugsViaSourgeforce/Tests/ID.1207096-[1234]*).
Could you please check, whether my stable output is correct?
If so, please close this bug report.
If not, please fix the stable output by hand.
## Comment 3124
Date: 2005-11-09 15:30:30 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207096-2.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207096-1.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207096-4.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207096-3.*
## Comment 3125
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207096 at http://sourceforge.net/support/tracker.php?aid=1207096
| XQuery: inconsistency in treating numbers with whitespaces | https://api.github.com/repos/MonetDB/MonetDB/issues/565/comments | 0 | 2020-11-30T08:42:50Z | 2024-06-28T07:36:39Z | https://github.com/MonetDB/MonetDB/issues/565 | 753,277,764 | 565 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 03:52:06 +0200
From: @MarcinZukowski
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-24 08:18:10 +0200
## Comment 3113
Date: 2005-05-23 15:52:06 +0200
From: @MarcinZukowski
Using book.xml from /tests/XQuery/Tests
The following query:]
doc("book.xml")/bib/book/price
returns
<price> 65.95</price>,
<price>65.95</price>,
<price>39.95</price>,
<price>129.95</price>
Now:
doc("book.xml")/bib/book[price<=65.96]/price
=>
<price> 65.95</price>,
<price>65.95</price>,
<price>39.95</price>.
seems OK
I have problems with these queries:
doc("book.xml")/bib/book[price<=65.95]/price
=>
<price>39.95</price>
and I'd expect 65.95 as well
doc("book.xml")/bib/book[price=65.95]/price
=>
NOTHING
and I'd expect 65.95
doc("book.xml")/bib/book[price="65.95"]/price
=>
<price>65.95</price>
this one is perhaps correct 'cos I specified number as
a string?
It's my first ever attempt at XQuery, so parhaps these
are not bugs at all, but looks suspicious.
## Comment 3114
Date: 2005-05-23 15:55:54 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
same problem when trying:
for $x in doc("book.xml")/bib/book
where $x/price <= "65.95"
return $x/price
=>
<price>39.95</price>
## Comment 3115
Date: 2005-05-23 16:15:15 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Surprise:
doc("book.xml")/bib/book[price<39.95]/price
=>
<price>39.95</price>
## Comment 3116
Date: 2005-05-23 16:27:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I think the problem here is that we use dbl instead of decimal
and one is added to MonetDB as string and one as number:
MonetDB>dbl("65.95").print();
[ 65.950000000000003 ]
MonetDB>dbl(65.95).print();
[ 65.949996948242188 ]
The solution could be to add the values as casted strings, but
I'm not sure wether we want that...
## Comment 3117
Date: 2005-05-24 19:12:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
To mee, this looks very much like a casting problem:
In MIL, floating point constants are by default parsed as
flt; only with a "LL" suffix they are parsed as dbl. Due to
the obvious differences in the binary representation of dbl
(64bit) and flt (32 bit), we get:
========
MonetDB>print(65.95);
[ 65.9499969 ]
MonetDB>print(flt(65.95));
[ 65.9499969 ]
MonetDB>print(dbl(65.95));
[ 65.949996948242188 ]
MonetDB>print(flt("65.95"));
[ 65.9499969 ]
MonetDB>print(dbl("65.95"));
[ 65.950000000000003 ]
MonetDB>print(dbl(65.95LL));
[ 65.950000000000003 ]
MonetDB>print(flt(65.95LL));
[ 65.9499969 ]
MonetDB>print(65.95LL);
[ 65.950000000000003 ]
========
Note, this IS CORRECT!
Obviously, there is no excat float or double representation
for "65.95"; the closest representation are shown above.
I'm not quite sure, but I suppose, that the "65.95" is
parsed differently in different places...
## Comment 3118
Date: 2005-05-24 20:18:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jan R. fixed the double-handling in compiler/milprint_summer.c .
## Comment 3119
Date: 2005-11-09 15:29:12 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-3.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-6.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-7.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-4.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-2.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-5.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207090-1.*
## Comment 3120
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207090 at http://sourceforge.net/support/tracker.php?aid=1207090
| XQuery: bug in a simple predicate evaluation | https://api.github.com/repos/MonetDB/MonetDB/issues/564/comments | 0 | 2020-11-30T08:42:47Z | 2024-06-27T11:04:04Z | https://github.com/MonetDB/MonetDB/issues/564 | 753,277,727 | 564 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 03:30:28 +0200
From: @MarcinZukowski
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-05-23 07:53:34 +0200
## Comment 3110
Date: 2005-05-23 15:30:28 +0200
From: @MarcinZukowski
HowToStart-PF clearly says you CAN do this:
MapiClient -lx < element2.xq
However, the result is the same as if you would just type:
MapiClient -lx
## Comment 3111
Date: 2005-11-09 15:34:33 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / DOCUMENTATION + DUPLICATE
## Comment 3112
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207070 at http://sourceforge.net/support/tracker.php?aid=1207070
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.
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| Documentation wrong about piping to MapiClient -lx | https://api.github.com/repos/MonetDB/MonetDB/issues/563/comments | 0 | 2020-11-30T08:42:44Z | 2024-06-28T07:36:38Z | https://github.com/MonetDB/MonetDB/issues/563 | 753,277,695 | 563 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 03:09:23 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-24 10:05:02 +0200
## Comment 3105
Date: 2005-05-23 15:09:23 +0200
From: Wouter Alink <<alink>>
Look at the queries below:
query 1 returns the expected result
<a>aap</a>
query 2 returns the expected result
<a>aap</a>,
<a>aap</a>,
<a>aap</a>
query 3 returns:
WARNING: BBPdecref: range error -164
1.
for $t in (1)
return <doc><a>aap</a></doc>/a[text() = "aap"]
2.
for $t in (1,2,3)
return <doc><a>aap</a></doc>/a
3.
for $t in (1,2,3)
return <doc><a>aap</a></doc>/a[text() = "aap"]
## Comment 3106
Date: 2005-05-23 16:09:36 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
The problem here is that in case 1 and 3 the join recognition is
applied. Using the first example triggers another level of
optimization in the thetajoin translation than the third one.
I think the problem is the line:
"snd_iter := snd_iter.leftjoin(rx);\n");
which should be replace by
"snd_iter := snd_iter.leftjoin(%s);\n", rx);
because rx is no variable name, but the string with the variable
name. The same applies for lx 5 lines above in
mil/milprint_summer.c.
I'm not 100% sure if that change matches the wanted
behaviour --- Stefan could you have a look at it and fix it :)
## Comment 3107
Date: 2005-05-24 10:05:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed in revision 1.74.2.1 of
pathfinder/compiler/mil/milprint_summer.c .
## Comment 3108
Date: 2005-11-09 14:53:23 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207056-1.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207056-2.*
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207056-3.*
## Comment 3109
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207056 at http://sourceforge.net/support/tracker.php?aid=1207056
| XQuery: error using a test in return-clause of FLWR | https://api.github.com/repos/MonetDB/MonetDB/issues/562/comments | 0 | 2020-11-30T08:42:42Z | 2024-06-27T11:04:02Z | https://github.com/MonetDB/MonetDB/issues/562 | 753,277,671 | 562 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 02:46:26 +0200
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2007-05-28 11:26:58 +0200
## Comment 3090
Date: 2005-05-23 14:46:26 +0200
From: Wouter Alink <<alink>>
Although a very stupid one... the attached script does
let my Mserver crash with a segfault. the query
recursively calls the 'string' function 1120 times.
note that Mserver does not crash if a user defined
function is infinitely calling itself. it then returns:
"WARNING: BBPdecref: range error -2075"
and exits clean.
## Comment 3091
Date: 2005-05-23 15:52:07 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
On my machine this works if I use:
pf test3.xq > foo & Mserver foo
But the created foo file is 51 MB big and takes about 2,5
minutes to generate. Mserver itself has no problems and
returns the result within 5 seconds.
One solution could be to add an optimization rule, which omits
1119 string function calls -- but I don't think that solves the
problem :-)
Wouter are you sure that Mserver and not pf crashes on your
machine?
## Comment 3092
Date: 2005-05-23 16:43:24 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
quite sure, but it might be that you have a superior rechner ;)
Terminal A:
[alink@volans test-data]$ MapiClient -lxquery test3.xq
Connection terminated
[alink@volans test-data]$
Terminal B:
[alink@volans alink]$ Mserver
Monet Database Server V4.9.0
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(pathfinder);
MonetDB>pfstart();
MonetDB>Segmentation fault
[alink@volans alink]$
## Comment 3093
Date: 2005-05-23 17:09:56 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
stupid me... (excuse me very much... it is probably not
Mserver)
[alink@volans test-data]$ pf test3.xq > foo
Segmentation fault
## Comment 3094
Date: 2005-05-23 17:46:57 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
here my timings:
time cat test.xq | pf -T > /dev/null
parsing: 007ms
normalization: 016ms
semantical analysis: 005ms
XML Schema import: 000ms
core mapping: 065ms
core simplification: 01m 53s 752ms
type checking: 147ms
core tree optimization: 003ms
MIL code output: 02s 148ms
real 1m56.220s
user 1m55.655s
sys 0m0.598s
I think the performance is killed in rule 10 of core/simplify.brg,
where let bindings are unnested:
let $v1 := let $v2 := e return e' return e''
-->
let $v2 := e return
let $v1 := e' return
e''
Perhaps we could avoid such let binding at an earlier stage or
avoid relabeling the subtree at every step - does somebody
have any ideas?
## Comment 3095
Date: 2005-05-23 18:00:12 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
don't know if this helps, but i ran the same test and this
is the output:
[alink@volans test-data]$ time cat test3.xq | pf -T > /dev/null
Segmentation fault
real 0m0.077s
user 0m0.033s
sys 0m0.026s
[alink@volans test-data]$
## Comment 3096
Date: 2005-05-24 13:33:58 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Concerning the performance issues around let-unfolding:
When original implementation of our Core simplifier was Twig based, we
saw quite some significant performance problems with let-unfolding. This
is actually why Torsten had introduced the -O command line option.
With the shift to Burg, my impression was that performance problems are
gone now, and I had let the unfolding phase run unconditionally.
My impression is that this is okay in many situations. This is actually the
first query I see where let-unfolding actually hurts. In other cases, I think
let-unfolding could lead to interesting optimizations that we also benefit
from in later compilation stages.
I could think of two choices:
1. We have the user decide via the -O switch again. But what about
server-side compilation? Do we want to do this with or without let-
unfolding?
2. We could unfold only a limited number of let clauses. This is a
compromise that I'd suggest. We could count the number of unfolds as
we go. As soon as we hit a certain number, we just stop unfolding and
continue compilation. This would bring us optimization for most queries,
while still not causing real trouble for the other cases.
For the (original) problem of the Segmentation Fault I don't have a good
idea. Actually, the Pathfinder compiler should report a few lines more than
just a plain `Segmentation Fault'. This looks a bit strange to me.
## Comment 3097
Date: 2005-05-24 18:37:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
Maybe I missed something, but in my case, the generated MIL
code is only 2.5 KB...
Producing it works fine, though it takes pf more than 4
minutes (configured with --enable-debug).
Mserver than produces the correct result in about 1 second.
========
18:27:04 manegold@draco:~/Monet/Stable/pathfinder $ time pf
-T /tmp/test3.xq > /tmp/test3.mil
parsing: 012ms
normalization: 033ms
semantical analysis: 007ms
XML Schema import: 000ms
core mapping: 081ms
core simplification: 04m 04s 548ms
type checking: 198ms
core tree optimization: 006ms
MIL code output: 02s 655ms
real 4m7.597s
user 4m6.776s
sys 0m0.632s
18:31:34 manegold@draco:~/Monet/Stable/pathfinder $ l -h
/tmp/test3.*
-rw-r----- 1 manegold ins 2.8K May 24 18:31 /tmp/test3.mil
-rw-r--r-- 1 manegold ins 8.9K May 24 18:13 /tmp/test3.xq
18:32:09 manegold@draco:~/Monet/Stable/pathfinder $ wc
/tmp/test3.mil
118 357 2855 /tmp/test3.mil
18:36:09 manegold@draco:~/Monet/Stable/pathfinder $ time
Mserver --set monet_prompt='' < /tmp/test3.mil
Monet Database Server V4.8.0_rc1
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
"test"
</XQueryResult>
Trans 247535.997 msec
Shred 0.000 msec
Query 1.000 msec
Print 0.000 msec
real 0m1.001s
user 0m0.919s
sys 0m0.082s
18:36:22 manegold@draco:~/Monet/Stable/pathfinder $
========
## Comment 3098
Date: 2005-05-24 20:19:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
The problem of the huge MIL output has been solved by Jan R.
The remaining performance problems are not crucial for the
(first) release.
## Comment 3099
Date: 2005-11-09 15:26:32 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: TEST ADDED / FAILURE
$MapiClient -lx xquery_crashtest.SF-1207048.xq
syntax error, unexpected $end, expecting ")" on line 116
(Note: since there are quite some '('-s and ')'-s, mistake
can be quickly made. But I have checked in several different
ways, and they all result in the same number of '('-s and ')'-s)
$pf xquery_crashtest.SF-1207048.xq
Segmentation fault
(This should not happen anyway)
## Comment 3100
Date: 2006-01-22 20:52:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
test results in a segfault
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-11-09_0.9.3/xquery_crashtest.SF-1207048.err.00.html
bug I doubt that there is time to fix this before the release.
volunteer(s)?
## Comment 3101
Date: 2006-06-06 20:55:04 +0200
From: @grobian
Logged In: YES
user_id=963970
BUMP!
This thing apparently still crashes:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_BugDay_2005-11-09_0.9.3/xquery_crashtest.SF-1207048.err.00.html
## Comment 3102
Date: 2006-06-19 13:05:37 +0200
From: @peterboncz
Logged In: YES
user_id=591107
why is this bug so relevant? I descreased its priority.
this bug is about the limitations of a parser in the
nesting depth. There are always such limitations, because
a machine has limited resources. The crash here happens
because the stack space is exhausted. One can prevent it
by increasing the stack size (on some OS-es).
Of course, serious software should not crash. A malignant
user can just bring down MXQ servers by sending this query
to them. So it would be better that some checks are
inserted on the maximum nesting depth. MIL does have
support for this.
The problem occurs inside the burg-generated code.
Imposing such a check is pretty simple, but requires a fix
in burg.
(in reduce, one could pass it a stack limit as a second
parameter and then check in the first line of reduce()
whether a the address of a local variable (i.e. on the
stcak) exceeds the limit.
or is there some option in burg already to impose a
maximum nesting depth?
## Comment 3103
Date: 2007-05-28 11:26:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
since Peter'\''s recent fix for
[ 1607210 ] XQ: server-side compilation crash (member benchmark)
http://sourceforge.net/tracker/index.php?func=detail&aid=1607210&group_id=56967&atid=482468
"
- introduced a stack fence that aborts too deep recursion
only enabled in embedded mode (to keep Mserver alive on bad queries)
",
the query no longer causes a segfault, but produces a proper error message.
Approved error message and (empty) output
## Comment 3104
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207048 at http://sourceforge.net/support/tracker.php?aid=1207048
| XQuery: crashtest | https://api.github.com/repos/MonetDB/MonetDB/issues/561/comments | 0 | 2020-11-30T08:42:39Z | 2024-06-27T11:04:00Z | https://github.com/MonetDB/MonetDB/issues/561 | 753,277,641 | 561 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 02:14:32 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-23 11:55:37 +0200
## Comment 3084
Date: 2005-05-23 14:14:32 +0200
From: Wouter Alink <<alink>>
MIL statement 'string_join' expects sorted BAT
The query:
xquery("xml","for $t in (text { \"Hello \" }, text {
\"my \" }, \"World\")\n\
where string($t) != \"my \"\n\
return text { $t }");
returns:
!ERROR: !ERROR: string_join: input BAT separator must
be sorted on head.
!ERROR: CMDstring_join: operation failed.
## Comment 3085
Date: 2005-05-23 14:19:17 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
note: i guess it should return... cannot do: 'text { text {
.. } }'
The following returns the same error:
xquery("xml","text { text { \"test\" } } ");
## Comment 3086
Date: 2005-05-23 16:37:21 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
see also [ 1205565 ] XQuery: text constructor...
## Comment 3087
Date: 2005-05-23 23:55:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by improved sorted-property propagation in revision
1.34.2.1 of runtime/pf_support.mx .
## Comment 3088
Date: 2005-11-09 14:51:45 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1207029.*
## Comment 3089
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1207029 at http://sourceforge.net/support/tracker.php?aid=1207029
| XQuery: 'string_join' expects sorted BAT | https://api.github.com/repos/MonetDB/MonetDB/issues/560/comments | 0 | 2020-11-30T08:42:37Z | 2024-06-27T11:04:00Z | https://github.com/MonetDB/MonetDB/issues/560 | 753,277,619 | 560 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 12:31:56 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-23 02:57:02 +0200
## Comment 3080
Date: 2005-05-23 12:31:56 +0200
From: @drstmane
12:29:54 manegold@draco:~/Monet/Stable/pathfinder $ cat
/tmp/test.xq
<doc>
!this is a test
</doc>
12:30:11 manegold@draco:~/Monet/Stable/pathfinder $ pf
/tmp/test.xq | Mserver --set monet_prompt=''
Monet Database Server V4.8.0_rc1
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit; dynamically
linked.
Visit http://monetdb.cwi.nl/ for further information.
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<doc>
!this is a test
</doc>
</XQueryResult>
12:30:21 manegold@draco:~/Monet/Stable/pathfinder $
MapiClient -lxq /tmp/test.xq
<doc>
this is a test
</doc>
12:30:33 manegold@draco:~/Monet/Stable/pathfinder $
MapiClient -lxq -sxml /tmp/test.xq
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<doc>
this is a test
</doc>
</XQueryResult>
12:30:36 manegold@draco:~/Monet/Stable/pathfinder $
## Comment 3081
Date: 2005-05-23 14:57:02 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed in revision 1.13.2.1 of runtime/serialize.mx.
## Comment 3082
Date: 2005-12-19 08:57:54 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
BugsViaSourgeforce/Tests/ID.1206985.xq
## Comment 3083
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206985 at http://sourceforge.net/support/tracker.php?aid=1206985
| XQuery: MapiClient -lxquery "swallows" leading '!' in output | https://api.github.com/repos/MonetDB/MonetDB/issues/559/comments | 0 | 2020-11-30T08:42:34Z | 2024-06-27T11:03:59Z | https://github.com/MonetDB/MonetDB/issues/559 | 753,277,593 | 559 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 08:48:44 +0200
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2005-05-23 11:44:44 +0200
## Comment 3072
Date: 2005-05-23 08:48:44 +0200
From: @drstmane
When running XQuery queries with
Mserver ... &
MapiClient -lxquery *.xq
instead of
pf *.xq | Mserver ...
errors issued by the XQuery compiler (Pathfinder),
respectively the generated MIL code are displayed with
an extra 'ERROR: ' prefix, e.g.:
ERROR: !ERROR: division by 0 is forbidden
^^^^^^^
(cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU_32-d_Fedora3/tests_XQuery/div.err.00.html
)
Well, if this is rather a (MAPI?-)"feature" than a bug,
that's fine with me; I just need to know...
## Comment 3073
Date: 2005-05-23 10:30:06 +0200
From: @peterboncz
Logged In: YES
user_id=591107
it is not a mapi feature, rather MIL.
the MIL code in pathfinder.mx CATCH-es all errors in thiugs
like var err := CATCH(statement)
if an error occurred, it is raised later:
is (not(isnil(err))) ERROR(err)
what will probably work is cutting off the error prefix from th
err varoiable (that holds the error message generated in the
Catch BLOCK9
## Comment 3074
Date: 2005-05-23 10:49:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
Note, with "MapiClient -lxquery *.xq" resp. " pf *.xq" I do
not mean that I want to use multiple files on the command
line --- a single file is just fine --- the "*" should here
just indicate that I mean any (single) .xq file...
## Comment 3075
Date: 2005-05-23 10:59:39 +0200
From: @grobian
Logged In: YES
user_id=963970
just my 2 cents:
MapiClient (mapi?) interprets each line starting with an !
as error, and so it prints it's contents prefixed by ERROR:
... To avoid having double ERROR, the error message should
simply be: "!division by zero is forbidden". The ! could be
omitted in the output.
## Comment 3076
Date: 2005-05-23 11:08:42 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Maybe related:
the document test.xq:
<doc>
!this is a test
</doc>
returns as:
[alink@volans test-data]$ MapiClient -lxquery test.xq
<doc>
this is a test
</doc>
without the !....
## Comment 3077
Date: 2005-05-23 11:44:43 +0200
From: @drstmane
Logged In: YES
user_id=572415
Well, I understand, now, that this extra "ERROR: " is indeed
a feature (at least for this release).
Hence, I'll approve the respective output, and close this
bug report.
I'll create at new bug report with Wouter's bug.
## Comment 3078
Date: 2005-12-19 08:46:12 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
bug found by the Xquery tests
## Comment 3079
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206853 at http://sourceforge.net/support/tracker.php?aid=1206853
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: "odd" format of error messages with "MapiClient -lx" | https://api.github.com/repos/MonetDB/MonetDB/issues/558/comments | 0 | 2020-11-30T08:42:31Z | 2024-06-28T07:36:38Z | https://github.com/MonetDB/MonetDB/issues/558 | 753,277,549 | 558 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 08:39:32 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-23 04:44:56 +0200
## Comment 3067
Date: 2005-05-23 08:39:32 +0200
From: @drstmane
When running XQuery queries with
Mserver ... &
MapiClient -lxquery *.xq
instead of
pf *.xq | Mserver ...
warnings issued by the XQuery compiler (Pathfinder)
seem to get lost.
See (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU_32-d_Fedora3/tests_XQuery/let_for2.err.00.html
## Comment 3068
Date: 2005-05-23 10:49:48 +0200
From: @drstmane
Logged In: YES
user_id=572415
Note, with "MapiClient -lxquery *.xq" resp. " pf *.xq" I do
not mean that I want to use multiple files on the command
line --- a single file is just fine --- the "*" should here
just indicate that I mean any (single) .xq file...
## Comment 3069
Date: 2005-05-23 16:44:56 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
## Comment 3070
Date: 2005-12-19 08:40:28 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
Many tests exist for this bug, example tests_XQuery/let_for2
## Comment 3071
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206852 at http://sourceforge.net/support/tracker.php?aid=1206852
| XQuery: warnings get lost with "MapiClient -lxquery" | https://api.github.com/repos/MonetDB/MonetDB/issues/557/comments | 0 | 2020-11-30T08:42:28Z | 2024-06-27T11:03:57Z | https://github.com/MonetDB/MonetDB/issues/557 | 753,277,517 | 557 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 08:29:39 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2005-05-25 12:47:47 +0200
## Comment 3062
Date: 2005-05-23 08:29:39 +0200
From: @drstmane
Test sql/src/backends/monet4/Tests/smack01 fails with
"!ERROR: initClient: Out of client slots";
see (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU_32-d_Fedora3/src_backends_monet4/smack01.out.00.html
## Comment 3063
Date: 2005-05-23 09:59:07 +0200
From: @njnes
Logged In: YES
user_id=43556
Client slots problem is fixed. We needed a closeClient call.
Now smack01 fails because we are running out of memory.
## Comment 3064
Date: 2005-05-25 00:47:47 +0200
From: @njnes
Logged In: YES
user_id=43556
also fixed the memory leak
## Comment 3065
Date: 2005-12-19 08:38:01 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
smack01 caused problems
## Comment 3066
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206849 at http://sourceforge.net/support/tracker.php?aid=1206849
| SQL: test smack01 fails with "Out of client slots" | https://api.github.com/repos/MonetDB/MonetDB/issues/556/comments | 0 | 2020-11-30T08:42:25Z | 2024-06-27T11:03:56Z | https://github.com/MonetDB/MonetDB/issues/556 | 753,277,489 | 556 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-23 08:16:45 +0200
From: @drstmane
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-06-08 11:58:30 +0200
## Comment 3056
Date: 2005-05-23 08:16:45 +0200
From: @drstmane
On Darwin (at least version 7.9.0), dropping modules
that define new atoms failes with (e.g.)
========
!ERROR: unloadmod_check_use: drop(_monettime) failed:
monet_fcn_tpe[oid,int] has 1 reference.
========
See (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_32-d_Darwin7.9.0/src_monet/modrefcnt1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_32-d_Darwin7.9.0/src_monet/modrefcnt2-is.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_32-d_Darwin7.9.0/src_monet/modrefcnt2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_32-d_Darwin7.9.0/tests_Availability/02_Modules_plain.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_32-d_Darwin7.9.0/tests_BugReports/no.166.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_32-d_Darwin7.9.0/tests_sigs/none.out.00.html
## Comment 3057
Date: 2005-05-28 16:40:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
This seems to be a bug in the Apple version of gcc 3.3
(gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495 &
1671):
when configured with "--enable-debug", and hence compiled
with "-g", everything seems to work fine; without
"--enable-debug", i.e., when compiled with the default "-g
-O2" and with "--enable-optimize" ("-O6") things go wrong.
Hence, we postpone this bug for now...
## Comment 3058
Date: 2005-06-08 23:58:30 +0200
From: @njnes
Logged In: YES
user_id=43556
Apple fixed the gcc bug. So on Darwin-8.1.0 (gcc-4) this is
now fixed
## Comment 3059
Date: 2005-06-09 07:50:41 +0200
From: @njnes
Logged In: YES
user_id=43556
Apple fixed the gcc bug. So on Darwin-8.1.0 (gcc-4) this is
now fixed
## Comment 3060
Date: 2005-12-19 08:16:06 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
bug was found by the tests modrefcnt1,2 .
## Comment 3061
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206844 at http://sourceforge.net/support/tracker.php?aid=1206844
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.
| Dropping modules with atoms fails on Darwin | https://api.github.com/repos/MonetDB/MonetDB/issues/555/comments | 0 | 2020-11-30T08:42:22Z | 2024-06-28T07:36:38Z | https://github.com/MonetDB/MonetDB/issues/555 | 753,277,449 | 555 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-22 09:12:48 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-05-22 10:39:58 +0200
## Comment 3052
Date: 2005-05-22 21:12:48 +0200
From: @grobian
% MapiClient -lsql
sql>create table t (t timestamp with time zone);
6 querytype
sql>insert into t values (now());
4 querytype
[ 1 ]
sql>select * from t;
3 querytype
t table_name
t name
timestamp type
25 length
1 tuplecount
2 id
[ 2005-05-22 19:11:12.000 ]
sql>
as can be observed in the example above, the server
does NOT return a timestamp with time zone, ie. the
+00:00 part is missing.
## Comment 3053
Date: 2005-05-22 22:39:58 +0200
From: @njnes
Logged In: YES
user_id=43556
the type of the column was timestamp not timestamptz (this
is fixed in the parser).
## Comment 3054
Date: 2005-12-19 08:14:06 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
THis is for example tested with the jdbc test Test_PStimezone
## Comment 3055
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206643 at http://sourceforge.net/support/tracker.php?aid=1206643
| SQL: timestamps with time zone returned incorrectly | https://api.github.com/repos/MonetDB/MonetDB/issues/554/comments | 0 | 2020-11-30T08:42:19Z | 2024-06-27T11:03:54Z | https://github.com/MonetDB/MonetDB/issues/554 | 753,277,422 | 554 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-22 02:38:36 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-23 10:58:33 +0200
## Comment 3048
Date: 2005-05-22 14:38:36 +0200
From: @drstmane
(Most probably) since the latest changes to Io.c (see
below), Mx failse to set/use the target directory
specified via "-R":
========
14:35:46 manegold@draco:~/Monet/Stable/MonetDB/doc $ l
/tmp/stm
ls: /tmp/stm: No such file or directory
14:36:05 manegold@draco:~/Monet/Stable/MonetDB/doc $ Mx
-R/tmp -H1 -w "mil.mx"
Mx(fmustopen:):Can't create directory
[mil.mx:1].
14:36:14 manegold@draco:~/Monet/Stable/MonetDB/doc $ Mx
-R/tmp/stm -H1 -w "mil.mx"
Invalid target directory (/tmp/stm), using "." instead
mil.mx: ./mil.html - not modified
14:36:20 manegold@draco:~/Monet/Stable/MonetDB/doc $
========
This causes "make docs" to fail.
===================================================================
2005/04/29 - sjoerd: Io.c,1.28
On Windows, make mel and Mx understand / as file name
separators in
addition to \.
===================================================================
## Comment 3049
Date: 2005-05-23 10:58:32 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed in Io.c revision 1.28.2.1.
## Comment 3050
Date: 2005-12-19 08:11:55 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / COMPILATION
Mx is part of the buildtools, ie cannot be tested with mtest
## Comment 3051
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206512 at http://sourceforge.net/support/tracker.php?aid=1206512
| Mx fails to set/use target directory with "-R" option | https://api.github.com/repos/MonetDB/MonetDB/issues/553/comments | 0 | 2020-11-30T08:42:16Z | 2024-06-27T11:03:53Z | https://github.com/MonetDB/MonetDB/issues/553 | 753,277,394 | 553 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-22 10:50:06 +0200
From: @drstmane
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-05-25 04:21:04 +0200
## Comment 3043
Date: 2005-05-22 10:50:06 +0200
From: @drstmane
At least during testing, loading module "salgebra"
causes a segfault on SuSE 9.3 & Fedora Core 3 (both on
x86_64; the latter with both gcc & icc); cf.:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/GNU_64-d_SuSE9.3/tests_Availability/02_Modules_plain.out.00.html
## Comment 3044
Date: 2005-05-25 12:26:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
The problem only occurs, if the test script
(tests_Availability/Tests/02_Modules_plain.milS) is read
from stdin (piped, re-directed, or cut-and-pasted into the
console; test requires to run test
tests_Availability/00_Mserver, first).
Then, BBPdestroy() seems to be called on a BAT, whos head
appear to be corrupted, at least the tailtype is wrongly set
to "-42"(!):
========
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912516686080 (LWP 22276)]
0x00002aaaab8bd006 in BBPdestroy (b=0x6f0a48) at gdk_bbp.mx:1650
1650 int (*tunfix) (ptr) =
BATatoms[b->ttype].atomUnfix;
(gdb) bt
0 0x00002aaaab8bd006 in BBPdestroy (b=0x6f0a48) at
gdk_bbp.mx:1650
1 0x00002aaaab8bb870 in decref (i=37, logical=0, lock=1)
at gdk_bbp.mx:1319
2 0x00002aaaab8bb0f2 in BBPdecref (i=37, logical=0) at
gdk_bbp.mx:1340
3 0x00002aaab4596ca7 in salgebra_epilogue () at
salgebra.mx:1123
4 0x00002aaab4593bbd in _salgebra_Module_Delete
(user=0x376eb15300 "") at salgebra.glue.c:372
5 0x00002aaaaab15121 in TBL_unloadmod
(client=0x2aaaaac37d20, module=0x72bf70 "_salgebra",
level=1) at monet_tbl.mx:2110
6 0x00002aaaaab152b7 in TBL_unloadmod
(client=0x2aaaaac37d20, module=0x717bf8 "salgebra", level=0)
at monet_tbl.mx:2128
7 0x00002aaaaaadc636 in dropClient (c=0x2aaaaac37d20,
lt=0x6d7b18) at monet_client.mx:790
8 0x00002aaaaaff5126 in CMDdrop (stk=515, lt=0x6d7b18,
res=0x7fffffffe570) at builtin.mx:370
9 0x00002aaaaaabccd5 in interpret (stk=515, lt=0x6d7b18,
res=0x7fffffffe570) at monet_interpreter.mx:846
10 0x00002aaaaaac5acf in interpret_seqblock (stk=515,
lt=0x581318, res=0x7fffffffe570, scope=1) at
monet_interpreter.mx:1776
11 0x00002aaaaaabc43f in interpret (stk=0, lt=0x581318,
res=0x7fffffffe570) at monet_interpreter.mx:756
12 0x00002aaaaaacf9c7 in tuple_interpret_vpval_vpval
(head=0x717bf8, tail=0x719d00, handle=0x5b9dd8) at
monet_interpreter.mx:2191
13 0x00002aaaaaee114e in doCMDbatloop (b=0x688258,
handle=0x7fffffffe880, low=0, high=27) at bat.mx:1583
14 0x00002aaaaaee13b3 in CMDbatloop_std (b=0x688258,
handle=0x7fffffffe880) at bat.mx:1629
15 0x00002aaaaaeda76f in CMDbatloop_std_unpack218853434
(argc=3, argv=0x7fffffffe860) at bat.glue.c:1601
16 0x00002aaaaaad41cf in interpret_iterator (stk=0,
lt=0x570f28, parallel=1) at monet_interpreter.mx:2138
17 0x00002aaaaaabca24 in interpret (stk=0, lt=0x570f28,
res=0x7fffffffee30) at monet_interpreter.mx:802
18 0x00002aaaaaac5acf in interpret_seqblock (stk=0,
lt=0x6e5d48, res=0x7fffffffee30, scope=0) at
monet_interpreter.mx:1776
19 0x00002aaaaaabc43f in interpret (stk=0, lt=0x6e5d48,
res=0x7fffffffee30) at monet_interpreter.mx:756
20 0x00002aaaaaad831f in handleRequest (t=0x2aaaabc1c200,
q=0x6b5898, res=0x7fffffffee30) at monet_queue.mx:534
21 0x00002aaaaaad8759 in doRequest (t=0x2aaaabc1c200,
preference=0x0) at monet_queue.mx:560
22 0x00002aaaaab27438 in monetInterpreter
(status=0x7fffffffee98) at monet_process.mx:112
23 0x0000000000402574 in main (argc=2, av=0x7fffffffefa8)
at Mserver.mx:442
(gdb) li
1645 bat bid = ABS(b->batCacheid), parent =
VIEWparent(b);
1646
1647 if (!parent) {
1648 /* bats that get destroyed must
unfix their atoms */
1649 int (*hunfix) (ptr) =
BATatoms[b->htype].atomUnfix;
1650 int (*tunfix) (ptr) =
BATatoms[b->ttype].atomUnfix;
1651 BUN p, q;
1652 int xx;
1653
1654 assert(b->batSharecnt == 0);
(gdb) print b
$1 = (BAT *) 0x6f0a48
(gdb) print *b
$2 = {GDKversion = 20749, batCacheid = 37, dims = {headtype
= 5 '\005', tailtype = -42 '\uffff', headloc = 56, tailloc =
0, headkey = 0 '\0', tailkey = 0 '\0',
headvarsized = 0 '\0', tailvarsized = 0 '\0', bunshift =
6 '\006', bunwidth = 64, hseq = 0, tseq = 0}, batBuns =
0x6f0b80, hhash = 0x0, thash = 0x0,
H = 0x6f0ac0, T = 0x6f0b10, P = 0x6f0b60, U = 0x6f0b80,
void_tid = 0, void_cnt = 0, void_seq1 = 0, void_seq2 = 0}
(gdb) print BATprint(b)
Program received signal SIGSEGV, Segmentation fault.
0x00002aaaab972de9 in BATmultiprintf (s=0x505f00, argc=1,
argv=0x7fffffffd588, printhead=1, order=0, printorder=1) at
gdk_storage.mx:978
978 c[j + 1].format =
printfcn(argv[j]);
The program being debugged was signaled while in a function
called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function
(BATprint) will be abandoned.
(gdb)
========
Any one any idea, where to start/continue debugging?
## Comment 3045
Date: 2005-05-25 16:21:03 +0200
From: @njnes
Logged In: YES
user_id=43556
the atoms where unloaded before the epiloge was called.
Therefor the epiloge unfixed a bat with unknown types,
leading to the crash.
## Comment 3046
Date: 2005-12-19 08:09:24 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
loading of modules is done by the availability tests
## Comment 3047
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206446 at http://sourceforge.net/support/tracker.php?aid=1206446
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.
| loading mod. salgebra segfaults on SuSE 9.3/64 & Fedore 3/64 | https://api.github.com/repos/MonetDB/MonetDB/issues/552/comments | 0 | 2020-11-30T08:42:13Z | 2024-06-27T11:03:52Z | https://github.com/MonetDB/MonetDB/issues/552 | 753,277,361 | 552 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-22 09:16:50 +0200
From: @njnes
To: @njnes
Version: -- development
Last updated: 2005-05-23 07:48:59 +0200
## Comment 3039
Date: 2005-05-22 09:16:50 +0200
From: @njnes
Test tests/by_Peter/Tests/tst_append_readonly.milM
crashes. This
test tests mmapped bats changing access from readonly
to append and back (after inserts).
## Comment 3040
Date: 2005-05-23 19:48:58 +0200
From: @njnes
Logged In: YES
user_id=43556
seems fixed after the fixes in BATsetaccess
## Comment 3041
Date: 2005-12-19 08:07:52 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
crash was in a test
## Comment 3042
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1206432 at http://sourceforge.net/support/tracker.php?aid=1206432
| access(BAT_READ/BAT_APPEND) crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/551/comments | 0 | 2020-11-30T08:42:09Z | 2024-06-27T11:03:51Z | https://github.com/MonetDB/MonetDB/issues/551 | 753,277,328 | 551 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-20 12:56:54 +0200
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-23 11:54:58 +0200
## Comment 3031
Date: 2005-05-20 12:56:54 +0200
From: Wouter Alink <<alink>>
The grammar in the XQuery specification allows to do:
text { <node/> }
But this is not accepted, nor rejected by Pathfinder.
The following error is returned:
MonetDB>xquery("xml","text { <node/> }");
!ERROR: string_join: input BAT separator must be sorted
on head.
!ERROR: CMDstring_join: operation failed.
## Comment 3032
Date: 2005-05-20 13:09:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
well, apparently, it is accepted by Pathfinder, only the
generated MIL code does not work properly (either because
it's wrong, or because there is a (property-)bug "somewhere"
--- need to investigate it ...
Jan(R), would you have an "immediate" idea?
Wouter, what should be the "correct"/expected output?
## Comment 3033
Date: 2005-05-20 13:13:20 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
i guess it would be an empty string (but i am not sure)
## Comment 3034
Date: 2005-05-21 15:00:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
The error happens in the last string_join operator. If I replace
the (one row) relation
iter_str := iter_str.string_join(iter.tunique().project(" "));
by
var foobar := iter.tunique().project(" ");
foobar := foobar.sort();
iter_str := iter_str.string_join(foobar);
it works.
So some properties have to be fixed -- but probably not by me
:)
## Comment 3035
Date: 2005-05-23 16:37:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
see also 1207029 ] XQuery: 'string_join' expects sorted BAT
## Comment 3036
Date: 2005-05-23 23:54:58 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by improved sorted-property propagation in revision
1.34.2.1 of runtime/pf_support.mx .
## Comment 3037
Date: 2005-12-19 00:44:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1205565*
## Comment 3038
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1205565 at http://sourceforge.net/support/tracker.php?aid=1205565
| XQuery: text constructor... | https://api.github.com/repos/MonetDB/MonetDB/issues/550/comments | 0 | 2020-11-30T08:42:06Z | 2024-06-27T11:03:50Z | https://github.com/MonetDB/MonetDB/issues/550 | 753,277,292 | 550 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-19 04:23:30 +0200
From: Steffen Goeldner <<sgoeldner>>
To: @njnes
Version: -- development
Last updated: 2005-05-20 02:58:45 +0200
## Comment 3023
Date: 2005-05-19 16:23:30 +0200
From: Steffen Goeldner <<sgoeldner>>
OS: Windows 2000
Compiler: MS VC++ Toolkit 2003
Parser tools: UnxUtils
Running
bin\MapiClient.exe -c etc\MonetDB.conf -l sql
shows
MAPI = monetdb@localhost:45123
ACTION= mapi_start_talking
ERROR = Challenge string is not valid
and the server crashes.
## Comment 3024
Date: 2005-05-19 18:42:29 +0200
From: @grobian
Logged In: YES
user_id=963970
This is actually two bugs:
1) the server should not crash on a prematurely
disconnecting client
2) the server should send a valid challenge string
(something which has two colons `:' in it, because that's
what the error indicates)
## Comment 3025
Date: 2005-05-19 18:46:40 +0200
From: @grobian
Logged In: YES
user_id=963970
perhaps this bug is related to
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1204471&group_id=56967
?
## Comment 3026
Date: 2005-05-19 19:28:31 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
No, it's not really related. The bug you refer to has been
fixed, and the problem still persists.
It could well be that the same set of changes caused the
current bug, but it's certainly a different one.
## Comment 3027
Date: 2005-05-20 11:11:48 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The problem is very definitely in Peter's new mapi code,
hence I assign the bug to him.
The following problems exist in the code that handles the
case where cmd is not "" in MAPIlisten:
- argv[0] is the return type, so fds should have length 3,
and fds[1] and fds[2] should be filled in instead of fds[0]
and fds[1]. In addition, in the call to TBL_normal_resolve
the argument count should be 3 instead of 2. Fixing this
will make that the function that is looked for will be found.
- The return value of TBL_normal_resolve should be checked.
The immediate cause of the Mserver crash was that the
function pointer that was filled in here was NULL because
the call to TBL_normal_resolve failed.
- In the case of the SQL server, the function being called
is SQLclient which is a PROC, not a BUILTIN. Hence the
hard-coded value TOK_BUILTIN is not correct.. Changing it
to TOK_PROC doesn't work, though, so something else needs to
be done. In any case, the type of the function needs to be
determined dynamically.
## Comment 3028
Date: 2005-05-20 14:58:45 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Niels fixed this the easy way.
It might be "better" to do a more general fix and allow
PROCs in addition to BUILTINs, but BUILTINs are enough for
our purposes (and it seems allowing PROCs isn't quite as
easy as I'd have liked).
## Comment 3029
Date: 2005-11-09 15:06:09 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / REDUNDANT
MapiClient is tests with MIL, SQL, & XQuery (at least on Unix)
## Comment 3030
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1205010 at http://sourceforge.net/support/tracker.php?aid=1205010
| Challenge string is not valid | https://api.github.com/repos/MonetDB/MonetDB/issues/549/comments | 0 | 2020-11-30T08:42:03Z | 2024-06-27T11:03:49Z | https://github.com/MonetDB/MonetDB/issues/549 | 753,277,259 | 549 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-19 03:33:58 +0200
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-15 11:43:13 +0100
## Comment 3013
Date: 2005-05-19 15:33:58 +0200
From: Wouter Alink <<alink>>
Hello,
I was trying to execute the query in example 3.8.4 on
the XQuery specification page
(http://www.w3.org/TR/2005/WD-xquery-20050404/)
(see attachment)
It came back to me with:
!ERROR: merged_union: BAT 4 must have the same size as
BAT 2.
!ERROR: CMDmerged_union: operation failed.
I guess this is isn't the expected behaviour.
Another thing:
I tried to do:
let $bib := element { .... }
and
let $bib := document { .... }
as well. but this is not supported i guess, because
these returned errors as well.
## Comment 3014
Date: 2005-05-21 20:25:49 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This seems to be either a bug in merged_union or in one of
therein called functions --- at least the bats are aligned and no
error should be triggered :)
## Comment 3015
Date: 2005-05-23 16:36:49 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
see also [ 1207112 ] XQuery: merged_union fails
## Comment 3016
Date: 2005-05-23 20:07:15 +0200
From: @drstmane
Logged In: YES
user_id=572415
This bug is most probably caused by bug
[ 1207243 ] "handling of property reverse-sortedness is
absolutely bogus".
## Comment 3017
Date: 2005-05-25 04:20:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
627 days after it was born on Friday Sep 05 2003:
Fixed implementation of reverse sorting.
Now, update operations also unset the reverse sortedness
property,
in case the updates do destroy the sort order!
Fixed some more places so that checking for sortedness looks
only
at the lowest bit of [ht]sorted, and setting sortedness assigns
GDK_SORTED instead of 1 to [ht]sorted.
These changes fix the BUGs
1204965 "XQuery: Example from W3C fails"
1207112 "XQuery: merged_union fails"
TODO:
Make BATpropcheck aware of reverse sortedness!
## Comment 3018
Date: 2005-11-09 14:54:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1204965
## Comment 3019
Date: 2005-12-21 00:19:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
re-opened as the respective test fails with a segfault in
Mserver:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1204965-a.err.00.html
## Comment 3020
Date: 2006-01-13 22:21:53 +0100
From: @drstmane
Logged In: YES
user_id=572415
This seems to be the same on-the-fly shredding bug as
1405188 "PF: shredding documents on-the-fly via fn:doc()
fails".
cf.
https://sourceforge.net/tracker/index.php?func=detail&aid=1405188&group_id=56967&atid=482468
## Comment 3021
Date: 2006-01-15 11:43:13 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by back-porting Peter's "tentative" fix for http://sourceforge.net/support/tracker.php?aid=1405188 "PF: shredding documents on-the-fly via fn:doc() fails"
1377006 "XQuery: shredding-on-the-fly"
1204965 "XQuery: Example from W3C fails"
from the XQuery_0-9_update branch to the main trunk.
## Comment 3022
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1204965 at http://sourceforge.net/support/tracker.php?aid=1204965
| XQuery: Example from W3C fails | https://api.github.com/repos/MonetDB/MonetDB/issues/548/comments | 0 | 2020-11-30T08:42:00Z | 2024-06-27T11:03:47Z | https://github.com/MonetDB/MonetDB/issues/548 | 753,277,227 | 548 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-18 08:38:28 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-19 11:00:32 +0200
## Comment 3008
Date: 2005-05-18 20:38:28 +0200
From: @drstmane
With the latest changes in src/mapi/mapi.mx, tests
src/mapi/Tests/manyMapiClients
(1234 MAPI connextions from a Python script)
&
src/mapi/examples/C/Tests/smack01
(1000 MAPI connections from a C program)
cause a segfault in the Mserver fail after 252
connections when run via Mtest:
Mtest_MonetDB src/mapi/Tests/ manyMapiClients
Mtest_MonetDB src/mapi/examples/C/Tests/ smack01
When run "by hand", Mserver segfaults after 1275
connections (requires two subsequent invocations of the
tests in any combination on the same Mserver):
Mserver --dbinit='module(mapi); mapi_start();' &
$MONETDB_PREFIX/lib/MonetDB/Tests/smack01 50000
MAPIPORT=50000 python
src/mapi/Tests/manyMapiClients.MAPI.py
I have not analysed this any further, yet, but might
have a closer look at it tomorrow morning...
## Comment 3009
Date: 2005-05-19 10:38:39 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
It looks like the problem is due to stack overflow:
I managed to get a core dump and looked at the difference of
the addresses of local variables in the top-most and
bottom-most function in the stack. The difference was about
2 million. The stack which is allocated for new threads is
2 MB.
I'll investigate further which function is the culprit.
But in general I can say that alloca is dangerous. You have
to be very sure that the amount of memory allocated on the
stack is bounded and low!
## Comment 3010
Date: 2005-05-19 11:00:32 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
There was a newly introduced alloca in a loop in MAPIlisten.
By replacing this with an automatically allocated buffer,
the bug was fixed.
Lesson: do not *ever* use alloca in a loop. Memory is
allocated in each iteration, but it is only released when
the function returns.
## Comment 3011
Date: 2005-11-09 14:53:43 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / REDUNDANT
bug refers to existing tests
## Comment 3012
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1204471 at http://sourceforge.net/support/tracker.php?aid=1204471
| latest mapi.mx causes segfault in Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/547/comments | 0 | 2020-11-30T08:41:57Z | 2024-06-27T11:03:46Z | https://github.com/MonetDB/MonetDB/issues/547 | 753,277,197 | 547 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-18 11:30:41 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-05-18 11:46:14 +0200
## Comment 3005
Date: 2005-05-18 11:30:41 +0200
From: @drstmane
Since Peter's recent changes, MonetDB fails to compile
with icc due to:
========
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.ntv_32-d.11516/MonetDB/src/gdk -I../..
-I/var/tmp/monet.ntv_32-d.11516/MonetDB/src/gdk
-I../common -DLIBGDK -we140 -wd1418 -c99 -Wall -w2 -mp1
-O3 -restrict -unroll -tpp6 -axKWNPB -DHWCOUNTERS
-DHW_Linux -DHW_i686 -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-D_REENTRANT -c gdk_bbp.c -KPIC -DPIC -o
.libs/libbat_la-gdk_bbp.o
/var/tmp/monet.ntv_32-d.11516/MonetDB/src/gdk/gdk_bbp.mx(494):
error 593: variable "recover" was set but never used
int i = 0, recover = FALSE, max_stamp = 0,
min_stamp = 0x7fffffff;
^
compilation aborted for gdk_bbp.c (code 2)
make[4]: *** [libbat_la-gdk_bbp.lo] Error 1
========
I'm not quite sure, whether this variable was simply
"forgotten", and we could hence remove it, or whether
this indecates that some other code using this variable
has been forgotten...
## Comment 3006
Date: 2005-11-09 14:52:39 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / COMPILATION
## Comment 3007
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1204158 at http://sourceforge.net/support/tracker.php?aid=1204158
| MonetDB fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/546/comments | 0 | 2020-11-30T08:41:53Z | 2024-06-27T11:03:45Z | https://github.com/MonetDB/MonetDB/issues/546 | 753,277,162 | 546 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-18 09:00:11 +0200
From: @Teggy
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2005-05-24 12:31:13 +0200
## Comment 3001
Date: 2005-05-18 09:00:11 +0200
From: @Teggy
In serialization mode `dm', i.e., while doing
$ MapiClient -lxquery -sdm foo.xq
atomic values of type xs:boolean are serialized as
true()
false()
while they should be serialized as
true
false
## Comment 3002
Date: 2005-05-24 11:58:25 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Fixed it!
## Comment 3003
Date: 2005-11-09 15:05:11 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: TEST ADDED / SUCCESS
pathfinder/tests/BugDay_2005-11-09_0.8/Tests/boolean_dm.SF-1204097.*
## Comment 3004
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1204097 at http://sourceforge.net/support/tracker.php?aid=1204097
| Serialization mode `dm': values of type xs:boolean | https://api.github.com/repos/MonetDB/MonetDB/issues/545/comments | 0 | 2020-11-30T08:41:50Z | 2024-06-27T11:03:44Z | https://github.com/MonetDB/MonetDB/issues/545 | 753,277,129 | 545 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-18 08:57:52 +0200
From: @Teggy
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-24 02:16:35 +0200
## Comment 2996
Date: 2005-05-18 08:57:52 +0200
From: @Teggy
Inside (constructed) elements, the serialization of atomic
values of type xs:boolean goes wrong (this happens
independent
of the mode of serialization [ dm, xml ]):
$ cat compare.xq
<x> { 3 > 5, fn:true() } </x>
$ pf compare.xq | Mserver --set monet_prompt=''"
[...]
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<x>0@0 1@0</x>
</XQueryResult>
While one would expect the result
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<x>false true</x>
</XQueryResult>
Note that outside element constructors, the
serialization seems OK:
$ cat compare-noelem.xq
3 > 5, fn:true()
$ pf compare-noelem.xq | Mserver --set monet_prompt=''"
[...]
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<x>false true</x>
</XQueryResult>
## Comment 2997
Date: 2005-05-24 11:54:29 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
I do not think this is a serialization problem. During
serialization the result within the <x></x> tags is just one
PFTEXT element containing the "0@0 1@0" string. So the
result string within the is created during query processing
and not during serialization. Am I right Jan (R)???
## Comment 2998
Date: 2005-05-24 14:16:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Didn't think about the cast from boolean to string...
Added special treating, were boolean values are mapped to
the strings "true" and "false".
## Comment 2999
Date: 2005-11-09 14:49:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: ALREADY IN TESTWEB
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1204095*
## Comment 3000
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1204095 at http://sourceforge.net/support/tracker.php?aid=1204095
| Atomic values of type xs:boolean serialization bug | https://api.github.com/repos/MonetDB/MonetDB/issues/544/comments | 0 | 2020-11-30T08:41:47Z | 2024-06-27T11:03:43Z | https://github.com/MonetDB/MonetDB/issues/544 | 753,277,099 | 544 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-17 12:34:12 +0200
From: @MarcinZukowski
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-05-19 06:57:40 +0200
## Comment 2987
Date: 2005-05-17 12:34:12 +0200
From: @MarcinZukowski
Due to our choice of marking 'metadata' rows with ''
sign, just like comments, the testing framework fails
to detect changes like column names or data types,
which might be relevant to front ends.
This is related to a http://sourceforge.net/support/tracker.php?aid=1203431, the change in bat
printing was not noticed by the testing.
## Comment 2988
Date: 2005-05-17 13:16:05 +0200
From: @grobian
Logged In: YES
user_id=963970
this is due to the misuse of the comment ().
MCL fixes this more or less...
## Comment 2989
Date: 2005-05-18 20:16:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
Mtest.py and thus testing relys on ignoring *comment* lines
starting with ''.
(Why? Try "Mtest_MonetDB -I'' -r scripts/gold/ tst100" and
you'll see ...)
Obviously, for historic (i.e., legacy) reasons, MonetDB uses
also for non-comments, e.g., '' to mark BAT headers.
Hence, this is not a testing bug, but a "protocol" bug.
(The subject is a bit misleading...)
## Comment 2990
Date: 2005-05-19 11:43:34 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
I agree it's a protocol error, but I think that Mtest could
recognize a set of standard 'comment' lines like ' name'
and ' type'.
## Comment 2991
Date: 2005-05-19 18:48:34 +0200
From: @grobian
Logged In: YES
user_id=963970
I think in that case you should try to do it :p
## Comment 2992
Date: 2005-05-19 18:57:40 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
There are things sane people do not touch :)
I'm closing it.
## Comment 2993
Date: 2005-05-19 19:33:23 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I'm not going to reopen this, but a fairly simple solution
would certainly be possible: Just use a different first
character on these metadata lines. That would be a simple
change in the SQL backend (sql_result.mx), and corresponding
changes in Mapi.mx.
And then you'd have to fix all the tests.
## Comment 2994
Date: 2005-11-09 14:51:53 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / DESIGN
## Comment 2995
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1203453 at http://sourceforge.net/support/tracker.php?aid=1203453
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.
| Testing doesn't detect metadata changes | https://api.github.com/repos/MonetDB/MonetDB/issues/543/comments | 0 | 2020-11-30T08:41:44Z | 2024-06-28T07:36:37Z | https://github.com/MonetDB/MonetDB/issues/543 | 753,277,058 | 543 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-17 11:49:58 +0200
From: @MarcinZukowski
To: @njnes
Version: -- development
Last updated: 2005-05-17 02:37:12 +0200
## Comment 2981
Date: 2005-05-17 11:49:58 +0200
From: @MarcinZukowski
Simple example:
b:=new(int,int).insert(0,3).insert(1,4);
b:=b1.roles("bhead","btail");
b.print();
generates:
bhead tmp_33 name
int int type
-----------------
[ 0, 3 ]
[ 1, 4 ]
As you can see, tail name is incorrect.
## Comment 2982
Date: 2005-05-17 13:12:18 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Didn't c/p correctly, should be
var b:=new(int,int).insert(0,3).insert(1,4);
b:=b.roles("bhead","btail");
b.print();
## Comment 2983
Date: 2005-05-17 13:45:54 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
It seems the bug is actually in printing, not BATroles.
The following patch seems to help:
RCS file: /cvsroot/monetdb/MonetDB/src/gdk/gdk_storage.mx,v
retrieving revision 1.92
diff -r1.92 gdk_storage.mx
976,979c976
< if (!default_ident(argv[j]->tident))
< c[j + 1].tabs =
print_tabwidth(argv[j], BATgetId(argv[j]), c + (j + 1));
< else
< c[j + 1].tabs =
print_tabwidth(argv[j], argv[j]->tident, c + (j + 1));
---
> c[j + 1].tabs = print_tabwidth(argv[j],
argv[j]->tident, c + (j + 1));
But I don't want to commit it before somebody (Niels?) takes
a look.
## Comment 2984
Date: 2005-05-17 14:37:12 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Fixed, changes accepted by Niels.
## Comment 2985
Date: 2005-11-09 14:46:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: TEST ADDED / SUCCESS
MonetDB/tests/BugDay_2005-11-09_4.8/Tests/roles.SF-1203431.*
## Comment 2986
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1203431 at http://sourceforge.net/support/tracker.php?aid=1203431
| BATroles doesn't work | https://api.github.com/repos/MonetDB/MonetDB/issues/542/comments | 0 | 2020-11-30T08:41:41Z | 2024-06-27T11:03:41Z | https://github.com/MonetDB/MonetDB/issues/542 | 753,277,026 | 542 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-17 11:45:43 +0200
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-17 02:02:42 +0200
## Comment 2977
Date: 2005-05-17 11:45:43 +0200
From: @swingbit
debugmask(debugmask() and 2) causes ....
debugmask(debugmask() and 8) causes ....
This should probably be 'or' operations.
## Comment 2978
Date: 2005-05-17 14:02:42 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
You're right, and it has been fixed in CVS.
## Comment 2979
Date: 2005-11-09 14:39:24 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / DOCUMENTATION
## Comment 2980
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1203429 at http://sourceforge.net/support/tracker.php?aid=1203429
| incorrect documentation in bat.mx | https://api.github.com/repos/MonetDB/MonetDB/issues/541/comments | 0 | 2020-11-30T08:41:38Z | 2024-06-27T11:03:40Z | https://github.com/MonetDB/MonetDB/issues/541 | 753,276,992 | 541 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-13 09:11:51 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-22 05:17:19 +0200
## Comment 2963
Date: 2005-05-13 21:11:51 +0200
From: @grobian
After installing Portage for OSX and emerging libpcre,
everything went fine, till make hit the following error:
cc1: warnings being treated as errors
decimal.mx: In function 'decimal_length':
type
decimal.mx:955: warning: comparison is always true due
to limited range of data type
decimal.mx: In function 'decimal_convert':
decimal.mx:961: warning: comparison is always true due
to limited range of data type
decimal.mx:961: warning: comparison is always true due
to limited range of data type
decimal.mx: In function 'decimal_put':
decimal.mx:988: warning: comparison is always true due
to limited range of data type
decimal.mx:988: warning: comparison is always true due
to limited range of data type
make[5]: *** [lib_decimal_la-decimal.lo] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I think the MAX or MIN macros are the cause here, but I
don't see why or how to fix it.
## Comment 2964
Date: 2005-05-13 22:08:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
The problem is known, and rather related to/cause by gcc
4.0.0 than Darwin 8.0.0:
With gcc 4.0.0,
compiling decimal.mx fails complaining about
"comparison is always true due to limited range of data type"
in MAX() and MIN() in macro TOTLEN() in functions
decimal_length, decimal_convert, & decimal_put;
I have no idea, what the problem is --- hence,
we "mis-use" the NO_INLINE_CFLAGS to switch off -Werror
for decimal.mx (see conf/monet.m4 &
src/modules/plain/Makefile.ag).
However, do to necessary changes in autogen and hence the
generated Makefile, our "NO_INLINE_CFLAGS"/"NO_INLINE_FILES"
HACK does not
work any more in MonetDB 4.7 (while is still works in 4.6;
Niels and I are aware of the details). The goal is to
completely remove this HACK (as well as the
"NO_OPTIMIZE_FILES" HACK, and enable to set/overwrite the
default CFLAGS (perferable) per source-/object-file or (at
least) per library in the Makefile.ag's (as it is already
possible for LDFLAGS.
Until this is done, please use "configure --enable-warning"
to globally disable "-Werror", or add a line "X_CFLAGS =
$(NO_INLINE_CFLAGS)" to your local copy of
src/modules/plain/Makefile.ag to switch off -Werror locally
for all files in src/modules/plain/ .
Sorry for the inconvenience...
## Comment 2965
Date: 2005-05-13 22:37:04 +0200
From: @grobian
Logged In: YES
user_id=963970
ok. next issue:
c -Wno-long-long -D_REENTRANT -L/sw/lib -o lib_pcre.la
-rpath /Volumes/Scratch/monetdb/program/lib/MonetDB
lib_pcre_la-pcre.glue.lo lib_pcre_la-pcre.lo
../../common/libstream.la ../../gdk/libbat.la
../../monet/libmonet.la -lz -lbz2 -lpthread -ldl
-L/usr/lib -lpcre -lpcre
gcc -m32 -dynamiclib -flat_namespace -undefined suppress -o
.libs/lib_pcre.0.dylib .libs/lib_pcre_la-pcre.glue.o
.libs/lib_pcre_la-pcre.o
/Volumes/Scratch/monetdb/MonetDB/src/gdk/.libs/libbat.0.0.0.dylib
/Volumes/Scratch/monetdb/MonetDB/src/common/.libs/libstream.0.0.0.dylib
/Volumes/Scratch/monetdb/MonetDB/src/common/.libs/libmutils.0.0.0.dylib
-L/sw/lib ../../common/.libs/libstream.0.0.0.dylib
../../gdk/.libs/libbat.0.0.0.dylib
../../monet/.libs/libmonet.0.0.0.dylib -lz -lbz2 -lpthread
-ldl -L/usr/lib /usr/lib/libpcre -m32 -install_name
/Volumes/Scratch/monetdb/program/lib/MonetDB/lib_pcre.0.dylib
-compatibility_version 1 -current_version 1.0
powerpc-apple-darwin8-gcc-4.0.0: /usr/lib/libpcre: No such
file or directory
make[5]: *** [lib_pcre.la] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I have emerged libpcre and it is installed. However I don't
have a file called libpcre:
% la /usr/lib/libpcre*
-rwxr-xr-x 1 root portage 65092 May 13 20:39
/usr/lib/libpcre.0.0.1.dylib
lrwxrwxrwx 1 root wheel 19 May 13 20:39
/usr/lib/libpcre.0.dylib -> libpcre.0.0.1.dylib
-rw-r--r-- 1 root wheel 88680 May 13 20:39
/usr/lib/libpcre.a
lrwxrwxrwx 1 root wheel 19 May 13 20:39
/usr/lib/libpcre.dylib -> libpcre.0.0.1.dylib
-rwxr-xr-x 1 root wheel 765 May 13 20:39
/usr/lib/libpcre.la
-rwxr-xr-x 1 root portage 14332 May 13 20:39
/usr/lib/libpcreposix.0.0.0.dylib
lrwxrwxrwx 1 root wheel 24 May 13 20:39
/usr/lib/libpcreposix.0.dylib -> libpcreposix.0.0.0.dylib
-rw-r--r-- 1 root wheel 6544 May 13 20:39
/usr/lib/libpcreposix.a
lrwxrwxrwx 1 root wheel 24 May 13 20:39
/usr/lib/libpcreposix.dylib -> libpcreposix.0.0.0.dylib
-rwxr-xr-x 1 root wheel 820 May 13 20:39
/usr/lib/libpcreposix.la
## Comment 2966
Date: 2005-05-14 11:42:18 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fabian,
the problems seem the be the "-L/usr/lib /usr/lib/pcre" in
the last gcc command line; I have no idea, where this comes
from; I'd rather/only expect the "-L/usr/lib -lpcre" as it
appears earlier on that command line.
Since I don't have access to a tiger machine myself
(anymore), coul dyou please provide me with all Makefile* in
your <SOURCE>/src/modules/plain/ ,
<BUILD>/src/modules/plain/ & <BUILD>/ ? Further, it would be
helpful to have your <BUILD>/config.log and the console
output of your configure run
(in case you didn't keep it, maybe you could rerun configure
in a new build directory?).
Final remark: though on Tiger, you "only" configure/compile
a 32-bit Mserver;
that's fine, if this was your intension; if you prefer a
64-bit version, you need to run configure with
"--enable-bi1970-01-01 01:01:04 +0100".
## Comment 2967
Date: 2005-05-14 23:20:07 +0200
From: @grobian
Logged In: YES
user_id=963970
With some luck I will be able to carry a Tiger with me, and
with some patience you'll be able to watch it compile
yourself ;)
I attached the files you asked for as a tar.bz2, the
configure output follows:
% ./configure --prefix=/Volumes/Scratch/monetdb/program
--enable-bi1970-01-01 01:01:04 +0100
checking build system type... powerpc-apple-darwin8.0.0
checking host system type... powerpc-apple-darwin8.0.0
checking target system type... powerpc-apple-darwin8.0.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for egrep... grep -E
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... none
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking if your compiler is C99 compliant... yes
checking for java... /usr/bin/java
checking for Java >= 1.4... yes -> 1.4.2_07 found
checking for javac... /usr/bin/javac
checking for jar... /usr/bin/jar
checking for a sed that does not truncate output... /usr/bin/sed
checking for option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -p
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -m64 -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for ld used by gcc -m64... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking the maximum length of command line arguments... 65536
checking command to parse /usr/bin/nm -p output from gcc
-m64 object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc -m64 static flag works... yes
checking if gcc -m64 supports -fno-rtti -fno-exceptions... no
checking for gcc -m64 option to produce PIC... -fno-common
checking if gcc -m64 PIC flag -fno-common works... yes
checking if gcc -m64 supports -c -o file.o... yes
checking whether the gcc -m64 linker (/usr/bin/ld) supports
shared libraries... yes
checking how to hardcode library paths into programs...
immediate
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... darwin8.0.0 dyld
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++ -m64... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking whether the g++ -m64 linker (/usr/bin/ld) supports
shared libraries... yes
checking for g++ -m64 option to produce PIC... -fno-common
checking if g++ -m64 PIC flag -fno-common works... yes
checking if g++ -m64 supports -c -o file.o... yes
checking whether the g++ -m64 linker (/usr/bin/ld) supports
shared libraries... yes
checking how to hardcode library paths into programs...
immediate
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... darwin8.0.0 dyld
appending configuration tag "F77" to libtool
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking whether ln -s works... yes
checking for rm... rm -f
checking for mv... mv -f
checking for lockfile... lockfile -r 2
checking for bash... /bin/sh
checking for rpmbuild... no
checking for rpm... no
checking for swig... no
checking for python... /usr/bin/python
checking whether /usr/bin/python is >= 2.0... yes: 2.3
checking for /usr/bin/python's include directory...
/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3
checking for /usr/bin/python's library directory...
$prefix/lib/python2.3/site-packages
checking for perl... /usr/bin/perl
checking for /usr/bin/perl's include directory...
/System/Library/Perl/5.8.6/darwin-thread-multi-2level/CORE
checking for /usr/bin/perl's library directory...
$prefix//Network/Library/Perl/5.8.6/darwin-thread-multi-2level
checking for objc... no
checking for ANSI C header files... (cached) yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking semaphore.h usability... yes
checking semaphore.h presence... yes
checking for semaphore.h... yes
checking sched.h usability... yes
checking sched.h presence... yes
checking for sched.h... yes
checking for sem_init in -lpthreadGC1... no
checking for sem_init in -lpthreadGC... no
checking for sem_init in -lpthread... yes
checking for pthread_sigmask in -lpthread... yes
checking for pthread_kill_other_threads_np in -lpthread... no
checking readline/readline.h usability... yes
checking readline/readline.h presence... yes
checking for readline/readline.h... yes
checking for readline in -lreadline... no
checking for rl_history_search_forward in -lreadline... no
checking for rl_reverse_search_history in -lreadline... no
checking for dlopen in -ldl... yes
checking for malloc in -lmalloc... no
checking for mallopt... no
checking for mallinfo... no
checking for gethostbyname_r... no
checking for gethostbyname_r in -lnsl_r... no
checking for gethostbyname_r in -lnsl... no
checking for setsockopt... yes
checking for setsockopt in winsock2... no
checking for getopt_long... yes
checking pcl.h usability... no
checking pcl.h presence... no
checking for pcl.h... no
checking for pcre-config... /usr/bin/pcre-config
checking for pcre >= 4.5... yes (found 5.0)
checking pcre.h usability... yes
checking pcre.h presence... yes
checking for pcre.h... yes
checking for pcre_compile in -lpcre... no
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking for nl_langinfo... yes
checking for setlocale... yes
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking for iconv_t... yes
checking for iconv in -liconv... no
checking for libiconv in -liconv... no
checking for iconv... no
checking for libiconv... no
checking for latex2html... no
checking for latex... no
checking for pdflatex... no
checking for dvips... no
checking for fig2dev... no
checking postscript option... eps
checking /usr/bin/install -c --backup option...
checking for php-config... /usr/bin/php-config
checking for PHP... yes: PHP_INCS=" -I/usr/include/php
-I/usr/include/php/main -I/usr/include/php/Zend
-I/usr/include/php/TSRM"
PHP_EXTENSIONDIR="$prefix/lib/php/extensions/no-debug-non-zts-20020429"
./configure: line 27513:
lib/php/extensions/no-debug-non-zts-20020429: No such file
or directory
checking for pear... /usr/bin/pear
checking for /usr/bin/pear's php_dir...
$prefix/php_dir=/usr/lib/php
./configure: line 27611: php_dir=/usr/lib/php: No such file
or directory
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for ANSI C header files... (cached) yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for sys/wait.h that is POSIX.1 compatible... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for unistd.h... (cached) yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking malloc.h usability... no
checking malloc.h presence... no
checking for malloc.h... no
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking for dlfcn.h... (cached) yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking sys/utime.h usability... no
checking sys/utime.h presence... no
checking for sys/utime.h... no
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking rlimit.h usability... no
checking rlimit.h presence... no
checking for rlimit.h... no
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking ieeefp.h usability... no
checking ieeefp.h presence... no
checking for ieeefp.h... no
checking winsock.h usability... no
checking winsock.h presence... no
checking for winsock.h... no
checking for new... yes
checking for iostream... yes
checking for cstdio... yes
checking for pid_t... yes
checking for off_t... yes
checking for size_t... yes
checking for ptrdiff_t... yes
checking for ssize_t... yes
checking for socklen_t... yes
checking whether stat file-mode macros are broken... no
checking whether time.h and sys/time.h may both be
included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct tm.tm_zone... yes
checking whether byte ordering is bigendian... yes
checking for long long... yes
checking for __int64... no
checking for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 8
checking for void *... yes
checking size of void *... 8
checking for size_t... (cached) yes
checking size of size_t... 8
checking for ptrdiff_t... (cached) yes
checking size of ptrdiff_t... 8
checking for long long... (cached) yes
checking size of long long... 8
checking for __int64... (cached) no
checking size of __int64... 0
checking for _sys_siglist... no
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking whether setpgrp takes no argument... yes
checking return type of signal handlers... void
checking whether utime accepts a null argument... yes
checking for vprintf... yes
checking for _doprnt... no
checking for working memcmp... yes
checking for strsignal... yes
checking for mkdir... yes
checking for rmdir... yes
checking for getcwd... yes
checking for getopt... yes
checking for getrlimit... yes
checking for vsnprintf... yes
checking for snprintf... yes
checking for kill... yes
checking for pipe... yes
checking for strcspn... yes
checking for strdup... yes
checking for strstr... yes
checking for strtod... yes
checking for strtof... yes
checking for strtol... yes
checking for strerror... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for strtoll... yes
checking for strtoull... yes
checking for gethostname... yes
checking for gettimeofday... yes
checking for setenv... yes
checking for putenv... yes
checking for select... yes
checking for times... yes
checking for fstat... yes
checking for getpwuid... yes
checking for getuid... yes
checking for ftime... yes
checking for sysconf... yes
checking for fcntl... yes
checking for shutdown... yes
checking for mrand48... yes
checking for drand48... yes
checking for nanosleep... yes
checking for lockf... yes
checking for ctime_r... yes
checking for asctime_r... yes
checking for localtime_r... yes
checking for isinf... yes
checking for fpclassify... no
checking for fpclass... no
checking for getlogin... yes
checking for madvise... yes
checking for posix_madvise... yes
checking for posix_fadvise... no
checking for uname... yes
checking for opendir... yes
checking for readdir... yes
checking for rewinddir... yes
checking for closedir... yes
checking for ftruncate... yes
checking whether strdup is declared... yes
checking whether strtof is declared... yes
checking whether strtoll is declared... yes
checking whether strtoull is declared... yes
checking whether ctime_r is declared... yes
checking asctime_r3... no
checking ctime_r3... no
checking for special C compiler options needed for large
files... no
checking for _FILE_OFFSET_BITS value needed for large
files... no
checking for _LARGE_FILES value needed for large files... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating MonetDB.pc
config.status: creating MonetDB.spec
config.status: creating RunMapiClient.bat
config.status: creating RunMapprove
config.status: creating RunMapprove.bat
config.status: creating RunMserver.bat
config.status: creating RunMtest
config.status: creating RunMtest.bat
config.status: creating rpm.mk
config.status: creating sysdefs.h
config.status: creating conf/Makefile
config.status: creating conf/MonetDB.conf
config.status: creating scripts/Makefile
config.status: creating src/Makefile
config.status: creating tests/Makefile
config.status: creating scripts/tools/Makefile
config.status: creating src/common/Makefile
config.status: creating src/common/monet_options.mx
config.status: creating src/common/monet_options.py
config.status: creating src/gdk/Makefile
config.status: creating src/mapi/Makefile
config.status: creating src/mel/Makefile
config.status: creating src/modules/Makefile
config.status: creating src/monet/Makefile
config.status: creating src/testing/Makefile
config.status: creating src/testing/Mfilter.py
config.status: creating src/testing/MkillUsers
config.status: creating src/testing/Mlog
config.status: creating src/testing/Mtest.py
config.status: creating src/tools/Makefile
config.status: creating src/tools/monetdb-config.bat
config.status: creating src/tools/monetdb-config.mx
config.status: creating src/utils/Makefile
config.status: creating src/mapi/clients/Makefile
config.status: creating src/mapi/examples/Makefile
config.status: creating src/modules/calibrator/Makefile
config.status: creating src/modules/contrib/Makefile
config.status: creating src/modules/mnetcdf/Makefile
config.status: creating src/modules/plain/Makefile
config.status: creating src/utils/Mx/Makefile
config.status: creating src/utils/Mx/epstogif
config.status: creating src/utils/autogen/Makefile
config.status: creating src/mapi/clients/C/Makefile
config.status: creating src/mapi/clients/haskell/Makefile
config.status: creating src/mapi/clients/java/Makefile
config.status: creating src/mapi/clients/perl/Makefile
config.status: creating src/mapi/clients/php/Makefile
config.status: creating src/mapi/clients/python/Makefile
config.status: creating src/mapi/clients/python/MapiClient.py
config.status: creating src/mapi/clients/tcl/Makefile
config.status: creating src/mapi/examples/C/Makefile
config.status: creating src/mapi/examples/java/Makefile
config.status: creating src/mapi/clients/perl/Cimpl/Makefile
config.status: creating src/mapi/clients/perl/DBD/Makefile
config.status: creating src/mapi/clients/php/Cimpl/Makefile
config.status: creating src/mapi/clients/python/Cimpl/Makefile
config.status: creating
src/mapi/clients/perl/DBD/monetdb/Makefile
config.status: creating src/mapi/clients/php/Cimpl/DB/Makefile
config.status: creating
src/mapi/clients/php/Cimpl/examples/Makefile
config.status: creating
src/mapi/clients/php/Cimpl/examples/php.ini
config.status: creating
src/mapi/clients/python/Cimpl/MonetSQLdb/Makefile
config.status: creating monetdb_config.h
config.status: executing depfiles commands
## Comment 2968
Date: 2005-05-14 23:25:47 +0200
From: @grobian
Logged In: YES
user_id=963970
Perhaps the ouput of bootstrap is interesting as well:
% ./bootstrap
using /usr/bin/glibtool and /usr/bin/glibtoolize.
automake 1.6.3 is 1.5 or newer. Good.
autoconf 2.59 is 2.57 or newer. Good.
libtool 1.5 is 1.4 or newer. Good.
Python 2.3.5 is 2.0.0 or newer. Good.
/Volumes/Scratch/monetdb/MonetDB/src
/Volumes/Scratch/monetdb/MonetDB/src/utils
/Volumes/Scratch/monetdb/MonetDB/src/utils/Mx
/Volumes/Scratch/monetdb/MonetDB/src/utils/autogen
/Volumes/Scratch/monetdb/MonetDB/src/mel
/Volumes/Scratch/monetdb/MonetDB/src/common
/Volumes/Scratch/monetdb/MonetDB/src/gdk
/Volumes/Scratch/monetdb/MonetDB/src/monet
/Volumes/Scratch/monetdb/MonetDB/src/modules
/Volumes/Scratch/monetdb/MonetDB/src/modules/plain
/Volumes/Scratch/monetdb/MonetDB/src/modules/contrib
/Volumes/Scratch/monetdb/MonetDB/src/modules/calibrator
/Volumes/Scratch/monetdb/MonetDB/src/modules/mnetcdf
/Volumes/Scratch/monetdb/MonetDB/src/mapi
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/C
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/perl
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/perl/DBD
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/perl/DBD/monetdb
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/perl/Cimpl
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/python
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/python/Cimpl
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/python/Cimpl/MonetSQLdb
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/haskell
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/tcl
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/php
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/php/Cimpl
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/php/Cimpl/DB
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/php/Cimpl/examples
/Volumes/Scratch/monetdb/MonetDB/src/mapi/clients/java
/Volumes/Scratch/monetdb/MonetDB/src/mapi/examples
/Volumes/Scratch/monetdb/MonetDB/src/mapi/examples/C
/Volumes/Scratch/monetdb/MonetDB/src/mapi/examples/java
/Volumes/Scratch/monetdb/MonetDB/src/tools
/Volumes/Scratch/monetdb/MonetDB/src/testing
/Volumes/Scratch/monetdb/MonetDB/conf
/Volumes/Scratch/monetdb/MonetDB/scripts
/Volumes/Scratch/monetdb/MonetDB/scripts/tools
/Volumes/Scratch/monetdb/MonetDB/tests
Remember to add `AC_PROG_LIBTOOL' to `configure.in'.
You should add the contents of
`/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `conf'.
automake/aclocal 1.6.3 is older than 1.7.
Patching aclocal.m4 for Intel compiler on Linux (icc/ecc).
patching file aclocal.m4
Hunk 1 FAILED at 2542.
1 out of 1 hunk FAILED -- saving rejects to file aclocal.m4.rej
patching file aclocal.m4
Hunk 1 FAILED at 1184.
Hunk 2 FAILED at 2444.
Hunk 3 FAILED at 2464.
3 out of 3 hunks FAILED -- saving rejects to file aclocal.m4.rej
configure.in: installing `conf/install-sh'
configure.in: installing `conf/mkinstalldirs'
## Comment 2969
Date: 2005-05-14 23:45:04 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fabian,
apparently, your libpcre is not 64bit:
the configure output says:
========
[...]
checking for pcre-config... /usr/bin/pcre-config
checking for pcre >= 4.5... yes (found 5.0)
checking pcre.h usability... yes
checking pcre.h presence... yes
checking for pcre.h... yes
checking for pcre_compile in -lpcre... no
[...]
========
and config.log says:
========
[...]
configure:26189: checking for pcre_compile in -lpcre
configure:26219: gcc -m64 -o conftest -g -O2 -std=c99 -Wall
-W -I/sw/include -L/sw/lib conftest.c -lpcre -L/usr/lib
-lpcre >&5
ld64 warning: in /usr/lib/libpcre.dylib, file does not
contain requested architecture
ld64 warning: in /usr/lib/libpcre.dylib, file does not
contain requested architecture
can't resolve symbols:
_pcre_compile, referenced from:
_main in ccRRoGzU.o
ld64 failed: symbol(s) not found
collect2: ld returned 1 exit status
configure:26225: $? = 1
configure: failed program was:
[...]
========
Hence, you should not get the original pcre linking problem
anymore, do you?
Does MonetDB compile with 64bit (but then without pcre), or
are there some other bug that keep it from doing so?
Could you also send the same info for the 32bit configure run?
## Comment 2970
Date: 2005-05-15 10:06:08 +0200
From: @grobian
Logged In: YES
user_id=963970
indeed, the compilation with 64 bits died with around 6000
warnings and errors on gdk_scanselect.mx. A small excerpt
(the tail):
gdk_scanselect.mx:408: warning: value computed is not used
gdk_scanselect.mx:408: error: parse error before ')' token
gdk_scanselect.mx:409: warning: left-hand operand of comma
expression has no effect
gdk_scanselect.mx:409: warning: left-hand operand of comma
expression has no effect
gdk_scanselect.mx:409: warning: statement with no effect
gdk_scanselect.mx:412: error: parse error before "BUN"
gdk_scanselect.mx:412: warning: incompatible implicit
declaration of built-in function 'memcpy'
gdk_scanselect.mx:412: warning: incompatible implicit
declaration of built-in function 'memcpy'
gdk_scanselect.mx: At top level:
gdk_scanselect.mx:725: error: parse error before '*' token
gdk_scanselect.mx:726: error: parse error before '*' token
gdk_scanselect.mx:727: warning: return type defaults to 'int'
gdk_scanselect.mx: In function 'BAT_scanselect':
gdk_scanselect.mx:603: error: 'equi' undeclared (first use
in this function)
gdk_scanselect.mx:419: error: 'nocheck' undeclared (first
use in this function)
gdk_scanselect.mx:608: error: 'lval' undeclared (first use
in this function)
gdk_scanselect.mx:608: error: 'hval' undeclared (first use
in this function)
gdk_scanselect.mx:609: error: 'li' undeclared (first use in
this function)
gdk_scanselect.mx:609: error: 'hi' undeclared (first use in
this function)
make[4]: *** [libbat_la-gdk_scanselect.lo] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I probably have to tell my portage to compile with 64-bits,
however, I have no idea what the effects of that will be.
Because the SF forums are not that clever (especially in the
mail) I will attach an archive again with all configure
stuff and Makefiles in the build directory.
## Comment 2971
Date: 2005-05-15 11:30:32 +0200
From: @drstmane
Logged In: YES
user_id=572415
Hm, I don't really understand, what's going wrong.
Everything look fine, until libtool seem to mess things up
by translating
libtool --mode=link ... -o lib_pcre.la ... -L/usr/lib -lpcre
-lpcre
into
gcc ... -o .libs/lib_pcre.0.dylib ...-L/usr/lib
/usr/lib/libpcre ...
instead of
gcc ... -o .libs/lib_pcre.0.dylib ...-L/usr/lib -lpcre ...
Maybe, it gets confused by the double "-lpcre -lpcre"
(though it works fine on all of our testing platforms).
You could try the following patch to avoid the double
"-lpcre -lpcre":
========
--- conf/monet.m4 4 May 2005 10:33:02 -0000 1.224
+++ conf/monet.m4 15 May 2005 09:21:20 -0000
@@ -1761,7 +1761,7 @@
if test "x$have_pcre" = xyes; then
save_LIBS="$LIBS"
LIBS="$LIBS $PCRE_LIBS"
- AC_CHECK_LIB(pcre, pcre_compile,
PCRE_LIBS="$PCRE_LIBS -lpcre" have_pcre=yes, have_pcre=no)
+ AC_CHECK_LIB(pcre, pcre_compile, PCRE_LIBS="`echo
"$PCRE_LIBS" | sed 's|-lpcre||g'` -lpcre" have_pcre=yes,
have_pcre=no)
LIBS="$save_LIBS"
fi
========
## Comment 2972
Date: 2005-05-20 16:06:13 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The original bug is fixed (I assume) in rev 1.49 of decimal.mx.
How about all this other stuff that should have been a new
bug report? Is that still valid?
## Comment 2973
Date: 2005-05-21 10:07:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
Indeed, your fix seems to solve the decimal.mx + gcc-4.0.0
problems --- at least on my Fedora Core 3. Thanks, Sjoerd!
The remainder is still open --- still looking for access to
a Tiger box...
## Comment 2974
Date: 2005-05-22 17:17:19 +0200
From: @grobian
Logged In: YES
user_id=963970
I'm closing this bug because in the meanwhile I'm running
Tiger 8.1.0 and will go through the process from scratch to
see exactly where problems arise.
## Comment 2975
Date: 2005-11-09 14:38:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / COMPILATION
## Comment 2976
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1201604 at http://sourceforge.net/support/tracker.php?aid=1201604
| Compilation issue on Darwin8.0.0 (Tiger) on decimal.mx | https://api.github.com/repos/MonetDB/MonetDB/issues/540/comments | 0 | 2020-11-30T08:41:34Z | 2024-06-27T11:03:39Z | https://github.com/MonetDB/MonetDB/issues/540 | 753,276,953 | 540 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-13 12:17:46 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-07-28 03:27:33 +0200
## Comment 2952
Date: 2005-05-13 12:17:46 +0200
From: @drstmane
Yesterday, I chnaged testing for XQuery from using
pf TST.xq | Mserver --dbinit="module(pathfinder);"
to using
Mserver --dbinit="module(pathfinder); pfstart();" &
MapiClient -lxquery -sxml TST.xq
Since then, with several XQuery on Darwin & Debian and
ALL XQuery tests on SunOS, MapiClient seems to hang
until it gets killed by Mtimeout
(after 60 seconds). Before the above changes, all these
tests used to work fine (and finish well before the 60
second limit).
I haven't investigated this any further, yet; but I
cannot image, that using the server-side XQuery
compiler instead of the stand-alone 'pf" is so much
slower; hence, I suspect there is some MAPI related
problem...
## Comment 2953
Date: 2005-05-14 15:17:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
See
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/index_short.html
for details.
## Comment 2954
Date: 2005-07-21 17:12:11 +0200
From: @Teggy
Logged In: YES
user_id=642632
I still see this hanging of MapiClient on Darwin 8.2.0
(MacOS X 10.4.2). While piping the output of pf into
Mserver works just fine -- as does the invocation of the
server-side compiler via the MIL xquery(str,str) command --
communication via MapiClient hangs.
More specifically, MapiClient hangs in the read() system
call in function socket_read() (common/stream.mx).
Interestingly, hitting ENTER in the Mserver console seems to
"cure" the problem: read() returns and the whole Mapi
conversation between client and server continues to run just
fine until the expected query result has been printed by
MapiClient.
I regard this as a show stopper if it indeed affects Solaris
and some Debian systems, too, as reported above.
## Comment 2955
Date: 2005-07-21 19:21:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
So far, Darwin/MacOS X was not a major platform for
Pathfinder, since there were no Pathfinder users working on
Apples, but that seems to have changed ... ;-)
Anyway, at least you seems to be able to get Pathfinder
compiled on Darwin 8.2.0 / MacOS X 10.4.2 --- on our testing
machine (a G4, hence "only" 32bit), I get the following
error which I haven't been able to fix, yet:
========
-monet@monet::~/Monet/pathfinder> gcc --version
powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 20041026 (Apple
Computer, Inc. build 4061)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying
conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
--------
monet@monet::~/Monet/pathfinder> uname -a
Darwin monet.cs.umass.edu 8.2.0 Darwin Kernel Version 8.2.0:
Fri Jun 24 17:46:54 PDT 2005;
root:xnu-792.2.4.obj~3/RELEASE_PPC Power Macintosh powerpc
========
/bin/sh ../libtool --mode=link gcc -m32 -std=c99 -Wall -W
-g -Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -Wno-uninitialized
-o lib_pathfinder.la -rpath
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB
lib_pathfinder_la-pathfinder.glue.lo
lib_pathfinder_la-pathfinder.lo ../compiler/libcompiler1.la
../compiler/schema/libschema.la
../compiler/debug/libdebug.la ../compiler/mem/libmem.la
../compiler/parser/libparser.la
../compiler/semantics/libsemantics.la
../compiler/core/libcore.la
../compiler/algebra/libalgebra.la ../compiler/mil/libmil.la
../compiler/algebra/hskparser/libhskparser.la
../compiler/libcompiler2.la -lxml2 -L/usr/lib -lxml2 -lz
-lpthread -liconv -lm -ldl
-L/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib
-L/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB
-lbat -lmonet -lstream -l_streams -l_builtin -l_ascii_io
-l_algebra lib_pf_support.la -l_monettime -l_lock -l_streams
gcc -m32 -dynamiclib -flat_namespace -undefined suppress -o
.libs/lib_pathfinder.0.dylib
.libs/lib_pathfinder_la-pathfinder.glue.o
.libs/lib_pathfinder_la-pathfinder.o -all_load
../compiler/.libs/libcompiler1.a
../compiler/schema/.libs/libschema.a
../compiler/debug/.libs/libdebug.a
../compiler/mem/.libs/libmem.a
../compiler/parser/.libs/libparser.a
../compiler/semantics/.libs/libsemantics.a
../compiler/core/.libs/libcore.a
../compiler/algebra/.libs/libalgebra.a
../compiler/mil/.libs/libmil.a
../compiler/algebra/hskparser/.libs/libhskparser.a
../compiler/.libs/libcompiler2.a /usr/lib/libdl.dylib
/usr/lib/libbz2.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/libmutils.0.0.0.dylib
/usr/lib/libm.dylib /usr/lib/libz.dylib
/usr/lib/libpthread.dylib -L/usr/lib /usr/lib/libxml2.dylib
-lz -lpthread /usr/lib/libiconv.dylib -lm -ldl
-L/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib
-L/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/libbat.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/libmonet.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/libstream.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_builtin.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_ascii_io.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_algebra.0.0.0.dylib
./.libs/lib_pf_support.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_monettime.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_lock.0.0.0.dylib
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_streams.0.0.0.dylib
-m32 -install_name
/Users/monet/Monet/_PREFIX_GNU_32_d_--enable-debug_/lib/MonetDB/lib_pathfinder.0.dylib
-compatibility_version 1 -current_version 1.0
ld: multiple definitions of symbol __Unwind_DeleteException
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_DeleteException in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_DeleteException in
section (__TEXT,__text)
ld: multiple definitions of symbol
__Unwind_FindEnclosingFunction
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_FindEnclosingFunction in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of
__Unwind_FindEnclosingFunction in section (__TEXT,__text)
ld: multiple definitions of symbol __Unwind_ForcedUnwind
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_ForcedUnwind in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_ForcedUnwind in
section (__TEXT,__text)
ld: multiple definitions of symbol __Unwind_GetDataRelBase
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_GetDataRelBase in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_GetDataRelBase in
section (__TEXT,__text)
ld: multiple definitions of symbol __Unwind_GetGR
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_GetGR in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_GetGR in section
(__TEXT,__text)
ld: multiple definitions of symbol __Unwind_GetIP
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_GetIP in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_GetIP in section
(__TEXT,__text)
ld: multiple definitions of symbol
__Unwind_GetLanguageSpecificData
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_GetLanguageSpecificData in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of
__Unwind_GetLanguageSpecificData in section
(__TEXT,__text)ld: multiple definitions of symbol
__Unwind_GetRegionStart
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_GetRegionStart in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_GetRegionStart in
section (__TEXT,__text)
ld: multiple definitions of symbol __Unwind_GetTextRelBase
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_GetTextRelBase in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_GetTextRelBase in
section (__TEXT,__text)
ld: multiple definitions of symbol __Unwind_RaiseException
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_RaiseException in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_RaiseException in
section (__TEXT,__text)
ld: multiple definitions of symbol __Unwind_Resume
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_Resume in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_Resume in section
(__TEXT,__text)
ld: multiple definitions of symbol __Unwind_SetGR
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_SetGR in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_SetGR in section
(__TEXT,__text)
ld: multiple definitions of symbol __Unwind_SetIP
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of __Unwind_SetIP in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of __Unwind_SetIP in section
(__TEXT,__text)
ld: multiple definitions of symbol ___frame_state_for
/usr/lib/libgcc.a(unwind-dw2.o) private external definition
of ___frame_state_for in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2.o)
private external definition of ___frame_state_for in section
(__TEXT,__text)
ld: multiple definitions of symbol __Unwind_Find_FDE
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of __Unwind_Find_FDE in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of __Unwind_Find_FDE in section
(__TEXT,__text)
ld: multiple definitions of symbol ___deregister_frame
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___deregister_frame in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___deregister_frame in
section (__TEXT,__text)
ld: multiple definitions of symbol ___deregister_frame_info
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___deregister_frame_info in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___deregister_frame_info in
section (__TEXT,__text)
ld: multiple definitions of symbol
___deregister_frame_info_bases
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___deregister_frame_info_bases in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of
___deregister_frame_info_bases in section (__TEXT,__text)
ld: multiple definitions of symbol ___register_frame
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___register_frame in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___register_frame in section
(__TEXT,__text)
ld: multiple definitions of symbol ___register_frame_info
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___register_frame_info in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___register_frame_info in
section (__TEXT,__text)
ld: multiple definitions of symbol ___register_frame_info_bases
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___register_frame_info_bases in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___register_frame_info_bases
in section (__TEXT,__text)
ld: multiple definitions of symbol ___register_frame_info_table
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___register_frame_info_table in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___register_frame_info_table
in section (__TEXT,__text)
ld: multiple definitions of symbol
___register_frame_info_table_bases
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___register_frame_info_table_bases in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of
___register_frame_info_table_bases in section (__TEXT,__text)
ld: multiple definitions of symbol ___register_frame_table
/usr/lib/libgcc.a(unwind-dw2-fde-darwin.o) private external
definition of ___register_frame_table in section (__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/libgcc_eh.a(unwind-dw2-fde-darwin.o)
private external definition of ___register_frame_table in
section (__TEXT,__text)
/usr/bin/libtool: internal link edit command failed
make[3]: *** [lib_pathfinder.la] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
========
Did you see similar problems and/or which compiler (version)
are you using?
## Comment 2956
Date: 2005-07-22 11:23:34 +0200
From: @Teggy
Logged In: YES
user_id=642632
Hi Stefan,
I did not see any particular problem during the MonetDB
and Pathfinder install. Everything went quite smoothly.
Starting with MacOS X 10.4., even dlopen() functionality is
built into the system, making the dlcompat library obsolete.
Here comes the configuration/version information (which
matches yours perfectly):
$ /Users/grust/sci/XQuery/pf/configure
--prefix=/Users/grust/sci/XQuery/Pathfinder --enable-debug
---------------------------------------------
$ uname -a
Darwin mackemper1.informatik.tu-muenchen.de 8.2.0 Darwin
Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005;
root:xnu-792.2.4.obj~3/RELEASE_PPC Power Macintosh powerpc
---------------------------------------------
$ gcc --version
powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 20041026 (Apple
Computer, Inc. build 4061)
Note: this is with MonetDB 4.8.0 and Pathfinder 0.8.0.
Greetings,
--Teggy
## Comment 2957
Date: 2005-07-22 11:32:23 +0200
From: @Teggy
Logged In: YES
user_id=642632
I just saw comment (found via Google) that other project are
struggling with the same compilation problems, too.
Possible suggested fixes:
- Upgrade to Xcode Tools 2.1 (gcc 4.0 build 5026 does not
seem to have the problem).
- Compile with gcc 3.3. To select gcc 3.3:
$ gcc_select 3.3
Does this help?
--Teggy
## Comment 2958
Date: 2005-07-22 12:47:12 +0200
From: @grobian
Logged In: YES
user_id=963970
I was just about to mention the Xcode 2.1 update...
I don't think we want to compile gcc3.3 on OSX, as it
doesn't support 64-bits.
## Comment 2959
Date: 2005-07-28 15:18:38 +0200
From: @grobian
Logged In: YES
user_id=963970
with the latest fix in CVS for scanner.1 this problem is
solved for Darwin 8.2.0 using bison-2.0
## Comment 2960
Date: 2005-07-28 15:27:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed in CVS:
In case yyin/pfin is not set, initialize it to /dev/null
(Unix) resp. C:nul
(Windows); otherwise it gets initialized to stdin, which
might conflict with
Mserver'\''s console:
The lexer eventually calls fileno() for yyin/pfin, which in
case of
yyin/pfin=stdin might be blocked as there is a waiting
select/read on the
console(=stdin)...
## Comment 2961
Date: 2005-11-09 15:28:51 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
All mapi xquery tests will test this bug
## Comment 2962
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1201291 at http://sourceforge.net/support/tracker.php?aid=1201291
| XQuery: MapiClient -lxquery hangs on Darwin, Debian & SunOS | https://api.github.com/repos/MonetDB/MonetDB/issues/539/comments | 0 | 2020-11-30T08:41:31Z | 2024-06-27T11:03:38Z | https://github.com/MonetDB/MonetDB/issues/539 | 753,276,909 | 539 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-12 03:09:03 +0200
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2005-05-13 10:33:27 +0200
## Comment 2948
Date: 2005-05-12 15:09:03 +0200
From: @swingbit
a is a bat sorted on head:
MonetDB>var a:=new(int,int).insert(1,0).insert(2,0).sort();
MonetDB>a.info().find("hsorted").print();
[ "65" ]
b is a bat sorted on tail:
MonetDB>var b:=a.reverse();
MonetDB>b.info().find("tsorted").print();
[ "65" ]
MonetDB>var c:=[+](b,1);
MonetDB>c.info().find("tsorted").print();
[ "0" ]
The addition of a constant shouldn't change the sort
property though.....
The tail of c should still be ordered!
## Comment 2949
Date: 2005-05-13 10:33:27 +0200
From: @njnes
Logged In: YES
user_id=43556
For bat_arith this is now fixed. The default 'map' operator
needs lots of work to get this fixed. So closing this bug
with a won't fix (its optimization only anyway).
## Comment 2950
Date: 2005-11-09 15:35:31 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / won't fix
## Comment 2951
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1200626 at http://sourceforge.net/support/tracker.php?aid=1200626
| sort information lost | https://api.github.com/repos/MonetDB/MonetDB/issues/538/comments | 0 | 2020-11-30T08:41:28Z | 2024-06-28T07:36:37Z | https://github.com/MonetDB/MonetDB/issues/538 | 753,276,878 | 538 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-12 09:51:37 +0200
From: Jan Rittinger <<jan.rittinger>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-11-09 03:43:51 +0100
## Comment 2943
Date: 2005-05-12 09:51:37 +0200
From: Jan Rittinger <<jan.rittinger>>
The proc 'delete_doc' in pathfinder.mx hangs during the
commit() statement in line 1224 (since version 1.57).
If I kill and restart the Mserver the commit seems to be
executed.
## Comment 2944
Date: 2005-11-09 15:09:54 +0100
From: @njnes
Logged In: YES
user_id=43556
could you please supply a test script
## Comment 2945
Date: 2005-11-09 15:43:51 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
There is already a test script (see BugsViaSourceforge)
## Comment 2946
Date: 2005-12-21 11:30:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay: stmane: ALREADY IN TESTWEB:
./tests/BugsViaSourgeforce/Tests/ID.1200405.milS
## Comment 2947
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1200405 at http://sourceforge.net/support/tracker.php?aid=1200405
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 hangs during commit (in pf) | https://api.github.com/repos/MonetDB/MonetDB/issues/537/comments | 0 | 2020-11-30T08:41:25Z | 2024-06-27T11:03:36Z | https://github.com/MonetDB/MonetDB/issues/537 | 753,276,850 | 537 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-11 01:32:02 +0200
From: Jens Teubner <<teubner>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-11-18 09:45:49 +0100
## Comment 2937
Date: 2005-05-11 13:32:02 +0200
From: Jens Teubner <<teubner>>
According to Jan R, MonetDB's implementation for tunique
appeared to be rather slow for string tails on large documents. He
circumvented this by introducing his own tuniqueALT that imitates
tunique by the (faster) unique insert into an empty BAT. For Jan, this
brought a 30sec performance boost for some queries (particularly
on large documents).
Though the MIL implementation in pf_support appears to work rather
well, this is probably something that should go into tunique() itself.
I don't know if this has happened in the meantime (if yes, we should
``fix'' pf). So think of this bug report as a reminder to bring up the
topic again.
## Comment 2938
Date: 2005-05-23 20:04:53 +0200
From: @njnes
Logged In: YES
user_id=43556
Any example documents, which prove this performance increase?
## Comment 2939
Date: 2005-06-07 23:31:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Could someone supply me a simple test (one of the Xquery
test scripts for example) which I could use to test the
performance improvement of the special tunique implementation.
## Comment 2940
Date: 2005-11-18 09:45:48 +0100
From: @peterboncz
Logged In: YES
user_id=591107
a fix in BATkunique (better setting the hash table size)
made the default kunique and tunique fast enough.
BTW the same problem happened for non-string values. Maybe
some PF queries now run faster!
## Comment 2941
Date: 2005-12-21 11:31:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay: stmane: NO TEST / CODING
## Comment 2942
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1199766 at http://sourceforge.net/support/tracker.php?aid=1199766
| tuniqueALT | https://api.github.com/repos/MonetDB/MonetDB/issues/536/comments | 0 | 2020-11-30T08:41:22Z | 2024-06-28T07:36:37Z | https://github.com/MonetDB/MonetDB/issues/536 | 753,276,810 | 536 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-11 10:15:30 +0200
From: @sjoerdmullender
To: @mlkersten
Version: -- development
Last updated: 2005-05-12 09:56:09 +0200
## Comment 2932
Date: 2005-05-11 10:15:30 +0200
From: @sjoerdmullender
Some tests, e.g. src/gdk/str_heap, cause a crash which
is due to a double free. I have been able to get stack
traces of the locations of the first and second free of
the same location when running the str_heap test.
The first:
0 GDKfree (blk=0x811ecf8) at gdk_utils.mx:1093
1 0xb7dcb2f4 in BATfree (b=0x8159f80) at gdk_bat.mx:484
2 0xb7d8ffd8 in BBPfree (b=0x811ecf8,
calledFrom=0xb7e28e50 "BBPdecref")
at gdk_bbp.mx:1695
3 0xb7d8e2c1 in decref (i=27, logical=0, lock=1) at
gdk_bbp.mx:1308
4 0xb7d8db1d in BBPdecref (i=27, logical=0) at
gdk_bbp.mx:1326
5 0xb7f18f0a in CMDunload (res=0x817f638 "",
input=0x80f7e30 "DRUID_sample")
at bat.mx:1434
6 0xb7f14cdf in CMDunload_unpack1505939241 (argc=2,
argv=0x817f638)
at bat.glue.c:1886
7 0xb7f83cff in interpret (stk=1, lt=0x818b358,
res=0xbffff310)
at monet_interpreter.mx:1148
8 0xb7f8ac58 in interpret_seqblock (stk=1,
lt=0x80b9c98, res=0xbffff310,
scope=0) at monet_interpreter.mx:1769
9 0xb7f82552 in interpret (stk=1, lt=0x80b9c98,
res=0xbffff310)
at monet_interpreter.mx:756
10 0xb7f80eb7 in interpret_str (stk=0,
buf=0x8185358
"new(int,str).persists(true).rename(\"DRUID_sample\");\n\nbat(\"DRUID_sample\").insert(1,str(\"Medicina
e salute Malattie , Medicina , Terapie ... Risorse
Biblioteche , Dizionari ... Scienza e tecnologia Arch"...,
res=0xbffff310) at monet_interpreter.mx:246
11 0xb7f8129c in interpret_file (stk=0, lt=0x80b3630,
res=0xbffff310)
at monet_interpreter.mx:291
12 0xb7f82d17 in interpret (stk=0, lt=0x80b3630,
res=0xbffff310)
at monet_interpreter.mx:846
13 0xb7f9bba2 in handleRequest (t=0xb7ed4900,
q=0x80607d8, res=0xbffff310)
at monet_queue.mx:534
14 0xb7f9bf9f in doRequest (t=0xb7ed4900, preference=0x0)
at monet_queue.mx:560
15 0xb7fe3972 in monetInterpreter (status=0xbffff38c)
at monet_process.mx:112
16 0x08049e6b in main (argc=2, av=0xbffff434) at
Mserver.mx:441
And the second:
0 GDKfree (blk=0x811ecf8) at gdk_utils.mx:1093
1 0xb7dcb418 in BATdestroy (b=0x811ecf8) at
gdk_bat.mx:501
2 0xb7d8c66d in BBPuncacheit_ (i=27, unloaddesc=1) at
gdk_bbp.mx:1048
3 0xb7d8fd00 in BBPdestroy (b=0x811ecf8) at
gdk_bbp.mx:1670
4 0xb7d8e254 in decref (i=27, logical=0, lock=1) at
gdk_bbp.mx:1305
5 0xb7d8db1d in BBPdecref (i=27, logical=0) at
gdk_bbp.mx:1326
6 0xb7f9ddad in Myyclean (t=0x8189e50) at yytree.mx:692
7 0xb7f8acf2 in interpret_seqblock (stk=1,
lt=0x80b9c98, res=0xbffff310,
scope=0) at monet_interpreter.mx:1770
8 0xb7f82552 in interpret (stk=1, lt=0x80b9c98,
res=0xbffff310)
at monet_interpreter.mx:756
9 0xb7f80eb7 in interpret_str (stk=0,
buf=0x8185358
"new(int,str).persists(true).rename(\"DRUID_sample\");\n\nbat(\"DRUID_sample\").insert(1,str(\"Medicina
e salute Malattie , Medicina , Terapie ... Risorse
Biblioteche , Dizionari ... Scienza e tecnologia Arch"...,
res=0xbffff310) at monet_interpreter.mx:246
10 0xb7f8129c in interpret_file (stk=0, lt=0x80b3630,
res=0xbffff310)
at monet_interpreter.mx:291
11 0xb7f82d17 in interpret (stk=0, lt=0x80b3630,
res=0xbffff310)
at monet_interpreter.mx:846
12 0xb7f9bba2 in handleRequest (t=0xb7ed4900,
q=0x80607d8, res=0xbffff310)
at monet_queue.mx:534
13 0xb7f9bf9f in doRequest (t=0xb7ed4900, preference=0x0)
at monet_queue.mx:560
14 0xb7fe3972 in monetInterpreter (status=0xbffff38c)
at monet_process.mx:112
15 0x08049e6b in main (argc=2, av=0xbffff434) at
Mserver.mx:441
## Comment 2933
Date: 2005-05-11 11:12:19 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Martin's "textual changes" probably caused this. The first
stack trace shows that a free is done on a BATmirror(b), but
the pointer is identical to the pointer that is later given
to BATdestroy.
I had added printfs to see which pointers were given back by
GDKmalloc and GDKrealloc, and which pointers were given to
GDKfree and GDKrealloc. The pointer was not returned by
either of the latter two functions in the time between the
two backtraces.
## Comment 2934
Date: 2005-05-12 09:56:09 +0200
From: @njnes
Logged In: YES
user_id=43556
A BATreset was incorrectly replaced with the implementation
of BATreverse.
## Comment 2935
Date: 2005-11-09 15:04:58 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
this bug report was reported because of red crosses in the
test web..
## Comment 2936
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1199649 at http://sourceforge.net/support/tracker.php?aid=1199649
| duoble free causes crash | https://api.github.com/repos/MonetDB/MonetDB/issues/535/comments | 0 | 2020-11-30T08:41:18Z | 2024-06-27T11:03:34Z | https://github.com/MonetDB/MonetDB/issues/535 | 753,276,783 | 535 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-10 04:46:04 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-05-10 05:52:27 +0200
## Comment 2928
Date: 2005-05-10 16:46:04 +0200
From: Wouter Alink <<alink>>
variables not mapped to all scopes in for-loops.
the example below results in an empty result ($name
becomes empty, while it should not):
declare function b($name as xs:string) as node()*
{ if ($name) then text{$name} else ()};
declare function a($name as xs:string) as node()*
{ for $a in (1,2,3)
for $s in b($name) return
$s
};
a(text{"bar"},'file')
## Comment 2929
Date: 2005-05-10 16:54:20 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
example is incorrect; should be:
declare function b($name as xs:string) as node()*
{ if ($name) then text{$name} else ()};
declare function a($name as xs:string) as node()*
{ for $a in (1,2,3)
for $s in b($name) return
$s
};
a('file')
## Comment 2930
Date: 2005-11-09 14:51:21 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: TEST ADDED / SUCCESS
pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/variables_scoping.SF-1199082.xq
## Comment 2931
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1199082 at http://sourceforge.net/support/tracker.php?aid=1199082
| XQuery: variables not mapped to all scopes | https://api.github.com/repos/MonetDB/MonetDB/issues/534/comments | 0 | 2020-11-30T08:41:14Z | 2024-06-27T11:03:33Z | https://github.com/MonetDB/MonetDB/issues/534 | 753,276,748 | 534 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-10 10:29:11 +0200
From: rimluga <<rimluga>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-05-10 11:35:59 +0200
## Comment 2924
Date: 2005-05-10 10:29:11 +0200
From: rimluga <<rimluga>>
Hi,
Is monetdb a main memory dbms?
I thought that the dbms storage is not persistent, and it's by default
persistent
or is it main memory just for DML statements (the db is in cache)
Best,
rim
## Comment 2925
Date: 2005-05-10 11:35:59 +0200
From: @drstmane
Logged In: YES
user_id=572415
MonetDB is a main-memory DBMS kernel in the sense that its
operators are optimized for in-memory processing.
Nevertheless, data (i.e., tables or BATs) can be stored
persistently on disk. This is the default if you use the SQL
interface. In MIL, BATs are by default transient; to make a
BAT B persistent you need to call `persists(B,TRUE);' (see
also `help("persists");' in MIL).
For more information please see http://monetdb.cwi.nl/ or
feel free to contact us via
mailto:monetdb-users@lists.sourceforge.net (or
mailto:monet@cwi.nl).
[PS: This is actually not a BUG report, but a user question
which should been posted to the MonetDB users mailing list
monetdb-users@lists.sourceforge.net (cf.
http://lists.sourceforge.net/lists/listinfo/monetdb-users)
instead of being filed as a BUG report.]
## Comment 2926
Date: 2005-11-09 14:31:35 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST
## Comment 2927
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1198860 at http://sourceforge.net/support/tracker.php?aid=1198860
| main memory db | https://api.github.com/repos/MonetDB/MonetDB/issues/533/comments | 0 | 2020-11-30T08:41:13Z | 2024-06-28T07:36:37Z | https://github.com/MonetDB/MonetDB/issues/533 | 753,276,726 | 533 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-09 08:37:27 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-11-25 12:21:19 +0100
## Comment 2918
Date: 2005-05-09 20:37:27 +0200
From: Wouter Alink <<alink>>
Pathfinder currently does not allow dashes in user
defined functions.
Example: the following XQuery results in errors
declare function dash-dash() as xs:string { 'should
work' };
dash-dash()
The error message is:
!ERROR: "v_vid000 := v_vid000.access(BAT_WRITE);"
! ^
! can't help you here, sorry.
!ERROR: interpret: unknown variable 'dash'.
!ERROR: interpret_params: -(param 1): evaluation error.
!WARNING: BBPdecref: range error -208
!ERROR: "drop("pathfinder");"
! ^
! can't help you here, sorry.
From the XQuery specification i found:
FunctionDecl ::="declare" "function" QName "(" .........
QName ::= (Prefix ':')? LocalPart
LocalPart ::= NCName
NCName ::= (Letter | '_') (NCNameChar)*
NCNameChar ::= Letter | Digit | '.' | '-' | '_' |
CombiningChar | Extender
So my guess is that pathfinder is not functioning
correctly... ;)
## Comment 2919
Date: 2005-05-10 11:46:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Well, apparently Pathfinder (i.e., the XQuery compiler) is
functioning correctly in that sense, that is does parse and
compile the query without issuing an error
(cf. `echo -e "declare function dash-dash() as xs:string {
'should work' };\ndash-dash()" | pf').
However, user defined functions are translated into MIL
PROCs, using hte same name as given in XQuery, and
(obviously) MIL does not allow identifies that contain '.'
or '-' ...
A fix would be to have the compiler (or at least the MIL
generator) check for these characters and replace them by
'_' --- hoping that noone defines two functions "x-y" and
"x_y" ...
Jan(R), could you please have a look?
## Comment 2920
Date: 2005-05-10 18:24:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
On behalve of JanR:
Fixed in CVS:
for user defined functions, do not use the original XQuery
function name
in/as the name for the respective MIL PROC, since the former
might contain
'.' and/or '-' which are not allowed in MIL identifiers.
## Comment 2921
Date: 2005-11-09 14:30:26 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: TEST ADDED / FAILURE
pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/dashes_in_functions.SF-1198495.xq
Bug reopened.
## Comment 2922
Date: 2005-11-25 00:21:19 +0100
From: @peterboncz
Logged In: YES
user_id=591107
should work now
## Comment 2923
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1198495 at http://sourceforge.net/support/tracker.php?aid=1198495
| '-' in User Defined Function names | https://api.github.com/repos/MonetDB/MonetDB/issues/532/comments | 0 | 2020-11-30T08:41:10Z | 2024-06-27T11:03:31Z | https://github.com/MonetDB/MonetDB/issues/532 | 753,276,700 | 532 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-09 02:22:41 +0200
From: rimluga <<rimluga>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2005-05-09 02:49:45 +0200
## Comment 2909
Date: 2005-05-09 14:22:41 +0200
From: rimluga <<rimluga>>
Hi,
Am trying to run TPC-W against monetdb,
the execution of the following code
try {
PreparedStatement statement = con.prepareStatement
("CREATE TABLE address ( addr_id int not null,
addr_street1 varchar(40), addr_street2 varchar(40), addr_city
varchar(30), addr_state varchar(20), addr_zip varchar(10),
addr_co_id int, PRIMARY KEY(addr_id))");
statement.executeUpdate();
con.commit();
System.out.println("Created table ADDRESS");
} catch (java.lang.Exception ex) {
System.out.println("Unable to create table: ADDRESS");
ex.printStackTrace();
System.exit(1);
}
generates the following error,
is the DDL staement should be re-written or it's another error
[java] Unable to create table: ADDRESS
[java] java.sql.SQLException: current transaction is aborted
(please ROLLBACK)
[java] at
nl.cwi.monetdb.jdbc.MonetConnection$HeaderList.getNextHeader(U
nknown Source)
[java] at
nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(Unknown
Source)
[java] at
nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(Unknown
Source)
[java] at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(Unknown
Source)
[java] at
nl.cwi.monetdb.jdbc.MonetStatement.execute(Unknown Source)
[java] at
nl.cwi.monetdb.jdbc.MonetPreparedStatement.execute(Unknown
Source)
[java] at
nl.cwi.monetdb.jdbc.MonetPreparedStatement.executeUpdate(Unkn
own Source)
[java] at TPCW_Populate.createTables(Unknown Source)
[java] at TPCW_Populate.main(Unknown Source)
Best
## Comment 2910
Date: 2005-05-09 14:31:50 +0200
From: @grobian
Logged In: YES
user_id=963970
Hi,
Apparently you disabled auto-commit mode and did a previous
query fail, hence the message "current transaction is
aborted (please ROLLBACK)". Can you easily check which
queries are run before this query? If not you should enable
a debug log to find out.
## Comment 2911
Date: 2005-05-09 14:45:15 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Hi,
thanx,
the syntax is OK I succeed to create the table from the monet
interactive jdbc terminal,
in tpc-w populate, the queries before are dropping tables if they exist,
try {
//Delete each table listed in the tables array
PreparedStatement statement = con.prepareStatement
("DROP TABLE " + tables[i]);
statement.executeUpdate();
con.commit();
System.out.println("Dropped table " + tables[i]);
} catch (java.lang.Exception ex) {
System.out.println("Already dropped table " + tables[i]);
}
since the tables do not exist I've the message "already dropped table" with
no exeptions raised,
but before executing anything, this code is executed in the tpc-w
should I change the false with true?
private static void getConnection(){
try {
Class.forName(driverName);
//dbName
con = DriverManager.getConnection("jdbc:monetdb://localhost/
database?debug=true","monetdb","monetdb");
con.setAutoCommit(false);
}
catch (java.lang.Exception ex) {
ex.printStackTrace();
}
}
every DDL is followed by
statement.executeUpdate();
con.commit();
Best, rim
## Comment 2912
Date: 2005-05-09 14:49:37 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Fabian,
how to enable a debug log? in this way
con = DriverManager.getConnection("jdbc:monetdb://localhost/database?
debug=true","monetdb","monetdb");
where can I find this log?
Best,
## Comment 2913
Date: 2005-05-09 14:49:45 +0200
From: @grobian
Logged In: YES
user_id=963970
You don't have to try the debug thing, because I think I
found the source to your problem.
The delete will indeed fail, because the table does not
exist. This *does* however break your transaction. Your
commit should indeed solve this, but this point is never
reached, because the exception is thrown at the
executeUpdate() statement. It would be better to place the
commit in the catch block, but maybe you should consider
putting it in the finally block, as I think that matches
best your original intentions of this code.
## Comment 2914
Date: 2005-05-09 14:52:40 +0200
From: @grobian
Logged In: YES
user_id=963970
your code to enable the debug log is ok. You will find the
log where Java has its current local path. If you want to
specify where the log file should go, use a connection
string such as:
con =
DriverManager.getConnection("jdbc:monetdb://localhost/datab
ase?debug=true&logfile=path/to/my/file","monetdb","monetdb");
## Comment 2915
Date: 2005-05-09 17:57:20 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Hi Fabian,
it's fine,
after thinking, the 1st execution will be a problem, the next one's no, I've
just putted into comments dropping tables.
am now with tpc-w interactions,
thank you for your help
best,
## Comment 2916
Date: 2005-11-09 14:20:13 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST
## Comment 2917
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1198238 at http://sourceforge.net/support/tracker.php?aid=1198238
| error of execution | https://api.github.com/repos/MonetDB/MonetDB/issues/531/comments | 0 | 2020-11-30T08:41:08Z | 2024-06-28T13:35:20Z | https://github.com/MonetDB/MonetDB/issues/531 | 753,276,670 | 531 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-05 10:49:54 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-05 11:26:42 +0200
## Comment 2905
Date: 2005-05-05 10:49:54 +0200
From: @drstmane
From
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.ntv_64-d/Fedora3/make.out:
========
[...]
icpc -no-gcc -DHAVE_CONFIG_H -I.
-I/tmp/monet.ntv_64-d.22780/MonetDB/src/mel -I../..
-I/tmp/monet.ntv_64-d.22780/MonetDB/src/mel -we140
-wd1418 -c99 -Wall -w2 -c -o mel.yy.o mel.yy.cc
[...]
/usr/include/c++/3.4.3/bits/postypes.h(72): error:
identifier "int64_t" is undefined
typedef int64_t streamoff;
^
[...]
compilation aborted for mel.yy.cc (code 2)
make[4]: *** [mel.yy.o] Error 2
make[4]: Leaving directory
`/tmp/monet.ntv_64-d.22780/MonetDB/Fedora3/src/mel'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/tmp/monet.ntv_64-d.22780/MonetDB/Fedora3/src/mel'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/tmp/monet.ntv_64-d.22780/MonetDB/Fedora3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/tmp/monet.ntv_64-d.22780/MonetDB/Fedora3'
make: *** [all] Error 2
========
## Comment 2906
Date: 2005-05-05 11:26:42 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed /usr/include/features.h. This file doesn't handle the
x86_64 case for the
intel compiler jet. Lets hope the next release of glibc
includes the fix.
## Comment 2907
Date: 2005-11-09 14:14:42 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST / COMPILATION
## Comment 2908
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1195753 at http://sourceforge.net/support/tracker.php?aid=1195753
| mel fails to compile with icc 8.1 on Fedora Core 3 / 64 bit | https://api.github.com/repos/MonetDB/MonetDB/issues/530/comments | 0 | 2020-11-30T08:41:05Z | 2024-06-27T11:03:29Z | https://github.com/MonetDB/MonetDB/issues/530 | 753,276,649 | 530 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-03 12:45:38 +0200
From: @sjoerdmullender
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-05-04 09:47:37 +0200
## Comment 2901
Date: 2005-05-03 12:45:38 +0200
From: @sjoerdmullender
pf-shred uses fseek. It calculates the position to
seek to and then writes data to the file. This is an
incorrect (and, as it happens, unportable) way of using
fseek. According to the C99 standard:
"For a text stream, either offset shall be zero, or
offset shall be a value returned by an earlier
successful call to the ftell function on a stream
associated with the same file and whence shall be
SEEK_SET."
Potential solutions:
- get rid of pf-shred;
- fix the use of fseek.
I think that the second option will be hard, and I
understand that pf-shred is not useful anymore (except
perhaps for the Haskell support?).
## Comment 2902
Date: 2005-05-04 09:47:37 +0200
From: @njnes
Logged In: YES
user_id=43556
The loader was simply dropped to a different repository, as
its not needed for the current pathfinder code.
## Comment 2903
Date: 2005-11-09 14:14:15 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST / OBSOLETE
pf-shred was removed from the repository.
## Comment 2904
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1194362 at http://sourceforge.net/support/tracker.php?aid=1194362
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-shred uses fseek incorrectly | https://api.github.com/repos/MonetDB/MonetDB/issues/529/comments | 0 | 2020-11-30T08:41:02Z | 2024-06-28T13:35:19Z | https://github.com/MonetDB/MonetDB/issues/529 | 753,276,617 | 529 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-03 10:57:35 +0200
From: @njnes
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-05-16 09:45:03 +0200
## Comment 2897
Date: 2005-05-03 10:57:35 +0200
From: @njnes
As can be seen from tst_updatestr* there is a bug in
updating mmapped bats. Somehow the updates are made
persistent allthough no commits are done. The reason
seems to be in the fact that X.priv files aren't kept.
Once an X file exists its moved over the X.priv and
then used. By moving the old persistent information is
lost.
## Comment 2898
Date: 2005-05-16 21:45:03 +0200
From: @peterboncz
Logged In: YES
user_id=591107
yesterdays commits in gdk (whiahc also introduce the new
partial commit feature) fix this bug.
## Comment 2899
Date: 2005-11-09 14:12:52 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: ALREADY IN TESTWEB
MonetDB/tests/by_Peter/Tests/tst_updatestr.milM
## Comment 2900
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1194299 at http://sourceforge.net/support/tracker.php?aid=1194299
| .priv file and STORE_PRIV | https://api.github.com/repos/MonetDB/MonetDB/issues/528/comments | 0 | 2020-11-30T08:41:00Z | 2024-06-28T13:35:18Z | https://github.com/MonetDB/MonetDB/issues/528 | 753,276,592 | 528 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-05-02 02:37:42 +0200
From: Jens Teubner <<teubner>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-05-23 10:40:55 +0200
## Comment 2892
Date: 2005-05-02 14:37:42 +0200
From: Jens Teubner <<teubner>>
The HowToStart-PF document currently states that MapiClient will
read XQuery expressions from stdin if no file is given on the
command line.
MapiClient, however, only reads files given on the command line. If
no file is given, no file is read and MapiClient directly exits.
We should either fix MapiClient for this respect, or update the
documentation accordingly. (I'm currently writing an online
documentation.) In the latter case, however, we should make the
filename a required argument and print an error message if it is
omitted.
I can force MapiClient to read queries from stdin by using the
filename /dev/stdin. In that case, piping XQuery expressions to
MapiClient works fine. No chance, however, to type XQuery
expressions on the command line (and terminate with ^D). I assume
that this is some limitation of the way how MapiClient reads its input.
I would thus suggest to update the documentation and require a file
argument on the command line. Given the above behavior, reading
from stdin is not really convenient anyway. Users could still use /
dev/stdin if they want to (or we could respect the special filename `-'
as many Unix utilities do).
## Comment 2893
Date: 2005-05-02 19:05:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
If I recall correctly from Peter, there were some issues
problems getting "MapiClient -lxquery" to work interactively.
I agree with Jens, that (at least for the first release) we
should simply require a file with the XQuery in MapiClient
commandline, issue an error otherwise, and fix the docu
accordingly. Later, we can take care of the rest.
If I recall correctly, there are some more features
mentioned in HowToStart-PF, which have not been implemented,
yet.
Peter, could you please comment?
Thanks in advance!
## Comment 2894
Date: 2005-05-23 22:40:55 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The intention was definitely that MapiClient would be able
to read from standard input, also for XQuery. However, the
XQuery server is not built in such a way that it can ask for
more input if it finds that the input does not form a
complete query (this is also due to the definition of the
language, I believe--in SQL it can be done because a query
always ends with a semicolon).
I have now fixed MapiClient again to be in-line with the
intention.
It will now happily read from standard input if no file
arguments were given or if the -i (--interactive) option was
given. It will, however, refuse to read from standard input
if that is a terminal.
## Comment 2895
Date: 2005-11-09 14:09:09 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-11-09, sjoerd: NO TEST
## Comment 2896
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1193769 at http://sourceforge.net/support/tracker.php?aid=1193769
| stdin for MapiClient -lxquery | https://api.github.com/repos/MonetDB/MonetDB/issues/527/comments | 0 | 2020-11-30T08:40:57Z | 2024-06-27T11:03:26Z | https://github.com/MonetDB/MonetDB/issues/527 | 753,276,565 | 527 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-29 01:24:51 +0200
From: Wouter Alink <<alink>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-04-29 02:29:41 +0200
## Comment 2888
Date: 2005-04-29 13:24:51 +0200
From: Wouter Alink <<alink>>
.COMMAND kunion ( BAT[any::1,any::2] left,
BAT[any::1,any::2] right) 271
BAT[any::1,any::2] = CMDkunion;
272 "Returns the union of two BATs; looking at
head-columns only.
273 Results in all BUNs of 'left' that are not in
'right', plus all BUNs
274 of 'right'. *no* double-elimination is done.
If you want this, do:
275 'kunion(left.kunique,right.kunique)' or:
'sunion(left,right).kunique'."
var x := bat(oid,int);
var y := bat(oid,int);
x.insert(0@0, 1);
x.insert(1@0, 2);
y.insert(1@0, 3);
y.insert(2@0, 4);
kunion(x,y).print()
would expect
0,1
1,3
2,4
but Monet returns:
-----------------
h tmp_69 name
oid int type
-----------------
[ 0@0, 1 ]
[ 1@0, 2 ]
[ 2@0, 4 ]
am i, is the documentation, or is the implementation
wrong??
## Comment 2889
Date: 2005-04-29 14:29:41 +0200
From: @njnes
Logged In: YES
user_id=43556
this is fixed in the CVS head version.
## Comment 2890
Date: 2005-10-06 21:14:52 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST / SUCCESS
Test added as
tests/BugDay_2005-10-06_4.9.3/Tests/union_semantics.SF-1192348
## Comment 2891
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1192348 at http://sourceforge.net/support/tracker.php?aid=1192348
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.
| Kunion? | https://api.github.com/repos/MonetDB/MonetDB/issues/526/comments | 0 | 2020-11-30T08:40:55Z | 2024-06-27T11:03:25Z | https://github.com/MonetDB/MonetDB/issues/526 | 753,276,535 | 526 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-28 09:47:45 +0200
From: @sjoerdmullender
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-04-28 10:17:20 +0200
## Comment 2884
Date: 2005-04-28 09:47:45 +0200
From: @sjoerdmullender
The test in
compiler/semantics/tests/varscope/Tests/good-004 was
totally bogus until I fixed it the other day and put
the XQery part in a separate file good-004.xq (use "cvs
-p -r1.1 good-004" to see the original). However,
there is a syntax error in that file, and I don't know
what the intention was.
Can somebody fix this?
## Comment 2885
Date: 2005-04-28 10:17:20 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
added missing '"' to test query.
## Comment 2886
Date: 2005-10-06 21:05:55 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST ALLREADY exists in testweb
## Comment 2887
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1191541 at http://sourceforge.net/support/tracker.php?aid=1191541
| bad XQuery syntax in test | https://api.github.com/repos/MonetDB/MonetDB/issues/525/comments | 0 | 2020-11-30T08:40:51Z | 2024-06-27T11:03:24Z | https://github.com/MonetDB/MonetDB/issues/525 | 753,276,493 | 525 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-27 03:03:11 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-05-12 10:25:39 +0200
## Comment 2880
Date: 2005-04-27 15:03:11 +0200
From: @grobian
monetdb-> set time zone interval '+02:00' hour;
monetdb-> select * from sessions;
+------------------+---------+--------------+------------+
| name | value | type | access |
+==================+=========+==============+============+
| debug | 0 | int | 0 |
| reply_size | 250 | int | 0 |
| explain | | varchar | 0 |
| auto_commit | true | boolean | 0 |
| current_schema | sys | varchar | 1 |
| current_user | monetdb | varchar | 1 |
| current_role | monetdb | varchar | 0 |
| current_timezone | 7200 | sec_interval | 0 |
| cache | true | boolean | 0 |
| factory | true | boolean | 0 |
+------------------+---------+--------------+------------+
10 rows
monetdb-> select now();
+---------------------+
| current_timestamp |
+=====================+
| 2005-04-27 12:55:37.0 |
+---------------------+
1 row
monetdb->
(pictor:~/develop/MonetJDBC) fabian% date
Wed Apr 27 14:55:42 CEST 2005
(pictor:~/develop/MonetJDBC) fabian% date +"%z"
+0200
Also, inserting into a table with a timestamp column
results in the same, but:
sql>create table t (t timestamp with time zone);
6 querytype
sql>insert into t values (now());
4 querytype
[ 1 ]
sql>insert into t values ('2005-04-27 12:57:43.000');
4 querytype
[ 1 ]
sql>select * from t;
3 querytype
t table_name
t name
timestamp type
25 length
2 tuplecount
8 id
[ 2005-04-27 14:59:06.000+02:00 ]
[ 2005-04-27 14:57:43.000+02:00 ]
sql>
(which seems to be correct to me)
## Comment 2881
Date: 2005-10-06 21:00:25 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST / SUCCESS
Test added as test/timezone.sql
## Comment 2882
Date: 2005-10-06 21:04:09 +0200
From: @grobian
Logged In: YES
user_id=963970
this is actually what the Jdbc timezone tests test.
## Comment 2883
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1190980 at http://sourceforge.net/support/tracker.php?aid=1190980
| SQL: time zone does not have effect on now() | https://api.github.com/repos/MonetDB/MonetDB/issues/524/comments | 0 | 2020-11-30T08:40:49Z | 2024-06-27T11:03:22Z | https://github.com/MonetDB/MonetDB/issues/524 | 753,276,456 | 524 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-22 01:24:33 +0200
From: @Teggy
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2005-05-24 12:28:53 +0200
## Comment 2872
Date: 2005-04-22 13:24:33 +0200
From: @Teggy
The XQuery query
declare namespace foo = "bar";
<foo:a/>
leads to the faulty serialized result
<foo:aattribute xmlns:foo { bar },
/>
while the query
declare namespace foo = "bar";
<foo:a>
<foo:b/>
</foo:a>
results in the expected
<foo:a xmlns:foo="bar"><foo:b/></foo:a>
## Comment 2873
Date: 2005-05-03 08:03:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
(Now,) I get
08:00:01 manegold@draco:~/Monet/Current/pathfinder $ cat
/tmp/t1.xq
declare namespace foo = "bar";
<foo:a/>
08:00:09 manegold@draco:~/Monet/Current/pathfinder $ pf
/tmp/t1.xq | Mserver --set monet_prompt=''
Monet Database Server V4.7.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<foo:a xmlns:foo="bar"/>
</XQueryResult>
08:00:15 manegold@draco:~/Monet/Current/pathfinder $ cat
/tmp/t2.xq
declare namespace foo = "bar";
<foo:a>
<foo:b/>
</foo:a>
08:00:21 manegold@draco:~/Monet/Current/pathfinder $ pf
/tmp/t2.xq | Mserver --set monet_prompt=''
Monet Database Server V4.7.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult>
<foo:a xmlns:foo="bar"><foo:b/></foo:a>
</XQueryResult>
08:00:25 manegold@draco:~/Monet/Current/pathfinder $
That looks correct to me, right?
Hence, the bug seems to be fixed, and this report should be
closed.
## Comment 2874
Date: 2005-05-03 09:38:19 +0200
From: @Teggy
Logged In: YES
user_id=642632
No, the bug persists when you use MapiClient -lx (in this case,
no top-level <XQueryResult> element is serialized and the result
still is:
$ cat foo.xq
declare namespace foo = "bar";
<foo:a/>
$ MapiClient -lx foo.xq
<foo:aattribute xmlns:foo { bar },
/>
)
It seems to be the serialization of the top-level element
that is affected.
## Comment 2875
Date: 2005-05-03 11:22:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
With the patch below, the problem would be solved.
This patch does not do any harm to the current tests, but
there are no specific tests for the server-side procesing (yet).
Since I'm not too sure, whether this patch is the correct
solution, I don't check it in, yet, but rather propose to
wait until JanF is back from holidays to check it.
========
Index: runtime/serialize.mx
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/runtime/serialize.mx,v
retrieving revision 1.12
diff -u -r1.12 serialize.mx
--- runtime/serialize.mx 20 Apr 2005 11:50:01 -0000
1.12
+++ runtime/serialize.mx 3 May 2005 09:17:15 -0000
@@ -1042,7 +1042,7 @@
oid pre = from;
do {
- if ( !xquery_node_print(ctx,
pre,pre_frag,top&&(from==to)) /*cheat*/ )
+ if ( !xquery_node_print(ctx,
pre,pre_frag,top&&0/*(from==to)*/) /*cheat*/ )
return 0;
if ( !xquery_endtag_print(ctx,++pre) )
return 0;
========
## Comment 2876
Date: 2005-05-24 12:28:53 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Fixed it! The problem was very simple. The top-level result
element detection flag was not set to false for an attribute
of a top-level element. (You're not supposed to understand ths:)
## Comment 2877
Date: 2005-05-24 12:30:50 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Fixed it! The problem was very simple. The top-level result
element detection flag was not set to false for an attribute
of a top-level element. (You're not supposed to understand ths:)
## Comment 2878
Date: 2005-10-06 20:51:40 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST ALLREADY exists in testweb
## Comment 2879
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1187994 at http://sourceforge.net/support/tracker.php?aid=1187994
| Namespace attribute serialization bug | https://api.github.com/repos/MonetDB/MonetDB/issues/523/comments | 0 | 2020-11-30T08:40:46Z | 2024-06-27T11:03:21Z | https://github.com/MonetDB/MonetDB/issues/523 | 753,276,419 | 523 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-22 10:30:02 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-08-17 09:57:55 +0200
## Comment 2868
Date: 2005-04-22 10:30:02 +0200
From: @grobian
the test script except-union-intersect-bug-sf-1146079
shows that the current implementation of INTERSECT,
UNION and EXCEPT does not follow the standard.
A 'tuple per tuple' approach is needed to make the
outputs of these operators correct.
## Comment 2869
Date: 2005-08-17 09:57:55 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed in cvs
## Comment 2870
Date: 2005-10-06 20:44:52 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST exits
Test allready exists in testweb
## Comment 2871
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1187910 at http://sourceforge.net/support/tracker.php?aid=1187910
| SQL: INTERSECT/UNION/EXCEPT semantics | https://api.github.com/repos/MonetDB/MonetDB/issues/522/comments | 0 | 2020-11-30T08:40:42Z | 2024-06-27T11:03:20Z | https://github.com/MonetDB/MonetDB/issues/522 | 753,276,365 | 522 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-21 10:03:30 +0200
From: @Teggy
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-04-21 01:08:20 +0200
## Comment 2863
Date: 2005-04-21 10:03:30 +0200
From: @Teggy
Compiler of pathfinder/runtime/pf_support.c fails with an
`invalid operands to binary !=' error. GCC version 3.3.
Here's the tail of the compilation log:
gcc -DHAVE_CONFIG_H -I.
-I/home/grust/sci/XQuery/pathfinder/runtime -I..
-I/home/grust/sci/XQuery/pathfinder/runtime
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/common
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/gdk
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/monet
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/plain
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/contrib
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/mapi
-I/home/grust/sci/XQuery/Pathfinder/include/MonetDB/C
-I/usr/include/libxml2 -I../compiler/include
-I/home/grust/sci/XQuery/pathfinder/runtime/../compiler/include
-DLIBPF_SUPPORT -g -O2 -std=c99 -Wall -W
-Werror-implicit-function-declaration -Werror
-Wno-format -Wno-unused-function -Wno-unused-label
-Wno-strict-aliasing -c pf_support.c -fPIC -DPIC -o
lib_pf_support_la-pf_support.lo
/home/grust/sci/XQuery/pathfinder/runtime/pf_support.mx:
In function `CMDmvaljoin':
/home/grust/sci/XQuery/pathfinder/runtime/pf_support.mx:1756:
error: invalid operands to binary !=
/home/grust/sci/XQuery/pathfinder/runtime/pf_support.mx:1744:
error: invalid operands to binary !=
make[3]: *** [lib_pf_support_la-pf_support.lo] Error 1
make[3]: Leaving directory
`/home/grust/tmp/pathfinder/runtime'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/grust/tmp/pathfinder/runtime'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/grust/tmp/pathfinder'
make: *** [all] Error 2
Greetings,
--Teggy
## Comment 2864
Date: 2005-04-21 12:36:48 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I suspect this has to do with Niels' changes to the BAT
structure in MonetDB. Please update your MonetDB
installation and try again.
## Comment 2865
Date: 2005-04-21 13:08:20 +0200
From: @Teggy
Logged In: YES
user_id=642632
Yes, after the MonetDB update everything compiles fine again.
Thanks for the quick response, Sjoerd.
## Comment 2866
Date: 2005-10-06 20:42:19 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TESTed by COMPILATION
## Comment 2867
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1187186 at http://sourceforge.net/support/tracker.php?aid=1187186
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.
| Compilation of pf_support.c fails | https://api.github.com/repos/MonetDB/MonetDB/issues/521/comments | 0 | 2020-11-30T08:40:39Z | 2024-06-27T11:03:19Z | https://github.com/MonetDB/MonetDB/issues/521 | 753,276,334 | 521 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-19 03:01:48 +0200
From: Wouter Alink <<alink>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2007-06-05 10:30:51 +0200
## Comment 2848
Date: 2005-04-19 15:01:48 +0200
From: Wouter Alink <<alink>>
Hello,
I was trying to load the INEX collection into
MonetDB/XQuery... but I soon ran into problems. I'm
using the head of MonetDB and today's pathfinder. I
don't know the status of MonetDB/XQuert with regards to
xml-entity-support.
First of all, i was wondering which entities are
declared $amp; >, etc by default? Is there a list of
these entities somewhere? (the only thing i could find
in the xml-spec was that was not part of xml)
Then, after defining some entities for myself I did the
following:
the document a1003.xml is the document attached.
the document a1003b.xml is equal to a1003.xml, but
without the line <!ENTITY mdash "d">.
The first problem is the fact that the entity ‐
has been defined in a1003b.xml and in my opinion should
not be mentioned as an error (see the output below).
(the problem disappears in a1003.xml)
The second problem is that when shredding a 'correct'
document, an error is returned (!ERROR:
interpret_params: insert(param 1): invalid BAT. ), but
obviously it did store the xml-doc.
Besides these errors it might be nice to be able to
include a document in another one (this mechanism is
often used in the INEX collection):
<!ENTITY A1003 SYSTEM "a1003.xml">
Or is this already possible?
Grtz,
Wouter
-------------------------
output:
MonetDB>shred_doc("/ufs/alink/test-data/a1003b.xml","a1003.xml");
/ufs/alink/test-data/a1003b.xml:55: error: Entity
'mdash' not defined
y, let me welcome a number of new article editors to
our Editorial Board —
^
/ufs/alink/test-data/a1003b.xml:55: error: Entity
'hyphen' not defined
cotty, Keith Smillie, James Cortada, and Tim Bergin
have joined our long‐
^
/ufs/alink/test-data/a1003b.xml:55: error: Entity
'hyphen' not defined
Rosin, Brian Randell, Arthur Burks, Bernard Galler,
and Martin Campbell‐
^
/ufs/alink/test-data/a1003b.xml:55: error: Entity
'mdash' not defined
of the <it>Annals</it>. We also welcome aboard a new
Production Manager —
^
!ERROR: XML input not well-formed.
!ERROR: CMDshred2bats: operation failed.
MonetDB>shred_doc("/ufs/alink/test-data/a1003.xml","a1003.xml");
!ERROR: interpret_params: insert(param 1): invalid BAT.
MonetDB>shred_doc("/ufs/alink/test-data/a1003.xml","a1003.xml");
!ERROR: xmlshred: Document a1003.xml already exists
MonetDB>
## Comment 2849
Date: 2005-04-19 15:25:04 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Wouter,
thanks for your bug report.
Let me first address the question in your bug report about predefined
entities in XML. It is a common misunderstanding that all the entities
known from HTML are also valid in XML. XML predefines only five entities
(see also http://www.w3.org/TR/REC-xml/sec-predefined-ent):
< <
> >
& &
' '
" "
Anything else that you want to use must be declared in your DTD.
I'll now start looking into the code what Pathfinder actually does about XML
entities. DTD support has been introduced quite recently; probably the
support is not complete, yet.
## Comment 2850
Date: 2005-04-19 16:32:48 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
I've tested the file (a1003.xml) you attached, and it loads
fine on my system.
You write that the same document, with the entity declaration
for mdash removed produces the errors you describe. I've
tested that as well and can confirm your error messages.
After removing the entity declaration, however, your document
in fact becomes invalid, so it is correct that shred_doc()
rejects the document. The unexpected behavior here is that
shred_doc() seems to complain about the hyphen entity as
well, although that one *is* defined.
I agree that the error messages in that case are a bit
misleading. However, they seem to be produced by the libxml
library that we use. I've checked with a small test program
that produces the exact same error messages. To me, this
appears like a bug in libxml2. (I'm surprised, though, that
xmllint reports errors correctly.)
Concerning your question about including other XML
documents (<!ENTITY A1003 SYSTEM "a1003.xml">):
I've tested that as well. Pathfinder currently does *not*
support that. Again, we depend on the libxml2 library. And
my simple SAX test program already couldn't handle these
includes. I've looked through the libxml2 API, and I suspect
that we hit the ``note that the use of this function for
unparsed entities may generate problems'' (API doc) issue
here. So I don't think we can handle this functionality in the
near future. (Again, xmllint can handle this. xmllint uses
libxml2's DOM mode, maybe this is why xmllint behaves
differently.)
What is left is your `interpret_params: insert(param 1):
invalid BAT' problem. I couldn't reproduce that one here.
What versions of MonetDB and Pathfinders do you use?
Did you initialize MonetDB's database with the same
versions or are they leftovers from older versions?
## Comment 2851
Date: 2005-04-20 12:48:56 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Thanks for helping out. I think I know where the second bug
stems from: I didn't delete my dbfarm after I installed the
new MonetDB with the changed interal format. I tought it
converted the bats automatically, but apparently it didn't.
It now does not happen anymore. (thanx go to peter).
I guess this bug-report has been boiled down to: too many
errors are returned when shredding with undefined entities.
Shall i post a feature request for the
include-a-whole-document-entity, or should we just wait?
## Comment 2852
Date: 2005-04-28 13:19:14 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Have the problems been resolved? If so, please close the
bug report.
## Comment 2853
Date: 2005-05-23 10:59:13 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
The returned error on a mal-formed document reads:
MonetDB>shred_doc("/ufs/alink/test-data/a1003b.xml","a1003b.xml");
!ERROR: XML input not well-formed.
!ERROR: CMDshred2bats: operation failed.
in my opinion this solves the bug
## Comment 2854
Date: 2005-10-06 20:38:17 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST / SUCCESS
Test added as
tests/BugDay_2005-10-06_4.9.3/Tests/Entities.SF-1185932
## Comment 2855
Date: 2006-11-13 11:28:34 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
The test belonging to this bug now fail, and they fail
correctly. There are two xml documents that go with this
test, entities.xml and entities-invalid.xml. Contrary to
what the naming suggests, *both* documents are invalid, and
the shredder, correctly, complains about that.
The problem with the purportedly valid document is that it
has an internal DTD which does not actually describe the
document.
The question is, how to fix this. We can just approve the
output, or we can change the test so that it has a DTD that
matches the document.
## Comment 2856
Date: 2006-11-13 12:42:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
see also BUG #1544002 "PF: several tests fail after recent
checkins" at
http://sourceforge.net/tracker/index.php?func=detail&aid=1544002&group_id=56967&atid=482468
## Comment 2857
Date: 2007-01-23 18:06:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Might be related to
http://sourceforge.net/support/tracker.php?aid=1642663 "XQ: shredding with inline DTD and ENTITIES does not work"
http://sourceforge.net/tracker/index.php?func=detail&aid=1642663&group_id=56967&atid=482468
and/or
http://sourceforge.net/support/tracker.php?aid=1642665 "XQ: shredding DTDs with ENTITIES erroneous"
http://sourceforge.net/tracker/index.php?func=detail&aid=1642665&group_id=56967&atid=482468
## Comment 2858
Date: 2007-05-15 12:09:26 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hoi Jan,
misschien is het leuk voor de aankomende release dat je die entity bugs fixed..
Peter
## Comment 2859
Date: 2007-06-04 10:36:59 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
Hoi Jan,
Voor de planning zou ik graag willen weten of je van plan bent voor de release (11 juni) de entity bugs te fixen of niet..
Peter
## Comment 2860
Date: 2007-06-04 16:32:32 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Originator: NO
Working on it. But through the lack of coherent documentation this is a very hard job. I first build my own entity tables and then discovered they were already there but not used by the parser. I now have the example doc which was the source of this bugreport running and try to figure out what is the cleanest method of handling entities.
## Comment 2861
Date: 2007-06-05 10:30:51 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Originator: NO
Problem is fixed. Implemented a getEntity by hand and ENTITIES now work for internal subsets. Added a testset for it (ID.1648854.xq)
## Comment 2862
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1185932 at http://sourceforge.net/support/tracker.php?aid=1185932
| XML: Entities | https://api.github.com/repos/MonetDB/MonetDB/issues/520/comments | 0 | 2020-11-30T08:40:36Z | 2024-06-27T11:03:18Z | https://github.com/MonetDB/MonetDB/issues/520 | 753,276,310 | 520 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-15 08:46:02 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-04-18 11:04:37 +0200
## Comment 2844
Date: 2005-04-15 08:46:02 +0200
From: @drstmane
Since a few days (see below for details) the test
src/benchmarks/tpch/Tests/load fails on Darwin, Gentoo,
and IRIX with:
========
~ MAPI = monetdb@medusa:53079
QUERY = COPY 5 RECORDS INTO region from
'/db1/tmp/monet.GNU_64-d.18919/sql/src/benchmarks/tpch/SF-0.01/region.tbl'
USING DELIMITERS '|', '|\n';
ERROR = !ERROR: strIconv: operation failed.
!ERROR: interpret_params: open_rastream(param
1): evaluation error.
!ERROR: yytree: sql1:
/db1/tmp/monet.GNU_64-d.18919/sql/src/benchmarks/tpch/SF-0.01/region.tbl.
========
First guess: some changes to sql's configure.ag or
MonetDB's conf/monet.m4 might be related.
On Monday, April 11 2005, the test still worked fine.
On Tuesday, April 12 2005, the test didn't run due to
other problems.
On Wednesday, April 13 2005, the test failed on all
plarforms (I don't know the reason[s]).
Since Thursday, April 14 2005, the test works fine
again on all platforms except Darwin, Gentoo, and IRIX.
## Comment 2845
Date: 2005-04-18 11:04:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Sjoerd.
## Comment 2846
Date: 2005-10-06 20:15:31 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST exists
Test exists as tpch
## Comment 2847
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1183534 at http://sourceforge.net/support/tracker.php?aid=1183534
| SQL: test src/benchmarks/tpch/Tests/load fails on strIconv | https://api.github.com/repos/MonetDB/MonetDB/issues/519/comments | 0 | 2020-11-30T08:40:33Z | 2024-06-27T11:03:17Z | https://github.com/MonetDB/MonetDB/issues/519 | 753,276,281 | 519 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-12 09:48:36 +0200
From: @Teggy
To: @njnes
Version: -- development
Last updated: 2005-04-12 12:38:02 +0200
## Comment 2839
Date: 2005-04-12 09:48:36 +0200
From: @Teggy
After `./bootstrap' and `configure', the variables MX
and MEL
in src/common/Makefile are both set to the string
`yes', resulting in an immediate failure during `make'.
This may be related to the recent changes in configure
option switches (--with-mx, --with-mel).
## Comment 2840
Date: 2005-04-12 09:58:17 +0200
From: @njnes
Logged In: YES
user_id=43556
fix is in cvs, could you try again?
## Comment 2841
Date: 2005-04-12 12:38:02 +0200
From: @Teggy
Logged In: YES
user_id=642632
This fixed it. Thanks.
## Comment 2842
Date: 2005-10-06 20:09:38 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: NO TEST Configure/COMPILATION
## Comment 2843
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1181305 at http://sourceforge.net/support/tracker.php?aid=1181305
| Variables MX and MEL set to `yes' after configure | https://api.github.com/repos/MonetDB/MonetDB/issues/518/comments | 0 | 2020-11-30T08:40:30Z | 2024-06-27T11:03:16Z | https://github.com/MonetDB/MonetDB/issues/518 | 753,276,252 | 518 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-11 05:50:50 +0200
From: rimluga <<rimluga>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-04-12 12:34:56 +0200
## Comment 2825
Date: 2005-04-11 17:50:50 +0200
From: rimluga <<rimluga>>
Hi,
I succeed to compile the source , test the build, install,
but I've problem executing
/usr/local/bin/Mtest.py -r,
the display,
sh-2.05b /usr/local/bin/Mtest.py -r
/bin/sh: line 1: --version: command not found
RECURSIVE = True
QUIET = 0
CONTEXT = -C1
IGNORE = ^
TIMEOUT = 60
ACCURACY = 1
Mtest.py Warning: TSTSRCBASE: Replacing logical path /users/
student/monetdb by absolute physical path /Users/Student/
MonetDB
Mtest.py Warning: TSTBLDBASE: Replacing logical path /Users/
student/monetdbconfig by absolute physical path /Users/Student/
monetdbconfig
MONETDB_SOURCE = /users/student/monetdb
MONETDB_BUILD = /Users/student/monetdbconfig
MONETDB_PREFIX = /usr/local
TSTSRCBASE = /Users/Student/MonetDB
TSTBLDBASE = /Users/Student/monetdbconfig
TSTTRGBASE = /usr/local
SQL_PREFIX =
SQLCLIENT = MapiClient -lsql
MAPICLIENT = MapiClient -lmil
X100CLIENT = x100run_mapi
XQUERYCLIENT = pf -O3
MAPIPORT = 43540
SQLPORT = 55527
GDK_DEBUG = 10
MONETDB_MOD_PATH = /usr/local/lib/MonetDB
SQL_LOGDIR = /usr/local/var/MonetDB/log
GDK_DBFARM = /usr/local/var/MonetDB/dbfarm
setMONETDB_MOD_PATH = --set "monet_mod_path=/usr/local/lib/
MonetDB"
SQL_SERVER = sql_server
PATH = /sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/
teTeX/bin/powerpc-apple-darwin-current:/usr/X11R6/bin
VERSION = 0
MSERVER = : Mserver "--config=/usr/local/etc/MonetDB.conf" --
debug=10 --set "monet_mod_path=/usr/local/lib/MonetDB" --set
"gdk_dbfarm=/usr/local/var/MonetDB/dbfarm" --set "sql_logdir=/usr/
local/var/MonetDB/log" --set mapi_port=43540 --set sql_port=55527
--set monet_prompt= --trace
MTIMEOUT = :
PYTHON = /usr/bin/python : python
SQL_CLIENT = : MapiClient -lsql -u monetdb -P monetdb --
host=rim --port=55527
XQUERY_CLIENT = : pf -O3
MAPI_CLIENT = : MapiClient -lmil -u monetdb -P monetdb "--
config=/usr/local/etc/MonetDB.conf" --host=rim --port=43540
MDIFF = : Mdiff
X100_CLIENT = : x100run_mapi -u monetdb -P monetdb "--config=/
usr/local/etc/MonetDB.conf" --host=rim --port=43540
Mtest.py Warning: Closing input pipe in Check failed with 32:
'Broken pipe'.
Mtest.py: ERROR: 'Mserver "--config=/usr/local/etc/MonetDB.conf"
--debug=10 --set "monet_mod_path=/usr/local/lib/MonetDB" --set
"gdk_dbfarm=/usr/local/var/MonetDB/dbfarm" --set "sql_logdir=/usr/
local/var/MonetDB/log" --set mapi_port=43540 --set sql_port=55527
--set monet_prompt= --trace --dbname=mTests` failed:
! Exit 1
/bin/sh: line 1: Mserver: command not found
Am also unable to launch Mserver, I've the following error,
rim:/usr/local/bin student$ ./Mserver
!FATAL: GDKlockHome: could not move to /usr/local/var/MonetDB/
dbfarm/demo/
Thank you in advance for your help
Best,
## Comment 2826
Date: 2005-04-11 18:00:11 +0200
From: @grobian
Logged In: YES
user_id=963970
Did you run "make install"?
If so, did you get any errors there? Do you have write
access to /usr/local/* ? As normal user, usually not. I
think you forgot to set the appropriate prefix during
configure time. Try for example "./configure
--prefix=/Users/Student/monetdb/"
## Comment 2827
Date: 2005-04-11 18:20:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Apparently, you did configure MonetDB without "--prefix=";
hence, the default "/usr/local" is used as prefix to install
MonetDB, right?
1)
Before running Mtest.py, you need to make sure, that
<prefixdir>/bin (in your case "/usr/local/bin" is in your
PATH. Apparently, this is not the case (see line "PATH=..."
in Mtest.py's console output).
2)
Did you install MonetDB as the same user as you're now
trying to run it?
Given the fact, that you installed it in /usr/local/, I
suppose, you installed it as root. But now, you try to run
it as user "rim" or "student", and I suppose the neither of
the is allowed to write in /usr/local//, right?
Solution:
To run MonetDB, you need to specify a database directory the
the very user has write permission on: "Mserver --dbfarm=..."
Likewise, when running Mtest.py, you need to specify a
directory that the very user has write permission on:
"Mtest.py --TSTTRGBASE=..."
## Comment 2828
Date: 2005-04-11 18:56:45 +0200
From: @drstmane
Logged In: YES
user_id=572415
Hi "rimluga",
since my reply to your mail was bounced, I also put it here:
> am sorry to write here , I didn't find the link to post a
reply,
reply works simply by adding a new comment to the bugreport ;-)
> Should I repeat everything, with sepcificatin of the
prefix to execute the
> configure, How should I proceed? delete what? How can I be
sure to have
> the right permissions
for now, you don't have to redo anything.
please also check the permissions of /usr/local/,
/usr/local/var/,
/usr/local/var/MonetDB/, /usr/local/var/MonetDB/dbfarm/, i.e.,
ls -ld /usr/local/
ls -la /usr/local/var/
ls -la /usr/local/var/MonetDB/
ls -la /usr/local/var/MonetDB/dbfarm/
which of these directories do exist, and which do you have
write permissions
in?
Stefan
> I've two folders: monetdb: the download and I've created
monetdbconfig.
> Both are in users\studentMonet was installed in
/usr/local/bin.
> below the permissions of the /usr/local/bin
>
> rim:/ student$ ls -ld /usr/local/bin
> drwxr-xr-x 56 student staff 1904 11 Apr 16:59
/usr/local/bin
> best
## Comment 2829
Date: 2005-04-11 19:05:40 +0200
From: @grobian
Logged In: YES
user_id=963970
Mail bounces
rimluga wrote:
> Message body follows:
>
> Hi Fabian, am sorry, I don't know how to post a reply in
the forum,
in the bug page below, a text box should be there
>
> I don't know how to allow myself (student) having the full
rights, that's why I connect with sudo please if you know
how tell me
If I were you, I would not user any super user privileges to
install MonetDB. Just follow the relevant instructions
(configure & make) from http://www.cwi.nl/~fabian/
>
> indeed I runned the make install, it seems OK,
>
> you advised me to re-run ./configure with the prefix..,
could I do it after executing make install again,
Try following the link I gave you above. Replace the cvs
part with the tarball you downloaded and omit the bootstrap
part. It should guide you into successful installation of
MonetDB in a folder you specify yourself.
Good luck! Feel free to report any problems.
Fabian
## Comment 2830
Date: 2005-04-12 09:12:43 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Hi Stefan,
thank you, I didn't seen it,
"student" doesn't have permissions, I can log as the root ,
but I don't know how to add myself to the wheel group,
rim:~ student$ ls -ld /usr/local/
drwxr-xr-x 19 root wheel 646 11 Apr 17:06 /usr/local/
rim:~ student$ ls -la /usr/local/var/
total 0
drwxr-xr-x 3 root wheel 102 11 Apr 16:59 .
drwxr-xr-x 19 root wheel 646 11 Apr 17:06 ..
drwxr-xr-x 4 root wheel 136 11 Apr 16:59 MonetDB
rim:~ student$ ls -la /usr/local/var/MonetDB/
total 0
drwxr-xr-x 4 root wheel 136 11 Apr 16:59 .
drwxr-xr-x 3 root wheel 102 11 Apr 16:59 ..
drwxr-xr-x 3 root wheel 102 11 Apr 17:06 dbfarm
drwxr-xr-x 2 root wheel 68 11 Apr 16:59 log
rim:~ student$ ls -la /usr/local/var/MonetDB/dbfarm
total 0
drwxr-xr-x 3 root wheel 102 11 Apr 17:06 .
drwxr-xr-x 4 root wheel 136 11 Apr 16:59 ..
drwxr-xr-x 2 root wheel 68 11 Apr 17:06 mTests
Best, rim
## Comment 2831
Date: 2005-04-12 10:00:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
Dear Rim,
(you could add yourself to group wheel using the "groupadd"
command; see `man groupadd` for details)
BUT:
I highly recommend not to do so.
First, you are apparently not yet too familiar with
unix/linux system administration. That's not a problem as
such, but for normal usage of a unix/linux system one should
NEVER use root priviledges, especially if on eis not (yet) a
very experienced system admin.
Second, adding yourself to group wheel would not solve the
underlying problem, but only tries to cure the symptoms ---
and it would not even help, since the respective directories
are not even writable for group wheel.
In your case --- I suppose you install MonetDB only for
yourself, not for other users --- I highly recommend to
install MonetDB NOT in /usr/local/ (which require(s|d) root
priviledges both to install it), but rather in a local
directory in your home directory, e.g., /home/rim/local/ or
/home/rim/MonetDB/ . The documentation in the "HowToStart"
file in the top-level source directory of MonetDB and/or the
detailed instructions on Fabian's web site
http://www.cwi.nl/~fabian/ should tell you how to do this.
Basically, you should first clean-up what you already
installed in /usr/local/:
a) become user root
b) go to your "monetdbconfig" directory (where you ran
"configure", "make", and "make install"
c) there, run "make uninstall"
d) then remove the whole "monetdbconfig" directory:
cd .. ; rm -rf monetdbconfig
e) leave the root shell, so that you're yourself (user rim),
again.
Then, (as yourself, i.e. user rim !) re-create the
monetdbconfig directory, go to it, and re-build and install
MonetDB, now with a local prefix:
configure --prefix=/home/rim/local
make
make check
make install
Then, you should be able to use MonetDB without problems,
provided <prefix>/bin (i.e., /home/rim/local/bin) is in your
PATH.
## Comment 2832
Date: 2005-04-12 10:23:38 +0200
From: @grobian
Logged In: YES
user_id=963970
> (you could add yourself to group wheel using the "groupadd"
> command; see `man groupadd` for details)
on OS X, use the preferences pane, go to users, and make
yourself an administrative user. You probably already are,
because you can sudo (and so a member of the wheel group).
However, there is a good way why Apple didn't make you an
admin, which Stefan explained up here. (You don't need that
power.)
## Comment 2833
Date: 2005-04-12 10:37:08 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Hi,
I executed the commands you indicated Stefan, and also ./debootstrap in
monetdb folder. I'am following the instructions the steps of Fabian,
At the end of .bootstrap : it displays (it happens also last time, to ignore
according to the installation instructions of monet)
But, should I update configure.in and where should I add
AC_PROG_LIBTOOL
Best, Rim
Remember to add `AC_PROG_LIBTOOL' to `configure.in'.
You should add the contents of `/usr/share/aclocal/libtool.m4' to
`aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `conf'.
automake/aclocal 1.6.3 is older than 1.7.
Patching aclocal.m4 for Intel compiler on Linux (icc/ecc).
patching file aclocal.m4
Hunk 1 FAILED at 2542.
1 out of 1 hunk FAILED -- saving rejects to file aclocal.m4.rej
patching file aclocal.m4
Hunk 1 FAILED at 1184.
Hunk 2 FAILED at 2444.
Hunk 3 FAILED at 2464.
3 out of 3 hunks FAILED -- saving rejects to file aclocal.m4.rej
configure.in: installing `conf/install-sh'
configure.in: installing `conf/mkinstalldirs'
## Comment 2834
Date: 2005-04-12 10:45:38 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Hi, I guess my questions are stupid to you, but I still have others,
the build folder fabian, should be created in monetdb folder or MonetDB
folder
about the prefix: is home a folder? he doesn't recognize it
rim:~ student$ cd /home/Student/MonetDB
-bash: cd: /home/Student/MonetDB: No such file or directory
Best,
## Comment 2835
Date: 2005-04-12 10:52:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
No, you don't need to fix anything. As stated in HowToStart,
just ignore these warnings of bootstrap (they're kind of the
price we pay to be as portable as possible across a wide
range of platforms ...)
And:
Since you're using MacOS (as Fabian correctly discovered, by
I didn't ;-)),
/home/ is called /Users/ .
## Comment 2836
Date: 2005-04-12 12:09:50 +0200
From: rimluga <<rimluga>>
Logged In: YES
user_id=1257166
Hi,
thank you for your help,
Best, Rim
## Comment 2837
Date: 2005-10-06 20:08:08 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: Done / NO TEST
installation issue
## Comment 2838
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1180838 at http://sourceforge.net/support/tracker.php?aid=1180838
| installation of monetdb | https://api.github.com/repos/MonetDB/MonetDB/issues/517/comments | 0 | 2020-11-30T08:40:26Z | 2024-06-28T13:35:18Z | https://github.com/MonetDB/MonetDB/issues/517 | 753,276,223 | 517 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-09 10:33:36 +0200
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2005-04-14 05:57:30 +0200
## Comment 2820
Date: 2005-04-09 22:33:36 +0200
From: @drstmane
Compilation of runtime/shredder.mx fails in case the
available libxml2 does not provide
xmlCreateURLParserCtxt(), as e.g., on Darwin:
========
gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU_32-d.14056/pathfinder/runtime -I..
-I/var/tmp/monet.GNU_32-d.14056/pathfinder/runtime
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/common
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/gdk
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/monet
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/plain
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/contrib
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/mapi
-I/var/tmp/monet.GNU_32-d.14056/MonetDB/.GNU_32-d/Darwin7.8.0/include/MonetDB/C
-I/Users/monet/soft/local//include
-I/usr/include/libxml2 -I../compiler/include
-I/var/tmp/monet.GNU_32-d.14056/pathfinder/runtime/../compiler/include
-I/sw/include -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions
-Werror-implicit-function-declaration -Werror
-Wno-format -Wno-unused-function -Wno-unused-label
-Wno-uninitialized -c shredder.c -fno-common -DPIC -o
.libs/shredder.o
/var/tmp/monet.GNU_32-d.14056/pathfinder/runtime/shredder.mx:
In function `mainSHREDDER':
/var/tmp/monet.GNU_32-d.14056/pathfinder/runtime/shredder.mx:1510:
error: implicit declaration of function
`xmlCreateURLParserCtxt'
/var/tmp/monet.GNU_32-d.14056/pathfinder/runtime/shredder.mx:1510:
warning: assignment makes pointer from integer without
a cast
make[3]: *** [shredder.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
========
Apparently, not all libxml2 implementations come with a
xmlCreateURLParserCtxt(); hence, I'd propose to add a
check for this function to configure.ag, define a marco
HAVE_xmlCreateURLParserCtxt, and guard the respective
code with this marco (and produce a proper runtime
error message in case xmlCreateURLParserCtxt() would
have been called).
Thus, we don't get compilation errors; however, the
respective functionality will then not be available
(configure should warn about this).
Alternatively, we could make pathfinder require
xmlCreateURLParserCtxt(); then, configure should issue
a proper error message and stop in case it does not
find xmlCreateURLParserCtxt().
## Comment 2821
Date: 2005-04-11 10:14:17 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
There were problems with the other SAX2 updates too with
this system I remember. I think it will become very complex
to have all these HAVE_xxxx for every subtle version
difference. I propose to to put the already existing
HAVE_SAX2 define around the xmlCreateURLParserCtxt() call
and enforce when HAVE_SAX2 is defined the
xmlCreateURLParserCtxt() function exists.
[PS. xmlCreateURLParserCtxt() is not a very 'new' function.
It already existed mid 2003.]
## Comment 2822
Date: 2005-04-14 17:57:30 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by JanF:
* Repair Darwin problem where the xmlCreateURLParserCtxt()
is not know. I put
a if HAVE_SAX2 around it because Darwin does not support
this either. So
when HAVE_SAX2 is not defined the follwoing functionality
is missing:
+ correct namespace handling, eg. xmlns:xx constructions
+ shredding of documents by specifyng their URL
## Comment 2823
Date: 2005-10-06 20:01:35 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TESTed by COMPILATION
## Comment 2824
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1179907 at http://sourceforge.net/support/tracker.php?aid=1179907
| PF: compilation fails without xmlCreateURLParserCtxt() | https://api.github.com/repos/MonetDB/MonetDB/issues/516/comments | 0 | 2020-11-30T08:40:23Z | 2024-06-27T11:03:14Z | https://github.com/MonetDB/MonetDB/issues/516 | 753,276,183 | 516 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-08 10:56:57 +0200
From: Jens Teubner <<teubner>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2005-04-14 09:15:54 +0200
## Comment 2808
Date: 2005-04-08 10:56:57 +0200
From: Jens Teubner <<teubner>>
I actually like the setup with server-side XQuery compilation a lot,
and it seems to work very well. However, I think there's one thing we
could even improve.
If Mserver is started as described in HowToStart-PF, it opens a Mapi
port (45789) for XQuery requests. My students now tried to load
some document with shred_doc(). They quickly figured that a
simple `MapiClient' failed with a `connection refused' error for port
50000. But they found out that Mserver is listening on 45789 and that
MapiClient has this nice `-p' command line option. So they did a
`MapiClient -p 45789'.
What you get this way is a really strangely behaving MapiClient.
Regardless on what you enter, you always just get the `more>'
prompt. If you type ^D, you will get some Pathfinder error message.
What I was missing here is an informative error message. I'd
suggest that MapiClient checks if the port it is connected to actually
``speaks'' the right language. It should report an error if you connect
to a MIL port in XQuery mode and vice versa.
(Another thing is that the documentation states that you can connect
to the running Mserver with MapiClient and load documents with
shred_doc(). If started as described, however, Mserver does NOT
open a MIL port, only an XQuery port. We should fix the
documentation here.)
teubner@phobos09:~> MapiClient -p 45789
mil>print(42);
more>
more>syntax error, unexpected $end on line 2
parse error: XQuery parsing failed
halted in parser.y (PFparse), line 2238
## Comment 2809
Date: 2005-04-08 11:13:00 +0200
From: @grobian
Logged In: YES
user_id=963970
Each server sends an identification string upon connect. It
can be used to detect language mismatches, and optionally
issue a warning.
However, I think that when giving the right language flag to
MapiClient, it should never be necessary to use the port
flag, but I might be wrong at this.
## Comment 2810
Date: 2005-04-08 11:13:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
(Also) from HowToStart-PF:
========
[...]
Executing XQuery queries:
-------------------------
Use the xquery language setting of MapiClient (-lxquery or
short -lx):
MapiClient -lx [files]
This executes a *single* xquery found in the file (or
multiple files, which are concatenated),
or on standard input (if no file is passed), and prints the
serialized result.
In case of standard input, interactive mode is not allowed.
You must pipe in a script:
MapiClient -lx < file.xq
[...]
========
Hence, you should use "MapiClient -lx[query]" to execute XQuery.
However, with me this results in an immediate exit of
MapiClient:
(Mserver --dbinit='module(pathfinder,mapi); pfstart();')
MapiClient -lxquery ; echo $?
0
I guess, Sjoerd and or Peter should have a closer look.
## Comment 2811
Date: 2005-04-08 12:00:41 +0200
From: @drstmane
Logged In: YES
user_id=572415
I just recalled, that there were some limitations related to
server-side XQuery & MapiClient. Basically, the XQuery
parser does not seem to be interactive, and hence,
MapiClient can read XQuery only directly from a file:
========
$ MapiClient -lxquery ; echo $?
0
$ cat /tmp/bad001.xq | MapiClient -lxquery ; echo $?
0
$ MapiClient -lxquery < /tmp/bad001.xq ; echo $?
0
$ MapiClient -lxquery /tmp/bad001.xq ; echo $?
xquery disabled. Please configure & compile MonetDB with
--with-gc=DIR
0
========
Sjoerd and/or Peter should know more.
Obviously, the HowToStart-PF needs to be fixed accordingly.
## Comment 2812
Date: 2005-04-08 12:08:20 +0200
From: @drstmane
Logged In: YES
user_id=572415
To be able to use shred_doc() (i.e., MIL) via MapiClient,
just change
Mserver --dbinit='module(pathfinder,mapi); pfstart();'
to
Mserver --dbinit='module(mapi,pathfinder); mapi_start();
pfstart();'
and then use "MapiClient [-lmil]" for MIL and "MapiClient
-lx[query]" for XQuery.
Note:
It seems to be important to load module "mapi" before module
"pathfinder", and to execute "mapi_start();" before
"pfstart();";
otherwise, Mserver crashed when MapiClient quits:
Mserver:
/ufs/manegold/Monet/Current/MonetDB/src/monet/monet_tbl.mx:1713:
TBL_M_decref: Assertion `p' failed.
Aborted (core dumped)
## Comment 2813
Date: 2005-04-08 12:16:44 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
> However, I think that when giving the right language flag to
> MapiClient, it should never be necessary to use the port
> flag, but I might be wrong at this.
Well, I know how to invoke Mserver and MapiClient the right way. But this
is not my point. The point is that other people did (and will do) it the wrong
way, and they don't even get any useful warning.
If I was an outside person, trying to play with Pathfinder/MonetDB the first
time, I'd probably do the same mistake. So I'd argue to exit MapiClient with
an error message if one uses the wrong port/language combination.
Fabian's comment suggests that this could easily be caught in MapiClient.
## Comment 2814
Date: 2005-04-08 12:27:00 +0200
From: @drstmane
Logged In: YES
user_id=572415
Oops, I obviously didn't get it --- but I completely agree
with you and Fabian ;-)
Nevertheless, "someone" should check HowToStart-PF
carefully, and fix it where necessary.
## Comment 2815
Date: 2005-04-08 12:53:45 +0200
From: @grobian
Logged In: YES
user_id=963970
> Well, I know how to invoke Mserver and MapiClient the
right way.
> But this
> is not my point. The point is that other people did (and will
> do) it the wrong
> way, and they don't even get any useful warning.
I get your point, and I think we both want the same here. A
warning wouldn't be that hard to add I think.
> If I was an outside person, trying to play with
Pathfinder/MonetDB
> the first
> time, I'd probably do the same mistake. So I'd argue to exit
> MapiClient with
> an error message if one uses the wrong port/language
combination.
I think this should never happen at all. An outside
(windows) person, should have one obvious way to do it. If
that's not documented clearly somehow, you will lose such
user immediately right after that point. Every user that
starts playing with flags other than -lxquery somehow lost
the instructions or wants to play for him/herself, something
I think we don't have to support. Again, we should make
sure that a user will not get lost easily.
## Comment 2816
Date: 2005-04-08 13:33:19 +0200
From: @grobian
Logged In: YES
user_id=963970
I checked in a little patch that gives a warning if there is
a mismatch between the chosen language and what language the
server says it understands.
## Comment 2817
Date: 2005-04-14 21:15:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Has been fixed by Fabian.
## Comment 2818
Date: 2005-10-06 20:00:04 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: NO TEST
## Comment 2819
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1179073 at http://sourceforge.net/support/tracker.php?aid=1179073
| Mapi ports XQuery <-> MIL | https://api.github.com/repos/MonetDB/MonetDB/issues/515/comments | 0 | 2020-11-30T08:40:20Z | 2024-06-27T11:03:13Z | https://github.com/MonetDB/MonetDB/issues/515 | 753,276,144 | 515 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-04 09:33:51 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-04-05 03:53:57 +0200
## Comment 2804
Date: 2005-04-04 21:33:51 +0200
From: Jan Rittinger <<jan.rittinger>>
compiled without optimization using gcc 3.3.3 (SuSE
Linux):
> echo '***' | pf
illegal reference to context node: at (1,1-1,1): ``.'' is
unbound
halted in /local_tmp/rittinge/pathfinder/compiler/core/fs.
brg (reduce), line 2721
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@inf.uni-konstanz.de).
When reporting problems, please attach your XQuery
input,
as well as the following information:
Invocation: command line
Compilation stage: 8
We apologize for the inconvenience...
Segmentation fault
## Comment 2805
Date: 2005-04-05 15:53:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
The segmentation faults reported here and in BUG #1175855 "PF: all "bad-???" tests in compiler// fail since
Mar 24 2005"
(http://sourceforge.net/tracker/index.php?func=detail&aid=1175855&group_id=56967&atid=482468)
were actually cause by the fact that the call of "setjmp()"
was hidden
in function "hidden_setjmp()" (which was done to keep some
compilers from
complaining about clobbered variables).
Fix:
remove "hidden_setjmp()", again;
instead, we call "setjmp()" before variables are declared.
also moved the "setjmp()" call for the stand-alone compiler
from "main()" to "pf_compiler()";
the "setjmp()" call for the in-lined server-side compiler
is in "pf_compiler_MonetDB()".
!
Note:
BUG #1175855 "PF: all "bad-???" tests in compiler// fail
since Mar 24 2005"
(http://sourceforge.net/tracker/index.php?func=detail&aid=1175855&group_id=56967&atid=482468)
is not fixed, yet; please look there for details!
!
## Comment 2806
Date: 2005-10-06 17:12:38 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TESTed by COMPILATION
## Comment 2807
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1176566 at http://sourceforge.net/support/tracker.php?aid=1176566
| correct error messages triggers segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/514/comments | 0 | 2020-11-30T08:40:17Z | 2024-06-27T11:03:12Z | https://github.com/MonetDB/MonetDB/issues/514 | 753,276,111 | 514 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-04 10:42:08 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-04-04 09:25:02 +0200
## Comment 2799
Date: 2005-04-04 10:42:08 +0200
From: @drstmane
On test tests/XQuery/Tests/orderby3.xq , the XQuery
compiler "pf" fails with:
========
!ERROR: Segmentation fault.
The Pathfinder compiler experienced an internal problem.
You may want to report this problem to the Pathfinder
development team (pathfinder@inf.uni-konstanz.de).
When reporting problems, please attach your XQuery input,
as well as the following information:
Invocation: command line
Compilation stage: 12
We apologize for the inconvenience...
========
(cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU_32-d_Fedora3/tests_XQuery/orderby3.err.00.html
)
## Comment 2800
Date: 2005-04-04 16:30:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
Debugging seem to reveal that PFty_simplfy seem to return a
messed-up "t1":
========
16:24:32 manegold@draco:~/Monet/Stable/pathfinder $ gdb pf
GNU gdb Red Hat Linux (6.1post-1.20040607.43rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using
host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) r tests/XQuery/Tests/orderby3.xq
Starting program:
/var/tmp/_Current_PREFIX__GNU_32_d_--enable-debug_--enable-noexpand=all_/bin/pf
tests/XQuery/Tests/orderby3.xq
[Thread debugging using libthread_db enabled]
[New Thread -1208101184 (LWP 7114)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208101184 (LWP 7114)]
0x0806b0fc in subtype (t1={type = 135087410, name = {ns =
{ns = 0x80d4532 "*", uri = 0x0}, loc = 0x0}, sym_space =
0x0, child = {0x0, 0xa18df38}}, t2=
{type = ty_atomic, name = {ns = {ns = 0x80d4532 "*",
uri = 0x80d4532 "*"}, loc = 0x0}, sym_space = 0x0, child =
{0x0, 0x0}}, a=0xa18dc68)
at
/ufs/manegold/Monet/Stable/pathfinder/compiler/semantics/subtyping.c:1415
1415 switch ((*trivial)[t1.type][t2.type]) {
(gdb) bt
0 0x0806b0fc in subtype (t1={type = 135087410, name = {ns
= {ns = 0x80d4532 "*", uri = 0x0}, loc = 0x0}, sym_space =
0x0, child = {0x0, 0xa18df38}}, t2=
{type = ty_atomic, name = {ns = {ns = 0x80d4532 "*",
uri = 0x80d4532 "*"}, loc = 0x0}, sym_space = 0x0, child =
{0x0, 0x0}}, a=0xa18dc68)
at
/ufs/manegold/Monet/Stable/pathfinder/compiler/semantics/subtyping.c:1415
1 0x0806b57a in PFty_equality (t1=
{type = 135087410, name = {ns = {ns = 0x80d4532 "*",
uri = 0x0}, loc = 0x0}, sym_space = 0x0, child = {0x0,
0xa18df38}}, t2=
{type = ty_atomic, name = {ns = {ns = 0x80d4532 "*",
uri = 0x80d4532 "*"}, loc = 0x0}, sym_space = 0x0, child =
{0x0, 0x0}})
at
/ufs/manegold/Monet/Stable/pathfinder/compiler/semantics/subtyping.c:1557
2 0x080ad0ce in simplifyCoreTree (c=0x9988d30) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8674
3 0x080ad20e in simplifyCoreTree (c=0x9988940) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8694
4 0x080ab3f4 in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8299
5 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
6 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
7 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
8 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
9 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
10 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
11 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
12 0x080ab00f in simplifyCoreTree (c=0x99881d0) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8226
13 0x080ad20e in simplifyCoreTree (c=0x9988160) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:8694
14 0x080af9c0 in PFprintMILtemp (c=0x9988160,
status=0x8109d40, tm=518837758, prologue=0xbff3c520,
query=0xbff3c51c, epilogue=0xbff3c518)
at
/ufs/manegold/Monet/Stable/pathfinder/compiler/mil/milprint_summer.c:9874
15 0x0804ba96 in pf_compile (pfin=0x98b3008,
pfout=0xd195c0, status=0x8109d40) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/compile.c:318
16 0x0804b4f1 in main (argc=2, argv=0xbff3c634) at
/ufs/manegold/Monet/Stable/pathfinder/compiler/main.c:705
(gdb) print t1
$1 = {type = 135087410, name = {ns = {ns = 0x80d4532 "*",
uri = 0x0}, loc = 0x0}, sym_space = 0x0, child = {0x0,
0xa18df38}}
(gdb) print t2
$2 = {type = ty_atomic, name = {ns = {ns = 0x80d4532 "*",
uri = 0x80d4532 "*"}, loc = 0x0}, sym_space = 0x0, child =
{0x0, 0x0}}
(gdb) li 1405
1400 PFty_str (ty_pair_set_elem (a,
n)->snd));
1401 else
1402 PFlog ("subtyping: [nothing]");
1403 endif /* DEBUG_TYPES */
1404
1405 t1 = *PFty_simplify (PFty_defn (t1));
1406 t2 = *PFty_simplify (PFty_defn (t2));
1407
1408 ifdef DEBUG_TYPES
1409 PFlog ("subtyping: (1) simplify inequality [%s
<: %s]",
(gdb) li 1415
1410 PFty_str (t1), PFty_str (t2));
1411 endif /* DEBUG_TYPES */
1412
1413 /* consult the XQuery type hierarchy first */
1414 assert (trivial);
1415 switch ((*trivial)[t1.type][t2.type]) {
1416 case 0:
1417 ifdef DEBUG_TYPES
1418 PFlog ("subtyping: NO PROOF (trivial/type
hierarchy)");
1419 endif /* DEBUG_TYPES */
(gdb)
========
## Comment 2801
Date: 2005-04-04 21:25:02 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
sorry (copied code and forgot to check if the variables were
initialized) -- now fixed.
## Comment 2802
Date: 2005-10-06 17:11:13 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST exists
Existing test
tests/XQuery/Tests/orderby3.xq
## Comment 2803
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1176219 at http://sourceforge.net/support/tracker.php?aid=1176219
| PF: XQuery compiler fails with Segmentation fault | https://api.github.com/repos/MonetDB/MonetDB/issues/513/comments | 0 | 2020-11-30T08:40:14Z | 2024-06-27T11:03:11Z | https://github.com/MonetDB/MonetDB/issues/513 | 753,276,084 | 513 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-04 10:37:09 +0200
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2005-04-04 09:22:35 +0200
## Comment 2795
Date: 2005-04-04 10:37:09 +0200
From: @drstmane
On tests tests/XPathMark/Tests/Q22.xq &
tests/XQuery/Tests/union.xq ,
the XQuery compiler "pf" fails with:
pf:
/var/tmp/monet.GNU_32-d.732/pathfinder/compiler/core/core.c:637:
PFcore_seq: Assertion `((e1) && ((e1)->kind ==
c_lit_str || (e1)->kind == c_lit_int || (e1)->kind ==
c_lit_dec || (e1)->kind == c_lit_dbl || (e1)->kind ==
c_true || (e1)->kind == c_false || (e1)->kind ==
c_empty || (e1)->kind == c_var))' failed.
## Comment 2796
Date: 2005-04-04 21:22:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
fixed - called PFcore_seq in simplifyCoreTree without binding
the expression to a variable.
solution: call 'PFcore_wire2(c_seq,...' instead of 'PFcore_seq(.
..'
## Comment 2797
Date: 2005-10-06 17:10:34 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST exists
existing test tests/XPathMark/Tests/Q22.xq
## Comment 2798
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1176217 at http://sourceforge.net/support/tracker.php?aid=1176217
| PF: XQuery compiler fails with assertion | https://api.github.com/repos/MonetDB/MonetDB/issues/512/comments | 0 | 2020-11-30T08:40:11Z | 2024-06-27T11:03:10Z | https://github.com/MonetDB/MonetDB/issues/512 | 753,276,060 | 512 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-04-04 10:23:27 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-04-04 04:18:11 +0200
## Comment 2791
Date: 2005-04-04 10:23:27 +0200
From: @drstmane
With Intel's icc on Linux, we get:
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/ufs/manegold/Monet/Stable/pathfinder/runtime -I..
-I/ufs/manegold/Monet/Stable/pathfinder/runtime
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/common
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/gdk
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/monet
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/plain
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/contrib
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/mapi
-I/var/tmp/_Current_PREFIX__ntv_32_d_--enable-debug_--enable-noexpand=all_/include/MonetDB/C
-I/soft/local/include -I/usr/include/libxml2
-I../compiler/include
-I/ufs/manegold/Monet/Stable/pathfinder/runtime/../compiler/include
-we140 -wd1418 -c99 -Wall -w2 -g -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c shredder.c -KPIC -DPIC -o .libs/shredder.o
/ufs/manegold/Monet/Stable/pathfinder/runtime/shredder.mx(897):
error 556: a value of type "char *" cannot be assigned
to an entity of type "const xmlChar={unsigned char} *"
a_pfx = emptyString;
^
/ufs/manegold/Monet/Stable/pathfinder/runtime/shredder.mx(901):
error 556: a value of type "char *" cannot be assigned
to an entity of type "const xmlChar={unsigned char} *"
a_uri = emptyString;
^
/ufs/manegold/Monet/Stable/pathfinder/runtime/shredder.mx(905):
error 556: a value of type "char *" cannot be assigned
to an entity of type "const xmlChar={unsigned char} *"
a_uri = a_pfx = emptyString;
^
compilation aborted for shredder.c (code 2)
make[2]: *** [shredder.lo] Error 1
make[2]: Leaving directory
`/var/tmp/_Current_BUILD_PATHFINDER_ntv_32_d_--enable-debug_--enable-noexpand=all_/runtime'
## Comment 2792
Date: 2005-04-04 16:18:11 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed by adding proper casts.
## Comment 2793
Date: 2005-10-06 17:09:06 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TESTed by COMPILATION
## Comment 2794
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1176206 at http://sourceforge.net/support/tracker.php?aid=1176206
| PF: runtime/shredder.mx fails to compile with Intel's icc | https://api.github.com/repos/MonetDB/MonetDB/issues/511/comments | 0 | 2020-11-30T08:40:07Z | 2024-06-27T11:03:09Z | https://github.com/MonetDB/MonetDB/issues/511 | 753,276,029 | 511 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.