Question Re: debugging software that connects to SAP ASE in Technology Q&A

debugging software that connects to SAP ASE

oneeyeman1 — Thu, 21 May 2026 03:00:51 GMT

Hi,

I'm trying to run gdb on my software that should connect to SAP ASE.

Both the server (version 16.1) and my software located on Linux.

So this is my scenario:

1. Laptop booted up.

2. Server starts up.

3. I ran gdb on my program.

4.. I am able to run it successfully until I find the problem.

5.. When I hit the problem I quit the gdb immediately and go to fix the issue.

6. After that I recompile and start gdb again.

7. At that point the only thing I can do is connect to the server. No query can be executed. The program just stuck somewhere inside the server.

Does this sounds familiar to anybody?

The server is started with the following script:

[code]

ulimit -s unlimited
cd /opt/sap
su
source SYBASE.sh
. /opt/sap/SYBASE.sh
cd ASE-16_1/install
startserver -f RUN_REINCLOUD

[/code]

Is there any way to continue debugging on the second run of my program?

When I interrupted the second gdb session I get the following gdb backtrace:

[code]

[Thread 0x7fffeaa7e640 (LWP 11506) exited]
^C
Thread 1 "dbhandler" received signal SIGINT, Interrupt.
0x00007ffff5ac4f6f in poll () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff5ac4f6f in poll () from /lib64/libc.so.6
#1  0x00007ffff76230c0 in __interceptor_poll (fds=0x7fffffff79f8, nfds=1, timeout=-1)
    at /var/tmp/portage/sys-devel/gcc-11.3.0/work/gcc-11.3.0/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:3961
#2  0x00007fffe777252b in SybaseTds::TCPSocket::Receive(SybaseTds::TdsBaseContext*, unsigned char*, int, bool, bool) ()
   from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#3  0x00007fffe776461f in SybaseTds::SocketManager::ReadResponse(SybaseTds::TdsBaseContext*) ()
   from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#4  0x00007fffe7792e60 in SybaseTds::TdsContext::GetChunk(SynchronizedManagedQueue<SybaseTds::BufferInterval, LoggedSyncronizer<SpinLock> >::Node**) () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#5  0x00007fffe7744a88 in SybaseTds::TdsDataInputStream::ReadByte(unsigned char*) ()
   from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#6  0x00007fffe77b8a70 in SybaseTds::Tokenizer::ProcessNextToken(SybaseTds::TdsBaseDataInputStream*, SybaseTds::TokenHandler*, SybaseTds::TdsBaseContext*, unsigned char*) () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#7  0x00007fffe778a396 in SybaseTds::TdsCommand::GetNextResult() () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#8  0x00007fffe778d5bd in SybaseTds::TdsCommand::ExecuteNonCursor() () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#9  0x00007fffe778d7c2 in SybaseTds::TdsCommand::ExecParsedCommand(bool) () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#10 0x00007fffe7823aab in SybaseOdbc::OdbcStatement::ExecuteParameterSets(bool, bool&, short&, MTResultState&) ()
   from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#11 0x00007fffe7827b8e in SybaseOdbc::OdbcStatement::ExecStatement() () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#12 0x00007fffe7828669 in SybaseOdbc::OdbcStatement::ExecDirect(unsigned char const*, int) ()
   from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#13 0x00007fffe78104b1 in SQLExecDirectWWork(void*, wchar_t*, int) () from /opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so
#14 0x00007fffe97e1ee7 in SQLExecDirectW () from /usr/lib64/libodbc.so.2
#15 0x00007fffe9c9be2e in ODBCDatabase::CreateSystemObjectsAndGetDatabaseInfo (this=0x61600004b680, errorMsg=...)
    at ../../libodbc/database_odbc.cpp:2094
#16 0x00007fffe9c84102 in ODBCDatabase::Connect (this=0x61600004b680, selectedDSN=..., dbList=..., errorMsg=...)
    at ../../libodbc/database_odbc.cpp:981
--Type <RET> for more, q to quit, c to continue without paging--

[/code]

Re: debugging software that connects to SAP ASE

ChrisBaker — Thu, 21 May 2026 11:51:13 GMT

The trace appears to be in the ODBC driver, not ASE, IMHO. I would suggest opening a support incident with SAP instead of attempting to fix yourself. Possible issues can then be tracked and resolved through a case, especially if it touches other components of the product, or requires engineering support.

There is also a possibility that any issue could be known and already being worked on or fixed.

Chris

Re: debugging software that connects to SAP ASE

oneeyeman1 — Thu, 21 May 2026 15:30:58 GMT

@ChrisBaker, where do I report it? Thank you.

Re: debugging software that connects to SAP ASE

ChrisBaker — Thu, 21 May 2026 15:41:11 GMT

Start with the link here - https://support.sap.com/en/index.html

Re: debugging software that connects to SAP ASE

oneeyeman1 — Thu, 21 May 2026 17:58:11 GMT

@ChrisBaker,

And then I should click "Get Support", right?

Do I need a paid account to file an issue?

Thank you.

P.S.: I think that when I interrupt the debugging session some resources are not cleaned up properly and so the server thinks there is still a connection.

Re: debugging software that connects to SAP ASE

oneeyeman1 — Fri, 22 May 2026 04:25:36 GMT

@ChrisBaker,

It looks like there is an open transaction somewhere because the loop starts on "BEGIN TRANSACTION" execution...

Re: debugging software that connects to SAP ASE

ChrisBaker — Thu, 28 May 2026 12:00:47 GMT

You must be current on support to submit cases. Is this a trial version of ASE?

Re: debugging software that connects to SAP ASE

oneeyeman1 — Thu, 28 May 2026 18:49:51 GMT

@ChrisBaker, yes it is a trial version.

Re: debugging software that connects to SAP ASE

sladebe — Wed, 24 Jun 2026 19:33:46 GMT

Is your test program starting a transaction? When you "quit the gdb" (exit your program) the corresponding process in the ASE server should disappear. Does it? Specifically, if you run sp_who in the ASE server do you:

see your gdb process when it's running and
see the process go away when you exit gdb?

When you say "No query can be executed" on the 2nd run, not even something like "select @@servername" ?

You can also use sp_lock to see if there's a blocking lock.