public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "petedietl at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26081] New: Function names in source window are always black source style turned on
Date: Thu, 04 Jun 2020 00:02:07 +0000	[thread overview]
Message-ID: <bug-26081-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26081
           Summary: Function names in source window are always black
                    source style turned on
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: petedietl at gmail dot com
  Target Milestone: ---

Created attachment 12586
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12586&action=edit
GDB window

I can't see the names of the functions in the TUI src window since they are
colored black. But the color looks correct in the asm window. Changing the
function style foreground color does change the function names in the asm
window but still no changes in the src window.

I didn't have these issues when I was using an older v10 from source. Though I
don't recall exactly which version I used. 

The color scheme looks weird in general now. I have attached a screen shot. 

Environment Details:
Linux pdietl-dev 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

GNU gdb (GDB) 10.0.50.20200603-git

This GDB was configured as follows:
   configure --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
             --with-auto-load-dir=$debugdir:$datadir/auto-load
             --with-auto-load-safe-path=$debugdir:$datadir/auto-load
             --with-expat
             --with-gdb-datadir=/usr/local/share/gdb (relocatable)
             --with-jit-reader-dir=/usr/local/lib/gdb (relocatable)
             --without-libunwind-ia64
             --without-lzma
             --without-babeltrace
             --without-intel-pt
             --with-mpfr
             --with-xxhash
             --with-python=/usr
             --without-debuginfod
             --without-guile
             --enable-source-highlight
             --with-separate-debug-dir=/usr/local/lib/debug (relocatable)

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

             reply	other threads:[~2020-06-04  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  0:02 petedietl at gmail dot com [this message]
2020-06-04 21:19 ` [Bug gdb/26081] " ssbssa at sourceware dot org
2020-06-05  2:08 ` petedietl at gmail dot com
2020-06-05  2:08 ` petedietl at gmail dot com
2020-06-07 16:54 ` tromey at sourceware dot org
2020-06-07 17:01 ` petedietl at gmail dot com
2020-06-07 17:49 ` tromey at sourceware dot org
2020-06-08 15:19 ` petedietl at gmail dot com
2020-06-11  2:39 ` tromey at sourceware dot org
2020-08-09 20:48 ` [Bug tui/26081] " 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:
  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-26081-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).