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: Sat, 30 Dec 2023 22:34:56 +0000	[thread overview]
Message-ID: <bug-31152-4717-EGpQYZ4Ibl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31152-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to stephen douglas from comment #5)
> I have an unexplained change in my glibc
> source to increase the size of the constant(s) FD_SETSIZE is generated from
> so it copes.

Ok, but then I don't understand what you meant in comment #3.

Anyway -- could you summarize what changes you might need?

Or better yet, you could try to fix the problems and we could
see if the changes can be put in.

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

  parent reply	other threads:[~2023-12-30 22:34 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 ` [Bug gdb/31152] " tromey at sourceware dot org
2023-12-12 20:31 ` 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 [this message]
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-EGpQYZ4Ibl@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).