[minicoredumper] [PATCH 0/3] Data collection fixes

[Simon Marchi]

I have been working on making GDB report bytes that have not been collected
in the minicoredump as "unavailable".  That is, trying to read these bytes
from the core will fail.  This uncovered these three issues that show that
there is some information missing in the minicoredump.

A "standard" gdb wouldn't fail, because it would read those bytes as zeroes.
However, it is unsafe because we don't know if the data at these addresses
was really 0 or not.  A gdb with the "unavailable bytes" shows many things
failing because some memory reads from the core suddenly start to fail.  When
we investigate the source of these errors, it is relatively easy to find what
gdb is trying to access, and figure out why that information is not included
in the minicoredump (and how to make it available).


Simon Marchi (3):
  dump_vma: use mem_end instead of file_end
  find_pthreads_cb: Call td_thr_get_info on the thread
  Dump NUL character at the end of solib name

 src/minicoredumper/corestripper.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

-- 
2.5.1