public inbox for
help / color / mirror / Atom feed
From: " at gmail dot com" <>
Subject: [Bug cli/30557] Exception after pressing tab to autocomplete in location_completer gdb/completer.c:766
Date: Mon, 03 Jul 2023 16:15:49 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

meator < at gmail dot com> changed:

           What    |Removed                     |Added
                 CC|                            | at gmail dot com

--- Comment #1 from meator < at gmail dot com> ---
I have encountered the same issue. I am unfortunately not familiar with GDB
internals but I will try to provide steps to reproduce this issue.

I am running gdb 13.2 (which is higher than the version marked in this bug

A visual showcase of this bug can be found here:

I have created a Dockerfile which can reproduce the issue. It can be found

The file is uploaded via Google Drive. I can reupload this file somewhere else
if needed.

The archive contains two things: the Dockerfile and copy of my unfinished
project related to matrixes. The project is largely unrelated to the bug but I
was able to trigger it when creating a breakpoint in one of the classes
contained in the project.

You can look at the Dockerfile to reproduce the issue manually.

My backtraces are similar to zwelf's, but it should be noted that gdb initially
fails with this error message:

terminate called after throwing an instance of 'std::length_error'
  what():  basic_string::_M_replace

My backtraces are here:

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

  reply	other threads:[~2023-07-03 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 18:33 [Bug cli/30557] New: " zwelf at strct dot cc
2023-07-03 16:15 ` at gmail dot com [this message]
2023-07-03 18:33 ` [Bug cli/30557] " tromey at sourceware dot org
2023-08-28 14:57 ` manas18244 at iiitd dot
2023-09-20 10:53 ` hi at alyssa dot is
2023-09-21  1:14 ` tromey at sourceware 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).