public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/26170] New: gdb.base/testenv.exp loops on Linux/sparc64
Date: Thu, 25 Jun 2020 08:18:51 +0000	[thread overview]
Message-ID: <bug-26170-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26170
           Summary: gdb.base/testenv.exp loops on Linux/sparc64
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: ro at gcc dot gnu.org
  Target Milestone: ---
              Host: sparc64-unknown-linux-gnu
            Target: sparc64-unknown-linux-gnu
             Build: sparc64-unknown-linux-gnu

While testing current master on Linux/sparc64, the gdb.base/testenv.exp would
loop:

PASS: gdb.base/testenv.exp: test_inherit_env_var: test1: test passing
TEST_GDB_G
LOBAL to GDB
FAIL: gdb.base/testenv.exp: test_inherit_env_var: test1: TEST_GDB_GLOBAL, get
nu
m vars
FAIL: gdb.base/testenv.exp: test_inherit_env_var: test1: TEST_GDB_GLOBAL,
confir
med
FAIL: gdb.base/testenv.exp: test_inherit_env_var: test1: printf "var: %s\n",
env
p[0] ? envp[0] : ""
[...]
FAIL: gdb.base/testenv.exp: test_inherit_env_var: test1: printf "var: %s\n",
envp[4443985] ? envp[4443985] : ""

which I only noticed after those 4.4+ million iterations.

The failure mode is like this:
(gdb) run 
Starting program:
/home/ro/obj/gdb/master/dist/gdb/testsuite/outputs/gdb.base/testenv/testenv 
Program found 0 variables starting with TEST_GDB

Breakpoint 1, main (argc=<error reading variable: Cannot access memory at
address 0x884>, argv=<error reading variable: Cannot access memory at address
0x88c>, envp=<error reading variable: Cannot access memory at address 0x894>)
at /home/ro/src/gdb/master/dist/gdb/testsuite/gdb.base/testenv.c:42
42          return 0; /* set breakpoint here.  */
(gdb) print /d j
Cannot access memory at address 0x7fc
(gdb) FAIL: gdb.base/testenv.exp: test_set_unset_env: test1: no TEST_GDB vars,
get num vars
FAIL: gdb.base/testenv.exp: test_set_unset_env: test1: no TEST_GDB vars,
confirmed

[...]

printf "var: %s\n", envp[4443985] ? envp[4443985] : ""
Cannot access memory at address 0x894
(gdb) FAIL: gdb.base/testenv.exp: test_inherit_env_var: test1: printf "var:
%s\n", envp[4443985] ? envp[4443985] : ""

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

             reply	other threads:[~2020-06-25  8:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  8:18 ro at gcc dot gnu.org [this message]
2020-11-23 17:38 ` [Bug tdep/26170] " glaubitz at physik dot fu-berlin.de
2020-11-23 17:39 ` glaubitz at physik dot fu-berlin.de
2021-04-27 15:01 ` matorola at gmail 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-26170-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).