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 build/30488] New: [gdb/build] Code guarded with HANDLE_MULTIBYTE is dead
Date: Thu, 25 May 2023 11:48:30 +0000	[thread overview]
Message-ID: <bug-30488-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30488
           Summary: [gdb/build] Code guarded with HANDLE_MULTIBYTE is dead
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I noticed a use of HANDLE_MULTIBYTE in gdb:
...
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
./gdb/completer.c:#if defined (HANDLE_MULTIBYTE)
...
while the macro seems to be defined in readline:
...
./readline/readline/rlmbutil.h:#    define HANDLE_MULTIBYTE      1
...

I first looked at system readline.

It seems that the library is build with multi-byte support:
...
$ nm -D /lib64/libreadline.so.7.0 | grep mbrtowc
                 U mbrtowc
...

But in the exported header files the macro is not set in any way:
...
$ find /usr/include/readline/ -type f | xargs grep HANDLE_MULTIBYTE
$
...

I then tried without system readline, and build gdb with this patch:
...
diff --git a/gdb/completer.c b/gdb/completer.c
index 91a29daee36..62bd87cc939 100644
--- a/gdb/completer.c
+++ b/gdb/completer.c
@@ -2435,6 +2435,7 @@ get_max_completions_reached_message (void)
 #undef VISIBLE_STATS

 #if defined (HANDLE_MULTIBYTE)
+#error bla
 #define MB_INVALIDCH(x) ((x) == (size_t)-1 || (x) == (size_t)-2)
 #define MB_NULLWCH(x)   ((x) == 0)
 #endif
...
which build fine.

So, in both cases HANDLE_MULTIBYTE is undefined, and the code guarded by it is
currently dead.

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

             reply	other threads:[~2023-05-25 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 11:48 vries at gcc dot gnu.org [this message]
2023-05-25 11:49 ` [Bug build/30488] " vries at gcc dot gnu.org
2023-08-28 13:50 ` tromey at sourceware dot org
2023-08-28 14:23 ` vries at gcc dot gnu.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-30488-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).