public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31088] gdb requires build directories to exist
Date: Wed, 29 Nov 2023 17:07:26 +0000	[thread overview]
Message-ID: <bug-31088-4717-s78LmSq4h9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31088-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
In particular the latest draft (note draft! can still change!)
https://snapshots.sourceware.org/dwarfstd/dwarf-spec/latest/
says:

--- DRAFT ---

A DW_AT_comp_dir attribute whose value is a null-terminated string containing
the current working directory of the compilation command that produced this
compilation unit in whatever form makes sense for the host system.

If a relative path is used in DW_AT_comp_dir, it will be relative to the
location of the linked image containing the DW_AT_comp_dir entry.

In some cases a producer may allow the user to specify a relative path for
DW_AT_comp_dir. There are a few cases in which this is useful, but in general
using a relative path for DW_AT_comp_dir is discouraged as it will not work
well in many cases including the following: different relative paths are used
within the same build; the build system creates multiple linked images in
different directories; the final linked image is moved before being debugged; .o
files that need to be debugged directly.

--- DRAFT ---

So that seems to imply that you really shouldn't use relative paths (like "."),
unless you can make sure that when the image or source files are moved (or the
DWARF is put into a separate .debug file) like when doing make install, all the
relative are updated/resolved/rewritten.

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

  parent reply	other threads:[~2023-11-29 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 18:33 [Bug gdb/31088] New: " giecrilj at stegny dot 2a.pl
2023-11-29 16:54 ` [Bug gdb/31088] " fche at redhat dot com
2023-11-29 16:55 ` mark at klomp dot org
2023-11-29 17:07 ` mark at klomp dot org [this message]
2023-12-04 19:50 ` amerey at redhat dot com

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-31088-4717-s78LmSq4h9@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).