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 gdb/30934] Stopping at a breakpoint takes minutes if a source file has long lines
Date: Tue, 03 Oct 2023 09:23:50 +0000	[thread overview]
Message-ID: <bug-30934-4717-TG5WDTTGCV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30934-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #5)
> So you can use as workaround:
> - build with --disable-source-highlight 

I just found that the same effect can be achieved by "maintenance set
gnu-source-highlight enabled off", so there's no need to rebuild.

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

  parent reply	other threads:[~2023-10-03  9:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 18:57 [Bug gdb/30934] New: " hi-angel at yandex dot ru
2023-10-02 22:54 ` [Bug gdb/30934] " tromey at sourceware dot org
2023-10-03  4:08 ` hi-angel at yandex dot ru
2023-10-03  4:15 ` hi-angel at yandex dot ru
2023-10-03  8:30 ` vries at gcc dot gnu.org
2023-10-03  8:49 ` vries at gcc dot gnu.org
2023-10-03  9:21 ` vries at gcc dot gnu.org
2023-10-03  9:23 ` vries at gcc dot gnu.org [this message]
2023-10-03 16:34 ` tromey at sourceware dot org
2023-10-03 21:07 ` vries at gcc dot gnu.org
2023-10-03 21:25 ` vries at gcc dot gnu.org
2023-10-05  6:35 ` vries at gcc dot gnu.org
2023-10-10 11:12 ` vries at gcc dot gnu.org
2023-10-11  7:28 ` vries at gcc dot gnu.org
2023-10-11 12:06 ` [Bug cli/30934] " vries at gcc dot gnu.org
2023-10-11 13:44 ` vries at gcc dot gnu.org
2023-10-11 17:10 ` hi-angel at yandex dot ru
2023-10-11 17:43 ` vries at gcc dot gnu.org
2023-10-12  9: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-30934-4717-TG5WDTTGCV@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).