Don't supply DAP 'path' for non-file shared libraries
authorTom Tromey <tromey@adacore.com>
Tue, 25 Jul 2023 16:55:14 +0000 (10:55 -0600)
committerTom Tromey <tromey@adacore.com>
Tue, 1 Aug 2023 19:06:53 +0000 (13:06 -0600)
commit7b4a5561e4bfc251f35c3bdf14f5a780cd3695a8
tree84db1f6ffc82f0edf236c128b1c09c214a19ddae
parente13769988480865662e8347ed9f131ce0b8f5afc
Don't supply DAP 'path' for non-file shared libraries

The DAP 'module' event may include a 'path' component.  I noticed that
this is supplied even when the module in question does not come from a
file.

This patch only emits this field when the objfile corresponds to a
real file.

No test case, because I wasn't sure how to write a portable one.
However, it's clear from gdb.log on Linux:

{"type": "event", "event": "module", "body": {"reason": "new", "module": {"id": "system-supplied DSO at 0x7ffff7fc4000", "name": "system-supplied DSO at 0x7ffff7fc4000"}}, "seq": 21}

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30676
gdb/python/lib/gdb/dap/modules.py