Is anybody here using a Macintosh computer to access ASE via python and pyODBC?

Is anybody here using a Macintosh computer to access ASE via python and pyODBC?

Postby gerham » Sat 01 Apr 2017 18:10

Hi,

Is anybody here using a Macintosh computer to access ASE via python and pyODBC ?

I get an pycharm disconnect within just a few seconds with the DEVART drivers and it's driving me crazy. It takes a restart of the pycharm (python) debugger to continue developing

pycharm reports

"Process finished with exit code 245"

When I push my VIRTUAL ENVIRONMENT over to Centos for User testing the DEVART drivers seem much more stable under NGINX.

On the Mac, under pycharm, they are very fragile. Other members in my team use the same setup but access postgresql and mongo via different NON-DEVART drivers. Only I use the DEVART drivers on a Mac.

Is anybody here using a Macintosh computer to access ASE via python and pyODBC?
Any clues on how to stop this?
gerham
 
Posts: 12
Joined: Thu 22 Sep 2016 23:58

Re: Is anybody here using a Macintosh computer to access ASE via python and pyODBC?

Postby gerham » Sat 01 Apr 2017 18:15

This is my pycharm crash. Every 30 seconds the pycharm debugger process crashes out.
I am rstarting the pycharm debugger often, every 30 s

All also happens outside the pycharm debugger. just once every 45 seconds. Not much relief

It looks to me as though you have some pointer malloc errors.

python(64469,0x70000100a000) malloc: *** error for object 0x7fd2d42bc200: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
02.Dec 2016 23:35:07.180465: get_codesmd start Consent_TypeID

Process finished with exit code 250 or 245 or 249


Only happens when the Devart ODBC drivers are active and doing their thing.

libdevartodbcase.x64 seems to be the problem area.

"malloc" seem to be the root issue



Thread 4 Crashed:
0 libdevartodbcase.x64.dylib 0x0000000106e2e3c4 0x106de4000 + 304068
1 libdevartodbcase.x64.dylib 0x0000000106fb26a7 0x106de4000 + 1894055
2 libdevartodbcase.x64.dylib 0x0000000106fb25ea 0x106de4000 + 1893866
3 libdevartodbcase.x64.dylib 0x0000000106f7dc3e 0x106de4000 + 1678398
4 libdevartodbcase.x64.dylib 0x0000000106f6f291 0x106de4000 + 1618577
5 libdevartodbcase.x64.dylib 0x0000000106f7d2ba 0x106de4000 + 1675962
6 pyodbc.so 0x00000001060ab492 execute(Cursor*, _object*, _object*, bool) + 272
7 org.python.python 0x0000000104371979 PyEval_EvalFrameEx + 14227
gerham
 
Posts: 12
Joined: Thu 22 Sep 2016 23:58

Re: Is anybody here using a Macintosh computer to access ASE via python and pyODBC?

Postby MaximG » Fri 05 May 2017 08:59

We tested the work of Devart ODBC Driver for ASE in MacOS X environment when using pyODBC and pyCharm. Unfortunately, we could not reproduce the problem according to the description. For further investigation, please provide some addtitional information:
- the exact pyCharm version which you are using
- specify the name and the exact version of ODBC manager used in MacOS X environment
- compose and send us a small complete project execution of which causes the problem. You can do this using the e-support form ( https://www.devart.com - menu «Support»\«Request Support» )
MaximG
Devart Team
 
Posts: 745
Joined: Mon 06 Jul 2015 11:34

Re: Is anybody here using a Macintosh computer to access ASE via python and pyODBC?

Postby gerham » Fri 05 May 2017 14:18

Thanks Guys.

I realise I need to supply a packaged up VirtualEnv with python 2.7/pyodbc 3/ unixodbc/ devart and flask 0.10, which displays the devart drivers crashing. I will supply this next week. Thank you for the reply
gerham
 
Posts: 12
Joined: Thu 22 Sep 2016 23:58

Re: Is anybody here using a Macintosh computer to access ASE via python and pyODBC?

Postby MaximG » Wed 10 May 2017 14:45

We will wait for news from you after the testing is finished.
MaximG
Devart Team
 
Posts: 745
Joined: Mon 06 Jul 2015 11:34


Return to ODBC Drivers