[all-commits] [llvm/llvm-project] 3b7611: [Offload] Improve error reporting on memory faults...

[Johannes Doerfert via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 3b7611594f010ecd5233ab9580b2feb88837f9ef
      https://github.com/llvm/llvm-project/commit/3b7611594f010ecd5233ab9580b2feb88837f9ef
  Author: Johannes Doerfert <johannes at jdoerfert.de>
  Date:   2024-08-21 (Wed, 21 Aug 2024)

  Changed paths:
    M offload/plugins-nextgen/amdgpu/src/rtl.cpp
    M offload/plugins-nextgen/common/include/ErrorReporting.h
    M offload/plugins-nextgen/common/include/PluginInterface.h
    M offload/test/sanitizer/double_free.c
    M offload/test/sanitizer/double_free_racy.c
    M offload/test/sanitizer/free_wrong_ptr_kind.c
    M offload/test/sanitizer/free_wrong_ptr_kind.cpp
    A offload/test/sanitizer/ptr_outside_alloc_1.c
    A offload/test/sanitizer/ptr_outside_alloc_2.c
    A offload/test/sanitizer/use_after_free_1.c
    A offload/test/sanitizer/use_after_free_2.c

  Log Message:
  -----------
  [Offload] Improve error reporting on memory faults (#104254)

Since we can already track allocations, we can diagnose memory faults to
some degree. If the fault happens in a prior allocation (use after free)
or "close but outside" one, we can provide that information to the user.
Note that the fault address might be page aligned, and not all accesses
trigger a fault, especially for allocations that are backed by a
MemoryManager. Still, if people disable the MemoryManager or the
allocation is big enough, we can sometimes provide valueable feedback.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications