Symptom
- An ESP project crashes while in the process of logging error messages.
- In the stdstreams.log file, messages similar to the following may be logged:
- tcmalloc: large alloc 139896504336384 bytes == (nil) @
Out of memory ERROR in thread 25480. - If you retrieve the stack trace from the core file that is produced, you should see a call to "getAdapterError" in the stack trace:
- $ gdb $ESP_HOME/bin/esp_server core
- (gdb) where
- ...etc...
-
#45 0x00007f43b2807c51 in std::string::append(std::string const&) () from /work/nstack/ESP51_SP4/ESP-5_1/bin/../lib/libstdc++.so.6 #46 0x00007f439a8ff512 in getAdapterError () from /work/nstack/ESP51_SP4/ESP-5_1/lib/adapters/libesp_adapter_util_lib.so #47 0x00007f43b5cfb826 in NewConnection::getError(std::string&) () from /work/nstack/ESP51_SP4/ESP-5_1/bin/../lib/libesp_server_lib.so #48 0x00007f43b56d294a in ConnectionWriter::doNonGDMode() () from /work/nstack/ESP51_SP4/ESP-5_1/bin/../lib/libesp_server_lib.so #49 0x00007f43b56d57c7 in ConnectionWriter::execute() () from /work/nstack/ESP51_SP4/ESP-5_1/bin/../lib/libesp_server_lib.so #50 0x00007f43b64aa2f1 in pt::_threadproc(void*) () from /work/nstack/ESP51_SP4/ESP-5_1/bin/../lib/libesp_system_lib.so #51 0x00007f43b3ace6a6 in start_thread () from /lib64/libpthread.so.0 #52 0x00007f43b2071f7d in clone () from /lib64/libc.so.6 #53 0x0000000000000000 in ?? ()
Read more...
Environment
- ESP 5.1
Product
SAP Event Stream Processor 5.1
Keywords
core crash abort , KBA , BC-SYB-ESP , Sybase ESP (Event Stream Processor) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.