public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/27238] New: [gcc-11] FAIL: gdb.go/package.exp: setting breakpoint at package2.Foo
Date: Mon, 25 Jan 2021 12:33:15 +0000 [thread overview]
Message-ID: <bug-27238-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27238
Bug ID: 27238
Summary: [gcc-11] FAIL: gdb.go/package.exp: setting breakpoint
at package2.Foo
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: go
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With gcc-11 I run into:
...
(gdb) break package2.Foo^M
Function "package2.Foo" not defined.^M
Make breakpoint pending on future shared library load? (y or [n]) n^M
(gdb) FAIL: gdb.go/package.exp: setting breakpoint at package2.Foo
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-25 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:33 vries at gcc dot gnu.org [this message]
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
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@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).