From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0EB7E3858C54; Tue, 28 Nov 2023 19:27:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0EB7E3858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1701199623; bh=56Q9PQv8Wq/u/MgQu9XooakGHBfGw3URZIOvkh3gXmE=; h=From:To:Subject:Date:From; b=eysAbegQEQQa1KU2TCgBOwe+RLngUzwzhQNzn0Y5pmPgyi8HzUA3kt9mVx5tRy5QK zKPURGJgUMkIsHdwY2QVLLYWF+IQnMzu1Ys67pHB6hQ6q3aLO7hatkL0b+6eaC731v /PqzV9FYOKPy4wfj39306uQIS3ZeGxoZDQM7+Ubg= From: "simark at simark dot ca" To: gdb-prs@sourceware.org Subject: [Bug gdb/31093] New: Random failures in gdb.gdb/index-file.exp (too much memory?) Date: Tue, 28 Nov 2023 19:27:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simark at simark dot ca X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31093 Bug ID: 31093 Summary: Random failures in gdb.gdb/index-file.exp (too much memory?) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simark at simark dot ca Target Milestone: --- On my CI, I've seen twice failures in gdb.gdb/index-file.exp. I did not fi= gure out the reason, and have not been able to reproduce locally. ~~~ Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for targ= et. Using /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/src/binutils-gdb/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file. Running /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/src/binutils-gdb/gdb/testsuite/gdb.gdb/index-file.exp ... Downloading on host to /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/outputs/gdb.gdb/index-f= ile/xgdb: /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/../../gdb/gdb builtin_spawn /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/../../gdb/gdb -nw -nx -q -iex set height 0 -iex set width 0 -data-directory /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/data-directory (gdb) set height 0 (gdb) set width 0 (gdb) dir Reinitialize source path to empty? (y or n) y Source directories searched: $cdir:$cwd (gdb) dir /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/src/binutils-gdb/gdb/testsuite/gdb.gdb Source directories searched: /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/src/binutils-gdb/gdb/testsuite/gdb.gdb:$cdir:$cwd (gdb) kill The program is not being run. (gdb) file /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/outputs/gdb.gdb/index-f= ile/xgdb Reading symbols from /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/outputs/gdb.gdb/index-f= ile/xgdb... (gdb) maintenance show worker-threads The number of worker threads GDB can use is unlimited (currently 8). (gdb) Executing on host: mkdir -p /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/outputs/gdb.gdb/index-f= ile/index_1 (timeout =3D 300) builtin_spawn -ignore SIGHUP mkdir -p /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/outputs/gdb.gdb/index-f= ile/index_1 save gdb-index /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/deb12-amd64= /target_board/unix/tmp/tmp.8a1kZQUJPh/gdb/testsuite/outputs/gdb.gdb/index-f= ile/index_1 ERROR: GDB process no longer exists GDB process exited with wait status 402279 exp6 0 0 CHILDKILLED SIGKILL {ki= ll signal} UNRESOLVED: gdb.gdb/index-file.exp: create gdb-index file ~~~ Notice that GDB gets killed with SIGKILL. dmesg shows that a process was killed by the Linux OOM killer at the exact time, so I'm pretty sure that t= his is what sent SIGKILL to the GDB process. My CI runs the testsuite in paral= lel, so that can explain the randomness, depending on what runs alongside that t= est, we might or might not exhaust the memory. Perhaps that's just the way it is and this operation needs to take a lot of memory, but it would be good to check if there is anything obvious that can= be done about it (like plugging a memory leak). --=20 You are receiving this mail because: You are on the CC list for the bug.=