From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id C37CE3858D20 for ; Tue, 30 May 2023 18:07:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C37CE3858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1685470030; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=J2se5PTDUX4ESl9DyEJMJFeH0sXjuiCl4k2l/AQLp3g=; b=iie/CsAxr1jXqmwThPZc6vCG3rNcYncBv6f/ivhMpT2t3+M8DHkHrkK0Qyjwjtr7pM0/zM VdIZZlUCts+qlrOlfddEgfmxxTiRk2DdU7BxXENVePXqMQq1arh9NHkNzRGqpWkyTGrwWv ak7nnq0cCrrsvCYkC9sMkhgjCOTnE7g= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-657-OfKct-ekMqmEArR06VfzMg-1; Tue, 30 May 2023 14:07:06 -0400 X-MC-Unique: OfKct-ekMqmEArR06VfzMg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 532F429AA2C3; Tue, 30 May 2023 18:07:06 +0000 (UTC) Received: from greed.delorie.com (unknown [10.22.10.184]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2EDF840C6EC4; Tue, 30 May 2023 18:07:06 +0000 (UTC) Received: from greed.delorie.com.redhat.com (localhost [127.0.0.1]) by greed.delorie.com (8.15.2/8.15.2) with ESMTP id 34UI75Vw3823468; Tue, 30 May 2023 14:07:05 -0400 From: DJ Delorie To: Tom Tromey Cc: gdb-patches@sourceware.org, tdevries@suse.de, tom@tromey.com Subject: Re: [PATCH] [gdb/tui] Handle unicode chars in prompt In-Reply-To: <875y89wy48.fsf@tromey.com> Date: Tue, 30 May 2023 14:07:05 -0400 Message-ID: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Tom Tromey writes: > Using wchar functions in gdb is a pain; at least in the past, > gdb_wchar.h was written to support systems that don't support these at > all (DJGPP - not sure if that host even builds any more). The latest gdb build we have is 8.0 but I don't do the builds so I don't know what the status is for anything newer. As for wide chars, DJGPP has wchar_t and the required helper functions, and that's about all the support we added. I don't think I've ever seen DJGPP produce anything beyond ASCII or the usual DOS code pages.