public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30665] DAP Server: Relative paths in stacktrace response
Date: Sun, 23 Jul 2023 17:48:09 +0000	[thread overview]
Message-ID: <bug-30665-4717-fegQfqGhg7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30665-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
The gdb log has:

4:38:59 PM  <-- stackTrace
{"request_seq":11,"type":"response","command":"stackTrace","body":{"stackFrames":[{"id":0,"name":"main::main","line":3,"column":0,"instructionPointerReference":"0x555555408175","source":{"name":"main.rs","path":"main.rs","sourceReference":0}}]},"success":true,"seq":37}

... whereas the lldb log uses "path":"/home/vmakaev/gdb-test/main.rs".

gdb also sends this "path" value in other spots, so it seems specific
to stack trace.

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

  parent reply	other threads:[~2023-07-23 17:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 23:49 [Bug gdb/30665] New: " vmakaev at gmail dot com
2023-07-23  0:21 ` [Bug gdb/30665] " vmakaev at gmail dot com
2023-07-23  0:42 ` [Bug dap/30665] " vmakaev at gmail dot com
2023-07-23 14:57 ` vmakaev at gmail dot com
2023-07-23 17:48 ` tromey at sourceware dot org [this message]
2023-07-23 17:48 ` tromey at sourceware dot org
2023-07-24 14:56 ` tromey at sourceware dot org
2023-07-24 15:00 ` tromey at sourceware dot org
2023-07-24 15:02 ` tromey at sourceware dot org
2023-07-24 16:26 ` tromey at sourceware dot org
2023-07-24 17:20 ` vmakaev at gmail dot com
2023-07-24 18:23 ` tromey at sourceware dot org
2023-07-25 13:50 ` tromey at sourceware dot org
2023-07-26 15:58 ` tromey at sourceware dot org
2023-08-01 18:55 ` cvs-commit at gcc dot gnu.org
2023-08-01 18:56 ` 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-30665-4717-fegQfqGhg7@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).