BewareMyPower commented on issue #9796: URL: https://github.com/apache/pulsar/issues/9796#issuecomment-801171217
I noticed that you provided some confused info. `setBlockIfQueueFull` accepts a `bool` value, `setBlockIfQueueFull(100000)` is same with `setBlockIfQueueFull(true)` in C++, or did you mean `setMaxPendingMessages(100000)`? And I also found a point from your gdb core. The stack 0 is `bits/std_functions.h` (just an included header of `<function>`) from `devtoolset-9` (did it mean GCC 9?) but the other stacks are all from `/usr/include/c++/4.8.2`, which is the default GCC of CentOS 7. I think GCC 4.8 is enough for building Pulsar C++ client, though it has some ABI incompatibilities with GCC >= 5. Could you compile it with pure GCC 4.8 including the dependencies? ---- BTW, I think the efficient communication way is “Asynchronous Communication”, which is also adopted by my company. I have my own jobs to focus on. Therefore, the best way is to provide detail information in the issue as much as we can, which can both save our time and the details are open to anyone from the community. The key point is how did you deploy your pulsar and run your code. For example: 1. I deploy the pulsar standalone simply by running `bin/pulsar standalone` with latest master. 2. The completed C++ code was pasted before. 3. The C++ compiler is `Apple clang version 12.0.0` and the OS is MacOS, though I think it won't make a big difference. So, could you repeat my steps and see if the segmentation fault happen again? If yes, the issue might be hard to locate. But you can still provide the information about how did you compile the C++ library its dependencies. For example, - CentOS 7 - GCC 4.8 - Boost 1.72 which is compiled from source with GCC 4.8 - Protobuf 2.6 which is compiled from source with GCC 4.8 - ... Otherwise, you should do some experiments to see which difference lead to the problem. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
