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 mi/29426] New: FAIL: gdb.mi/mi-var-invalidate.exp: linteger not anymore in scope due to binary changes (unexpected output)
Date: Thu, 28 Jul 2022 14:33:19 +0000	[thread overview]
Message-ID: <bug-29426-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29426
           Summary: FAIL: gdb.mi/mi-var-invalidate.exp: linteger not
                    anymore in scope due to binary changes (unexpected
                    output)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I'm running into:
...
FAIL: gdb.mi/mi-var-invalidate.exp: linteger not anymore in scope due to binary
changes (unexpected output)
FAIL: gdb.mi/mi-var-invalidate.exp: no type for invalid variable linteger (1)
(unexpected output)
...

In more detail:
...
PASS: gdb.mi/mi-var-invalidate.exp: set format variable float_simple
Expecting: ^(-var-update linteger[^M
]+)?(\^done,changelist=\[{name="linteger",in_scope="invalid",has_more="0"}\][^M
]+[(]gdb[)] ^M
[ ]*)
-var-update linteger^M
^done,changelist=[{name="linteger",in_scope="false",type_changed="false",has_more="0"}]^M
(gdb) ^M
FAIL: gdb.mi/mi-var-invalidate.exp: linteger not anymore in scope due to binary
changes (unexpected output)
...

Also I'm seeing these, and assuming they're related:
...
FAIL: gdb.mi/mi-var-invalidate-shlib.exp: separate_debuginfo=0: in new process:
global_var recreated (unexpected output)
FAIL: gdb.mi/mi-var-invalidate-shlib.exp: separate_debuginfo=1: in new process:
global_var recreated (unexpected output)
...

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

             reply	other threads:[~2022-07-28 14:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 14:33 vries at gcc dot gnu.org [this message]
2022-07-29  9:28 ` [Bug mi/29426] " lsix at lancelotsix dot com
2022-07-29 10:05 ` vries at gcc dot gnu.org
2022-07-29 10:31 ` vries at gcc dot gnu.org
2022-07-29 11:05 ` vries at gcc dot gnu.org
2022-07-29 12:28 ` vries at gcc dot gnu.org
2022-07-29 13:01 ` lsix at lancelotsix dot com
2022-07-29 13:46 ` vries at gcc dot gnu.org
2022-07-29 15:08 ` lsix at lancelotsix dot com
2022-07-29 16:25 ` vries at gcc dot gnu.org
2022-08-12 11:12 ` lsix at lancelotsix 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-29426-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).