Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Activity for Intel A80486DX2-66
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Edit | Post #296586 |
Post edited: Moved the debugger example to parentheses |
— | 25 days ago |
| Comment | Post #296587 |
With the essential clarification provided by alx in their comment (more) |
— | 26 days ago |
| Comment | Post #296588 |
What if the pointer is cast to an integer before reading?
```c
printf("%#" PRIxPTR "\n", (uintptr_t) pointer);
``` (more) |
— | 26 days ago |
| Edit | Post #296586 |
Post edited: Clarified the question |
— | 26 days ago |
| Comment | Post #296587 |
I understand that dereferencing pointers to deallocated memory is undefined behavior. However, I am specifically asking about the pointer value (the address) itself. Is it undefined behavior to simply read, copy or compare the address after the memory it pointed to has been deallocated? (more) |
— | 26 days ago |
| Edit | Post #296586 |
Post edited: |
— | 26 days ago |
| Edit | Post #296586 | Initial revision | — | 26 days ago |
| Question | — |
Is it UB to read value of heap pointer after freeing? I've read in a guide that "the use of indeterminate memory for anything, including apparently harmless comparison or arithmetic, can have undefined behavior if the value can be a trap representation for the type." The included quote from C11, section 6.2.4 §2, says: > The value of a pointer bec... (more) |
— | 26 days ago |