-
Notifications
You must be signed in to change notification settings - Fork 74k
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
Segfault when calling TF_OperationGetAttrTensor on malformed tensor #7394
Comments
We should probably error our more safely, but could you elabore on what you mean by an "empty" tensor? A tensor with Perhaps |
Yes thanks, that makes sense. It just seems problematic that a malformed tensor should cause |
@asimshankar do we plan to add a check or this is expected? |
It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly. |
1 similar comment
It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly. |
Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly. |
ping @asimshankar is this resolved? |
Ah, I hadn't gotten to this, but it seems like a simple fix. I'll try to get this out soon. |
On 1.0.0-rc1 (and earlier versions), this segfaults:
Note that
TF_Message(status)
isTF_OK
after the calls toTF_SetAttrTensor
andTF_FinishOperation
.The text was updated successfully, but these errors were encountered: