public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug ada/12607] New: BINOP_EQUAL does not work with system debug info installed Date: Mon, 28 Mar 2011 10:31:00 -0000 [thread overview] Message-ID: <bug-12607-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=12607 Summary: BINOP_EQUAL does not work with system debug info installed Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: ada AssignedTo: unassigned@sourceware.org ReportedBy: jan.kratochvil@redhat.com Host: x86_64-fedora15-linux-gnu Target: x86_64-fedora15-linux-gnu debuginfo-install gcc gdb -nx gdb.ada/str_ref_cmp/foo GNU gdb (GDB) 7.2.50.20110327-cvs This GDB was configured as "x86_64-unknown-linux-gnu". (gdb) p "a"="a" $1 = true (gdb) start (gdb) p "a"="a" $2 = false It affects the same way: (gdb) print String_Var (1 .. 3) = "Hel" -$1 = true -(gdb) PASS: gdb.ada/str_ref_cmp.exp: print String_Var (1 .. 3) = "Hel" +$1 = false +(gdb) FAIL: gdb.ada/str_ref_cmp.exp: print String_Var (1 .. 3) = "Hel" BINOP_EQUAL operator with gcc debug info installed resolves to: ada__strings__maps__Oeq (Ada.Strings.Maps) as its type matches in ada_resolve_function. I do not understand the Ada scoping to fix it. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-03-27 7:58 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-28 10:31 jan.kratochvil at redhat dot com [this message] 2011-03-29 6:52 ` [Bug ada/12607] " jan.kratochvil at redhat dot com 2024-02-26 18:32 ` tromey at sourceware dot org 2024-02-27 11:14 ` vries at gcc dot gnu.org 2024-02-27 15:21 ` cvs-commit 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-12607-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: linkBe 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).