From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44173: 28.0.50; gdb-mi mangles strings with octal escapes Date: Fri, 23 Oct 2020 15:01:52 +0300 Message-ID: <837drhjglr.fsf@gnu.org> References: <2A87D378-9FB9-4FC7-951E-5BA9832051CF@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37799"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 44173@debbugs.gnu.org To: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 23 14:03:10 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVvmn-0009hf-98 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 23 Oct 2020 14:03:09 +0200 Original-Received: from localhost ([::1]:56588 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kVvmm-00053Z-Ca for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 23 Oct 2020 08:03:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33028) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kVvmg-00051Y-4y for bug-gnu-emacs@gnu.org; Fri, 23 Oct 2020 08:03:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44682) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kVvmf-00075r-Ri for bug-gnu-emacs@gnu.org; Fri, 23 Oct 2020 08:03:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kVvmf-0008F6-NN for bug-gnu-emacs@gnu.org; Fri, 23 Oct 2020 08:03:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 23 Oct 2020 12:03:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44173 X-GNU-PR-Package: emacs Original-Received: via spool by 44173-submit@debbugs.gnu.org id=B44173.160345453530783 (code B ref 44173); Fri, 23 Oct 2020 12:03:01 +0000 Original-Received: (at 44173) by debbugs.gnu.org; 23 Oct 2020 12:02:15 +0000 Original-Received: from localhost ([127.0.0.1]:56228 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kVvlv-00080D-AP for submit@debbugs.gnu.org; Fri, 23 Oct 2020 08:02:15 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:60876) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kVvlt-0007uc-40 for 44173@debbugs.gnu.org; Fri, 23 Oct 2020 08:02:14 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46486) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kVvln-0006xV-RW; Fri, 23 Oct 2020 08:02:07 -0400 Original-Received: from [176.228.60.248] (port=3103 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kVvlm-0002mF-Ur; Fri, 23 Oct 2020 08:02:07 -0400 In-Reply-To: <2A87D378-9FB9-4FC7-951E-5BA9832051CF@acm.org> (message from Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= on Fri, 23 Oct 2020 13:50:24 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:191365 Archived-At: > From: Mattias Engdegård > Date: Fri, 23 Oct 2020 13:50:24 +0200 > > While the bug could be 'solved' by adding yet another regexp hack to gdb-mi-decode or gdb-mi-jsonify-buffer, I suggest we write a GDB/MI parser in Lisp directly, ditching the gdb-mi-decode preprocessing and JSON form entirely, solving this and related bugs once and for all. Many transforms can then be done on the S-expression result after parsing, which should be more efficient and less error-prone. I'm okay with writing a GDB/MI parser, but I'm not sure I understand how would that help to solve this particular conundrum. AFAIR, there's a genuine ambiguity there regarding non-ASCII characters reported from GDB. Could you tell how will this be solved by a different parser? P.S. Btw: gdb-mi.el already has a BNF parser for GDB/MI.