public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vmakaev at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30665] New: DAP Server: Relative paths in stacktrace response
Date: Sat, 22 Jul 2023 23:49:31 +0000	[thread overview]
Message-ID: <bug-30665-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30665
           Summary: DAP Server: Relative paths in stacktrace response
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vmakaev at gmail dot com
  Target Milestone: ---

Created attachment 14996
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14996&action=edit
Log files and main.rs

When debugging with newly added DAP server my VSCode shows me and error 

"Could not load source 'main.rs': 'source'."

The same binary debugged with LLDB DAP works correctly. Most likely the issue
is due to some responses from DAP having relative path instead of absolute path

Attaching logs from debugging session with gdb and lldb and also a main.rs
program.


(to compile I used "rustc -g main.rs")

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

             reply	other threads:[~2023-07-22 23:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 23:49 vmakaev at gmail dot com [this message]
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
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@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).