Not widely known problem in programming? (Developers)
> > I'd call this a type of "use after free".
>
> Yep, me too. The program is effectively using memory after it is
> considered "freed" back to the system.
>
> Apparently AddressSanitizer can
> sometimes
> detect such "stack use after return" bugs. But I am not sure if
> AddressSanitizer works (or can be made to work) with Free Pascal, or even
> with 32-bit DPMI.
No. The page it states its patches for LLVM and gcc, not an independent tool like valgrind.
Complete thread:
- Not widely known problem in programming? - Laaca, 27.03.2021, 20:06 (Developers)
- Not widely known problem in programming? - ecm, 27.03.2021, 20:30
- Not widely known problem in programming? - tkchia, 28.03.2021, 08:02
- Not widely known problem in programming? - marcov, 28.03.2021, 17:44
- Not widely known problem in programming? - bretjohn, 29.03.2021, 20:03
- Not widely known problem in programming? - Laaca, 29.03.2021, 22:24
- Not widely known problem in programming? - bretjohn, 29.03.2021, 23:02
- Not widely known problem in programming? - marcov, 30.03.2021, 12:05
- Not widely known problem in programming? - bretjohn, 29.03.2021, 23:02
- Not widely known problem in programming? - ecm, 29.03.2021, 22:26
- Not widely known problem in programming? - Laaca, 29.03.2021, 22:24
- Not widely known problem in programming? - tkchia, 28.03.2021, 08:02
- Not widely known problem in programming? - ecm, 28.03.2021, 21:52
- Not widely known problem in programming? - Laaca, 29.03.2021, 05:04
- Not widely known problem in programming? - ecm, 27.03.2021, 20:30