public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "josh.cottingham at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/31010] Evaluating "mixed-cased" fundamental types causes hangs/OOM due to full symtab expansion
Date: Wed, 05 Feb 2025 10:15:25 +0000	[thread overview]
Message-ID: <bug-31010-4717-dxh4hwFle9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31010-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Josh Cottingham <josh.cottingham at linaro dot org> ---
For simplicity, I have created a GDB test which you can use for validation if
you like:


# Copyright 1998-2025 Free Software Foundation, Inc.

# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program.  If not, see <http://www.gnu.org/licenses/>.

# This file was written by Joshua Cottingham (josh.cottingham@linaro.org)

# Used to catch regression where GDB would expand CU table when printing
# fundamental types that are in "mixed-case".

standard_testfile break.c break1.c

if {[prepare_for_testing "failed to prepare" $testfile \
         [list $srcfile $srcfile2] {debug nowarnings}]} {
    return -1
}

set readnow_p [readnow]

# The command we test here produce many lines of output; disable "press
# <return> to continue" prompts.
gdb_test_no_output "set height 0"

gdb_file_cmd ${binfile}

# Check no CU are currently read before starting the program
gdb_test "maint print statistics" \
    ".*Number of read CUs: 0.*" \
    "No CU are read at the start"

gdb_test "print INT" "" "printing uppercase fundamental type"

# Now check CUs have still not been read after printing
gdb_test "maint print statistics" \
    ".*Number of read CUs: 0.*" \
    "No CU are read after printing fundamental type"
``

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

  parent reply	other threads:[~2025-02-05 10:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 16:38 [Bug symtab/31010] New: " josh.cottingham at linaro dot org
2023-10-30 16:40 ` [Bug symtab/31010] " josh.cottingham at linaro dot org
2023-10-31  4:14 ` sam at gentoo dot org
2023-10-31 17:30 ` tromey at sourceware dot org
2023-11-30 17:15 ` tromey at sourceware dot org
2024-01-20  8:36 ` sam at gentoo dot org
2024-02-15 17:02 ` tromey at sourceware dot org
2025-02-04 15:38 ` josh.cottingham at linaro dot org
2025-02-05 10:15 ` josh.cottingham at linaro dot org [this message]
2025-02-20 22:23 ` tromey at sourceware dot org
2025-02-20 22:24 ` tromey at sourceware dot org
2025-02-21 16:27 ` tromey at sourceware dot org
2025-02-21 16:34 ` tromey at sourceware dot org
2025-02-22  0:40 ` tromey at sourceware dot org
2025-02-22 18:51 ` tromey at sourceware dot org
2025-03-08  0:15 ` cvs-commit at gcc dot gnu.org
2025-03-08  0:19 ` tromey at sourceware dot org
2025-03-08 18:18 ` sam at gentoo dot 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-31010-4717-dxh4hwFle9@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).