Hello Market Analysis Developers,
First of all thank you for creating a 64bit version.
I've attempted to run the version 1.8.2 beta.
The host is a VirtualBox machine running Ubuntu server 14.04.1 LTS.
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
uname -r
3.13.0-34-generic
uname -m
x86_64
cat /proc/meminfo | grep Mem
MemTotal: 501788 kB
MemFree: 164644 kB
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 69
Stepping: 1
CPU MHz: 2388.173
BogoMIPS: 4776.34
L1d cache: 32K
L1d cache: 32K
L2d cache: 6144K
NUMA node0 CPU(s): 0
The price data is stored on MySQL running on the same host. I am able to successfully connect from the mysql command line client to the mas database using the credentials in the mas_dbrc.
I had to create the three symbolic links inorder to get this far.
/usr/lib/x86_64-linux-gnu/libodbc.so.2 -> libodbc.so.1.bak
/usr/lib/x86_64-linux-gnu/libodbcinst.so.2 -> libodbcinst.so.1
/usr/lib/odbc/libmyodbc.so -> /usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so
This is the mas command line and error.
mas -p -b 13579
Caught signal in main routine:
Segmentation fault (11)
Details: Exception occurred :
"Segmentation fault"
from class "ANY".
Type of Exception : Operating system signal.
EXTENDED_MA_SERVER root's creation Segmentation fault:
<00007FA296226748> Operating system signal. Exit
EXTENDED_MA_SERVER root's creation
<00007FA296226748> Routine failure. Exit
EXTENDED_MA_SERVER root's creation
<00007FA296226748> Routine failure. Exit
If anyone could help me I'd be very gratefull.
Thanks for reporting this. I'm not surprised by this bug, since I've not yet tested the ODBC functionality of the new 64-bit mas executable and because the change from the old Eiffel compiler from several years ago to the up-to-date version (release 14.05) has introduced quite a few incompatibilities, some of which caused compiler errors (and were fixed) and some of which cause run-time errors. I've fixed many of the run-time errors but since I've not yet tested with ODBC I've not had time to look at ODBC-related problems. So it's good to receive this report to verify my suspicion that there are basic problems with ODBC due to the port that need tending to.
As far as timing for looking at this, I plan to tackle it at some point; but I'm working on another time-critical project (using MAS, but not ODBC) right now and won't be able to get to other tasks for probably at least several weeks. I hope to be able to get ODBC working (no guarantees) by the end of the year and possibly within a month or two.
Hey!
New message, please read http://topeleventokenhacks.com/use.php?m2
Jeff Epler
This, and all your other messages, "Jack Coats", appears to be spam - i.e., value: 0.
Hey!
New message, please read http://skinrefined.com/forward.php?k
Jean Edo
Hey!
Open message http://iceconstruction.com.sg/body.php?jk
Jean Edo
Hey!
Open message http://physiotherapyspecialists.co.uk/wall.php?e1ir
Mikeyz90
Hey!
Open message http://astro-babylon.ru/worth.php?boz
Jean Edo
Hey!
Open message http://kiddyland.com.sg/sudden.php?ydp
Mikeyz90
Hello!
You have a new message, please read http://trademark-homes.net/increase.php?ubst1
Greg Cooper