public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31152] Formalise unintened functionality in version 9.1
Date: Tue, 12 Dec 2023 20:31:01 +0000	[thread overview]
Message-ID: <bug-31152-4717-B6RLrbIG6W@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31152-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
On Linux hosts, gdb invokes iconvlist to get the list of
possible charsets.  There's no API for this on Linux.

If you build gdb using GNU libiconv, there will be an API,
and gdb won't try to exec this.

However, you may need additional patching, depending on what
you're trying to do.  For example, on Linux gdb will fork
and then test various ptrace features on its child.  This
is done to detect kernel differences at runtime.

> only to have a segment trap because the ifdef path for linux used a pointer set up through the exec iconv path.

Not sure what's going on here but perhaps whatever you did
was incomplete.  Using libiconv definitely works, even on Linux,
I test this way frequently.  (I don't test the iconv-completely-absent
path.)

Anyway, your needs are relatively unusual.  I'd consider clean patches
to arrange a setup that works for you, but I felt you should know that
it's somewhat unlikely that anyone else will pick up this bug.

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

  reply	other threads:[~2023-12-12 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 18:16 [Bug gdb/31152] New: " chris_douglas_email at yahoo dot com
2023-12-12 20:31 ` tromey at sourceware dot org [this message]
2023-12-12 20:31 ` [Bug gdb/31152] " tromey at sourceware dot org
2023-12-27 19:22 ` chris_douglas_email at yahoo dot com
2023-12-28 16:44 ` tromey at sourceware dot org
2023-12-30 20:12 ` chris_douglas_email at yahoo dot com
2023-12-30 22:34 ` tromey at sourceware dot org
2023-12-31 20:32 ` chris_douglas_email at yahoo dot com
2024-01-14 16:45 ` chris_douglas_email at yahoo dot com

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-31152-4717-B6RLrbIG6W@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).