public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30676] modules event includes non-path "path"
Date: Tue, 01 Aug 2023 19:08:32 +0000	[thread overview]
Message-ID: <bug-30676-4717-l6hp7xJJCR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30676-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30676

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7b4a5561e4bfc251f35c3bdf14f5a780cd3695a8

commit 7b4a5561e4bfc251f35c3bdf14f5a780cd3695a8
Author: Tom Tromey <tromey@adacore.com>
Date:   Tue Jul 25 10:55:14 2023 -0600

    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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-01 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 14:56 [Bug dap/30676] New: " tromey at sourceware dot org
2023-07-24 16:20 ` [Bug dap/30676] " tromey at sourceware dot org
2023-07-25 16:21 ` tromey at sourceware dot org
2023-07-25 16:50 ` tromey at sourceware dot org
2023-07-25 16:57 ` tromey at sourceware dot org
2023-07-26 15:58 ` tromey at sourceware dot org
2023-08-01 19:08 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-01 19:16 ` tromey at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30676-4717-l6hp7xJJCR@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).