public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/27238] [gcc-11] FAIL: gdb.go/package.exp: setting breakpoint at package2.Foo
Date: Mon, 02 Oct 2023 18:50:22 +0000	[thread overview]
Message-ID: <bug-27238-4717-Gsslziq8lc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27238-4717@http.sourceware.org/bugzilla/>

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

--- Comment #10 from Ian Lance Taylor <ian at airs dot com> ---
For a simple function like Run in this example, the name has two components:
the package-path and the name.  The symbol is the encoded package-path,
followed by ".", followed by the encoded name.

In normal usage, when building with "go build", GCC is invoked with a
-fgo-pkgpath option that sets the package path.  This will be based on the
module name and the package name.  When gccgo is invoked with the -fgo-pkgpath
option (or the older -fgo-prefix option) then the pkgpath will be the string
"go." (with a trailing period) followed by the package name that appears in the
source code.  In this case the package name in the source code is "läufer", so
the package-path is "go.läufer".  The "." is encoded as "_0", the "ä" is
encoded as "_u00e4", hence the encoded package-path is "go_0l_u00e4ufer".

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

  parent reply	other threads:[~2023-10-02 18:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 12:33 [Bug go/27238] New: " vries at gcc dot gnu.org
2021-01-26  7:54 ` [Bug go/27238] " vries at gcc dot gnu.org
2021-01-26  8:42 ` vries at gcc dot gnu.org
2021-01-26  8:43 ` vries at gcc dot gnu.org
2023-01-19 21:41 ` tromey at sourceware dot org
2023-02-17  0:41 ` tromey at sourceware dot org
2023-02-17  0:41 ` tromey at sourceware dot org
2023-10-02  8:31 ` vries at gcc dot gnu.org
2023-10-02  9:14 ` vries at gcc dot gnu.org
2023-10-02 11:33 ` vries at gcc dot gnu.org
2023-10-02 18:50 ` ian at airs dot com [this message]
2023-10-02 21:53 ` ian at airs dot com
2023-10-05  8:44 ` vries at gcc dot gnu.org
2023-10-05 13:10 ` vries at gcc dot gnu.org
2023-10-05 14:51 ` vries at gcc dot gnu.org
2023-10-05 21:22 ` cvs-commit at gcc dot gnu.org
2023-10-05 21:23 ` vries at gcc dot gnu.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-27238-4717-Gsslziq8lc@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).