- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
I think having the base pointer and memory allocation size as well as the pointer where the unitialized access occurs would help.
Obviously you must have the information internally so it would just be a matter of displaying it somewhere in the error report.
Thanks.
I think having the base pointer and memory allocation size as well as the pointer where the unitialized access occurs would help.
Obviously you must have the information internally so it would just be a matter of displaying it somewhere in the error report.
Thanks.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That is a nice suggestion, Laurent. Let me take it to Engineering and see what we can come up with. We have found that overloading information in a column is confusing, and we do not want to add too many columns which will complicate the interface.
Do note that the allocation point (if heap allocated) is shown as a related observation, so the information is available with a couple of clicks.
Do note that the allocation point (if heap allocated) is shown as a related observation, so the information is available with a couple of clicks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sure just having it in the detailled report after a double click would certainly be enough for me.
Laurent,
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page