From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) by sourceware.org (Postfix) with ESMTPS id EB90A3858C83 for ; Tue, 16 May 2023 16:25:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EB90A3858C83 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linaro.org Received: by mail-wr1-x42f.google.com with SMTP id ffacd0b85a97d-3062db220a3so9411733f8f.0 for ; Tue, 16 May 2023 09:25:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1684254299; x=1686846299; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=bmTxbnV5uDU9NOj0XFZHapimg9NDrYmZipippTyrUqA=; b=mymRuA39qpz64ZcNu5JSZYrcO0McmA6HNF8MsZs9VJgz8p9lQeiWBvnJ/w1aQbxeQP A1EbMWsdjt9nzCAU9l8iFzjG4IjXVXVcdDZqe5rt2gngS59tHb5cul3BVvrbxmXZDej6 61cW8RzLzTkVLyHSabS+FiIWyUCnJ3unYB+Q++FNhc3rf5CNsg3X7+5ZfeUtwVTpMolk bS5BdssX7cnMYjJk29qH0OBFMGQJIwhlyHLjRb7il2x6q/lig48zmfyyJjqGR5HV2fhj A1HKhq1R41+V1vBqKRRBE2OVTadwlLk8PxRig9ZXB7xvG4UiCMLVAtW6NFoKw9Inuakl j6iw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684254299; x=1686846299; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=bmTxbnV5uDU9NOj0XFZHapimg9NDrYmZipippTyrUqA=; b=L78mMRo99byTVBSNxGcAK8Ah1zvXL/ahxyt+2TrIuHZ6hdbO/ZCf+kYMqiX+Z5r6lb XOOGA0kkPTbwMdwu/ssNSoIDoEvI5DOf0xfQVJSkO+P89LJypoQD0Hvt7D7JIC6tXp6v fVJAXYC2NjV1UgFuvmnvXvDnR9byHxk0c13xrxpbaz1VCVW6StCfAgfY4jnc8byCsx07 jOHUW/NroXS0rE4rwxAcQX8JU0zC2t4gRBckkxYw7OVVZWBUnughKGwRvkMewzo+Jzeg jt2UVl/6Wh5oKth8VmnrhiMcyg3yBGV+EPZiofzS/T9PVCgnJhgXDYYsHgX5Ifq8DH8C lc4w== X-Gm-Message-State: AC+VfDxdRmYH1010U82vIzz1rrx1cv4ZMtwXeRbaPPzbJnpPwCFbYCm+ u8VZ2cMwFtR3LvqOIW6YXxZ8Dg== X-Google-Smtp-Source: ACHHUZ4yQoLNMzNN2SMosscYkGtwMl1H/BORae60DD3SbmhZv+3v3Nvro2Hq3R+n7JL/SaE4SbAeIg== X-Received: by 2002:adf:f1c5:0:b0:2f2:4db4:1f5b with SMTP id z5-20020adff1c5000000b002f24db41f5bmr26022323wro.29.1684254299608; Tue, 16 May 2023 09:24:59 -0700 (PDT) Received: from [10.32.33.60] ([130.43.161.185]) by smtp.gmail.com with ESMTPSA id t1-20020a5d5341000000b002ff2c39d072sm3112543wrv.104.2023.05.16.09.24.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 May 2023 09:24:59 -0700 (PDT) Message-ID: <30648a3b-221c-20ee-396a-727c5befcffc@linaro.org> Date: Tue, 16 May 2023 17:24:57 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH] gdb/mi: Fix printing of fortran strings in stack To: Tom Tromey , Richard Bunt via Gdb-patches References: <20230510102031.2125810-1-richard.bunt@linaro.org> <87ttwk5jds.fsf@tromey.com> <87wn1d2y4m.fsf@tromey.com> Content-Language: en-US From: Richard Bunt In-Reply-To: <87wn1d2y4m.fsf@tromey.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,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: On 12/05/2023 19:38, Tom Tromey wrote: >>>>>> "Richard" == Richard Bunt via Gdb-patches writes: > >>> I wonder if this can be fixed more directly after >>> 2fc3b8a4cb8439fc53975c4e70336d76e3ddc531 and its predecessors. >>> (Not that there's anything wrong with this patch.) >>> Tom > > Richard> Even better than that, it fixes the issue I was seeing. > > Nice. I wonder if we can remove the old fix then. I have confirmed that the fix applied to the cli-mode code path can be removed. I'll prepare a v2. > > Richard> If it is OK, I'd like to propose the test case for upstream as I > Richard> believe it covers a legitimate gap, even if there is no known bug > Richard> here. > > Yes, that would be great. Thank you. > > Tom Thanks, Rich.