-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[BUGFIX] Fix issue with LogMessageFatal #20848
[BUGFIX] Fix issue with LogMessageFatal #20848
Conversation
There were two different versions of the LogMessageFatal class in the same namespace in different files so depending on order of compilation it sometimes cause mixing it and segmentation fault (probably due to mixing versions of constructor/destructor (one inlined and one linked))
Hey @anko-intel , Thanks for submitting the PR
CI supported jobs: [edge, unix-cpu, windows-gpu, miscellaneous, website, centos-gpu, windows-cpu, sanity, unix-gpu, centos-cpu, clang] Note: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anko-intel: Why are these files modified here?
3rdparty/mshadow is no git module any longer. The other words it is not real 3rparty now |
@mxnet-bot run ci [centos-gpu, centos-cpu] |
Jenkins CI successfully triggered : [centos-cpu, centos-gpu] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks!
Description
There were two different versions of the LogMessageFatal class in the
same namespace in different files so depending on order of compilation
it sometimes cause mixing it and segmentation fault (probably due to
mixing versions of constructor/destructor (one inlined and one linked))
It is connected with the issue reported on v1.x branch: #20827
Checklist
Essentials