-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
syncd crash on master RPC image #6622
Comments
can you provide the suspicious commit id? |
@tahmed-dev , can you take a look? |
Looking. |
The unmangled symbols is: Looks like recent TSimpleServer is using |
for the second proposal, it is using CXXFLAGS="-DFORCE_BOOST_SMART_PTR" , I do not quite understand the proposal here. |
The second proposal to remove the macro definition such that it will use On another note and for first proposal above, there is no 0.13.0 in Debian packaging and it was not back-ported to buster. |
do you know why it is added, and who? |
@stepanblyschak the boost flag was introduced via PR:2640 Wonder why it was forced to use boost variant? |
@liat-grozovik , can you take a look at the question? |
@tahmed-dev @lguohan |
thanks @stepanblyschak! Indeed thrift 0.11.0 is using Let me dig further why the mangled name differed when upgraded to boost v1.71. I am under the impression that this compile time dependency would not affect mangled names. I might be wrong. I'll wait to see the recent build of syncd rpc. |
@Junchao-Mellanox, @daall was the issue seen with RPC syncd built after PR:6649 got merged and syncd compiled with that PR? |
I verified with hash aae9664, the issue is still there.
|
Description
syncd crash on master RPC image, error log:
The issue is found beween hash 25e4d77 and hash 46b3bd5. I went over all changes between two hash, here is a suspicious commit: 8ce1e3e
In this commit, it removes libboost-all-dev and upgrade it to libboost1.71-dev.
Steps to reproduce the issue:
Load master RPC image
Describe the results you received:
syncd crash and not all dockers up
Describe the results you expected:
syncd should be able to up correctly
Additional information you deem important (e.g. issue happens only occasionally):
Found at hash 46b3bd5
The text was updated successfully, but these errors were encountered: