I'm able to make the sapdb client segfault all the way from a perl script using DBD::ODBC, the script is attached here, this is what happens:

ff@leo:~/projects/sapdb/test> ./testsapdb-odbc.pl
Connecting (to :ZDB as TEST/TEST)...Segmentation fault

GDB tells me this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 4678)]
0x00000000 in ?? ()
(gdb) where
#0 0x00000000 in ?? ()
#1 0x00000001 in ?? ()
Cannot access memory at address 0x3dc7ba3f


I've tried recompiling the driver with debugging, but then everything works.

This is a long-standing problem, I initially didn't worry about it because I just kept running with the debug version of the lib, hoping that this would get fixed by the time I upgraded the lib...

Silly me:)

Have others seen this?

Can it be caused by giving the DSN ':ZDB' ?

I don't want to have to maintain an extra list of DSN's, just to be able to connect to the databases that I have (duplication of data and all that)

--
Regards Flemming Frandsen - http://dion.swamp.dk
PartyTicket.Net co founder & Yet Another Perl Hacker

Attachment: testsapdb-odbc.pl
Description: Perl program

Reply via email to