baidu / baidu/lac

C++ Call Stacks

Open
#119 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
4k
Forks
592
PR merge metrics
No merged PRs in 30d

Description

terminate called after throwing an instance of 'paddle::platform::EnforceNotMet'
what():

--------------------------------------------
C++ Call Stacks (More useful to developers):
--------------------------------------------
0 std::string paddle::platform::GetTraceBackString(std::string const&, char const*, int)
1 paddle::PaddleBuf::Free()
2 paddle::PaddleTensor::~PaddleTensor()

----------------------
Error Message Summary:
----------------------
Error: An error occurred here. There is no accurate error hint for this error yet. We are continuously in the process of increasing hint for this kind of error check. It would be helpful if you could inform us of how this conversion went by opening a github issue. And we will resolve it with high priority.
- New issue link: https://github.com/PaddlePaddle/Paddle/issues/new
- Recommended issue content: all error stack information
[Hint: Expected length_ > 0UL, but received length_:0 <= 0UL:0.] at (/paddle/paddle/fluid/inference/api/api.cc:107)

已放弃

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the reported C++ stack, especially paddle::platform::GetTraceBackString, PaddleBuf::Free, PaddleTensor::~PaddleTensor, and /paddle/paddle/fluid/inference/api/api.cc:107. Reproduce the conversion that leaves length_ at 0, then determine the intended error handling and confirm the result no longer aborts.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.