开云体育

开云体育

Running Cpp sample client out of the box.

I receive a segmentation fault.

0x00005555555efba6 in __bid64_to_string ()

Have sourced this function to client file to?Decimal.h

extern "C" void __bid64_to_string(char*, Decimal, unsigned int*);

This may have something to do with the floating point library that the API documentation mentions: Intel? Decimal Floating-Point Math Library

I have checked if this is installed on my ubuntu version, using WSL Ubuntu 20.04.05

libintelrdfpmath-dev/now 2.0u2-4 amd64 [installed,local]

Looking at the makefile:

CXXFLAGS=-pthread -Wall -Wno-switch -Wpedantic -Wno-unused-function -std=c++11
ROOT_DIR=../../../source/cppclient
BASE_SRC_DIR=${ROOT_DIR}/client
INCLUDES=-I${BASE_SRC_DIR} -I${ROOT_DIR}
SHARED_LIB_DIRS=${BASE_SRC_DIR}
SHARD_LIBS=libTwsSocketClient.so
TARGET=TestCppClient

$(TARGET)Static:
    $(CXX) $(CXXFLAGS) $(INCLUDES) $(BASE_SRC_DIR)/*.cpp ./*.cpp $(BASE_SRC_DIR)/lib/libbid.a -o$(TARGET)Static

$(TARGET):
    $(CXX) $(CXXFLAGS) $(INCLUDES) ./*.cpp $(BASE_SRC_DIR)/lib/libbid.so $(SHARED_LIB_DIRS)/$(SHARD_LIBS) -o$(TARGET)

clean:
    rm -f $(TARGET) $(TARGET)Static *.o

The interesting part - I can compile the exact same code on Windows, VScode in win32.

I have tried to enforce 32bit with gcc. adding -m32.

When doing this compiler shows numerous complaints:

 1974 |  printf("Soft dollar tiers (%lu):", tiers.size());
      |                             ~~^     ~~~~~~~~~~~~
      |                               |               |
      |                               |               std::vector<SoftDollarTier>::size_type {aka unsigned int}
      |                               long unsigned int
      |                             %u

I commented out these functions which include %lu as do not need them in main application.

Compile again, this time we have errors with the librarys that are packaged with the TWS API - the Intel decimal floating point math library, these libs come with the original TWS installation and locate:

/source/cppclient/client/lib/libbid.a

/usr/bin/ld: i386:x86-64 architecture of input file `../../../source/cppclient/client/lib/libbid.a(bid64_string.o)' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `../../../source/cppclient/client/lib/libbid.a(bid128_2_str_tables.o)' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `../../../source/cppclient/client/lib/libbid.a(bid_decimal_data.o)' is incompatible with i386 output

win32 runs this just fine vscode.

running with ```gcc -m64``

Obtain seg fault again:

Thread 1 "TestCppClientSt" received signal SIGSEGV, Segmentation fault.
0x00005555555efba6 in __bid64_to_string ()
(gdb) bt
#0  0x00005555555efba6 in __bid64_to_string ()
#1  0x00007fffffffd940 in ?? ()
#2  0x00007fffffffd940 in ?? ()
#3  0x00007fffffffd940 in ?? ()
#4  0x00007fffffffd941 in ?? ()
#5  0x00007fffffffd940 in ?? ()
#6  0x00007fffffffd820 in ?? ()
#7  0x000055555555d5ff in std::iterator_traits<char*>::difference_type std::distance<char*>(char*, char*) ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Not sure what it could be at this point - WSL and running ubuntu on windows - that process manages memory? is ubuntu clashing with windows.

At this point - what else can I check / troubleshoot?

Thanks

Hello! I want to ask how to calculate standard deviation for strike which is shown in option chains as popup on mouse cursor hover on strike:

I found that 1 standard deviation = stock price * volatility * square root of days to expiration/365. But in case of strike STD, stock price should be replaced with strike and what volatility should be used? IV?

Thanx

?

Is there any utility available for reading API logfile? Or any pointer on how to read these files?

Thanks

I think you have led me to a solution. I am using an older version of the ewrapper from an older version of the API. I have been working in VS2015 just because it is what I had installed. I can't open the newer samples with it, so I am downloading a new version of Visual Studio. I have a slow internet connection, so it may be a while? before I can look and see for sure. Thanks for your help.

They will definitely occur in case your internet connection is flaky. But We get them every night during the scheduled reset period (see )

• Message code 1100 at 23:17:37.220, 23:17:44.290, 23:17:49.284, 23:17:54.284, 23:18:00.200, 23:18:04.290, and 23:18:09.986
• Message code 1102 at 23:18:19.154

All times are US/Central.

闯ü谤驳别苍

When do you experience the 1100 errors, oho? During the IBKR maintenance windows and on weekends?

Take a look at the section of the TWS API Reference Guide. At the top of that section you'll find a little more detail about connection errors.

When we receive 1100 errors, we shortly after that receive code 1102 "Connectivity between IB and TWS has been restored- data maintained." so that nothing really needs to be done. The connection between our clients and TWS./IBGW is never impacted so that the clients do not have to restart.

We have never seen code 1101 "Connectivity between IB and TWS has been restored- data lost.". In case your client gets this message code, simply resubmit the market data requests your client had active before error 1100.

闯ü谤驳别苍

On Thu, Jan 5, 2023 at 11:30 PM, GreenGreen wrote:

* * Good point about OS resources, but my knowledge of OS are so limited that it looks like Python path is a bit easier.

Yeah, well... give it time and that stuff will become obvious. I was just taking an educated guess but if you're really curious you can actually read through the Python code for multiprocessing . Look inside process.py and subsequently context.py to get the final word on exactly what's happening "under the hood". Have fun :-)