Message ID | 1459851290-13123-1-git-send-email-catalin.udma@freescale.com |
---|---|
State | New, archived |
Headers |
Received: (qmail 91015 invoked by alias); 5 Apr 2016 10:16:17 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <gdb-patches.sourceware.org> List-Unsubscribe: <mailto:gdb-patches-unsubscribe-##L=##H@sourceware.org> List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org> List-Archive: <http://sourceware.org/ml/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs> Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 90999 invoked by uid 89); 5 Apr 2016 10:16:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=HReceived-SPF:helo, H*r:8.14.3, HReceived-SPF:receiver, HAuthentication-Results:fail X-HELO: na01-bl2-obe.outbound.protection.outlook.com Received: from mail-bl2on0134.outbound.protection.outlook.com (HELO na01-bl2-obe.outbound.protection.outlook.com) (65.55.169.134) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA256 encrypted) ESMTPS; Tue, 05 Apr 2016 10:16:06 +0000 Received: from BY2PR03CA044.namprd03.prod.outlook.com (10.141.249.17) by BY1PR03MB1514.namprd03.prod.outlook.com (10.162.210.148) with Microsoft SMTP Server (TLS) id 15.1.447.15; Tue, 5 Apr 2016 10:16:02 +0000 Received: from BN1AFFO11FD044.protection.gbl (2a01:111:f400:7c10::133) by BY2PR03CA044.outlook.office365.com (2a01:111:e400:2c5d::17) with Microsoft SMTP Server (TLS) id 15.1.447.15 via Frontend Transport; Tue, 5 Apr 2016 10:16:03 +0000 Authentication-Results: spf=fail (sender IP is 192.88.168.50) smtp.mailfrom=freescale.com; freescale.mail.onmicrosoft.com; dkim=none (message not signed) header.d=none; freescale.mail.onmicrosoft.com; dmarc=none action=none header.from=freescale.com; Received-SPF: Fail (protection.outlook.com: domain of freescale.com does not designate 192.88.168.50 as permitted sender) receiver=protection.outlook.com; client-ip=192.88.168.50; helo=tx30smr01.am.freescale.net; Received: from tx30smr01.am.freescale.net (192.88.168.50) by BN1AFFO11FD044.mail.protection.outlook.com (10.58.52.191) with Microsoft SMTP Server (TLS) id 15.1.453.6 via Frontend Transport; Tue, 5 Apr 2016 10:16:02 +0000 Received: from udp122517uds.ea.freescale.net (udp122517uds.ea.freescale.net [10.171.74.106]) by tx30smr01.am.freescale.net (8.14.3/8.14.0) with ESMTP id u35AG0gV020216; Tue, 5 Apr 2016 03:16:01 -0700 From: Catalin Udma <catalin.udma@freescale.com> To: <gdb-patches@sourceware.org> CC: Catalin Udma <catalin.udma@freescale.com> Subject: [PATCH] testsuite: Update py-mi-objfile to expect console format print Date: Tue, 5 Apr 2016 13:14:50 +0300 Message-ID: <1459851290-13123-1-git-send-email-catalin.udma@freescale.com> X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:192.88.168.50; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(2980300002)(1109001)(1110001)(339900001)(3190300001)(199003)(377424004)(189002)(2351001)(33646002)(85426001)(575784001)(106466001)(47776003)(450100001)(1096002)(87936001)(5008740100001)(77096005)(4001430100002)(36756003)(1220700001)(81166005)(229853001)(92566002)(50226001)(2906002)(189998001)(4326007)(107886002)(586003)(110136002)(50466002)(104016004)(48376002)(86362001)(19580395003)(19580405001)(5003940100001)(230783001)(6806005)(50986999); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR03MB1514; H:tx30smr01.am.freescale.net; FPR:; SPF:Fail; MLV:sfv; A:1; MX:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD044; 1:28jwwn3JJKQ2emdZ0kFOP5I7hHUln2f84E7kpj5qp1+P7CEdnv29GMGSNEt5wSkLM0MMzC9v60MsrCnxD8Hp7RQVlWA9wLA460EjIVq0YqQ3lGEQuS0uIsZxjSwv3kHmCCRFPEF9tUo8JtRZCi0DQFeASzOgDP/rrse6dbjSX6hlhSJ6wDFB74W3QVckZ9DykU8vgicvu8XJaETIpSwzDfwxUFV8/Iaj6+QHFkk4/uRW/Ec3n8DoHqyb+TZ9PkPwpR1px1L3tz4b+2vLCAD2A93WUbTS4BUVDA0gJvlE5cRtTU4VfjylLuv9/+S74JBrEw3VxebkiPV8tkxKQwTJd2ZK35SxnpRDTRwCytvQwC+YIrvTsbnnEeJRsU+05PZp8QUgoepUBc2Y5iKwRE+I9Mw2ejwKRe/DauVw/+KuAG4xB2bGkMylVlDFz65REu5gdrga7jDDh/7xXqQC8f1Fd7x4lgSDZDkFxGQ9YZf3pP9RDPEqhC9hitv+tuh5FYLpmJMa1jvyOePiDsoFaJeG7CA63sXJCraBMmCjjZ5ACPRT8FgGlgkk43e721Mck/APg9k82zm6cn9ii4U2qbqDjg+/FMb6AO352rBgGRhjlLo= MIME-Version: 1.0 Content-Type: text/plain X-MS-Office365-Filtering-Correlation-Id: ba3ab65e-7ebb-4096-156d-08d35d3b4a82 X-Microsoft-Exchange-Diagnostics: 1; BY1PR03MB1514; 2:GP7FWS0+dA8d8dStSPG9DEEkigPlmtUSLSfyn/LCyxLzZWgSyIU3mYUJdloPnh7ZBi+7kDCQJx8YqzyzcxdiAZ2KY8QnS3dwn/Skq6mMUbTPRL5lAOtScPJlVOuSBO6Xq1JbsgNEU03udoHLFf3pFph2gbLT4LH3FsZQmABHHvXDXJWO4uUow2fjSD069/Rm; 3:ZbDmxuscg2wYGiTjtnUmMkMoiwvJiXb7sq+Mgmer4X1MLHAhn0c3FY1bdxZ23LMlOkqFOIP4SQJGMeoqWw3vBjcmdDrxJOJR5R8dxajiN9OhZoc51H8W+3hr8sLURJHX2+1IWZNFbygLrk4bbbwoaCJZ8C4VJAmjE5yXduSBeoP0ySMBj8WRGtCdFUkaIB3xFA5u/JvdmtLLt3BfftiMCvhnFyO5gQn7dYAZ1LzanxM=; 25:EL0FLTaIjvfSKW1KdI8+E1FzhA2tKWXbgZsCU9WSs5OzTxizNwkeQ5aKwfA+Q/v7V/F0eVjxuleoeUC6RyiGC+4deHgdCekutthoI431dnjwP8VQoF3Q1hqKXj2SD5RV9gaS84FZzevvDdOvWkYUnUeE4XSy5Genw11WDNitnGYuGMkG19YN5tHLqLc4z/cGBdOAA56hmKGzK119T/3v30se715X8C3RjgoLGTJMl+/fCclUnRQEVxMfGUbRQ2pjvfTGVpGj3nvNGD01M7BZVdmvnjLWk7QVe9SMZ0QeHrfxjPNHQdv2jV2rGa2z7HD6CwgSn+zYaLjYFEKNIp05TXRAlr83NqGUiEJaQmPqOio= X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR03MB1514; X-Microsoft-Exchange-Diagnostics: 1; BY1PR03MB1514; 20:xuwndww35ab4sm6AnfE0xwJntPNR/ZCtsYYFrvH/KhvFCIqPtm5XY5TCGnrwa3tMZ//FQl6rm0CXBG2Pc0tcQGn46OFrv1d4XJnRzIpK4qndll/kXTOr0IqzO/WLqwabMaBcaOQ1PivAL0x0PVharg33YSenasf2P54emFX13FkttguSkeJe6MhnidMh+QiROuxG0/FC4oA1hPdqv+C+MzpuNxhs/jV4dmZous5JdQexxvyc+8TqRUm3gs9pI78y/fAERcUdHeLnFMt/ztcuf5Y9Jj8sM2UlXW3YOC39vFr9PsuagZ90s0/N8Awspsg8fwFgue1aXD968UXHCv1yJPdw4MMZR7tFfa3/KyLS1NL8XajojVGpnK7/edyzbXFh1wZzsFpjGWQzSyMf7lYWd1IhrrCVCypjDITmpqklxLX3k0bRBMw5sWRIC7ViRQeK; 4:TVyBT0Or3YVkwpsYsA9W+5f7/SttgWZxr66LG0QiY9a05/3IDJUwwxYh6VOAuIUMtbpf3QvQfzs6NcSVYLgKzIgEHuo9iP9tXayWWYcNTcu4WZrkc3qd1N0vYXFhgbL5uqP7j3JiTd5103tueR3d0ugeGJyeBlxkGYdInMUWjFvev4TnesAo2xHXi5X1qlJRCN6KSZ9NUGxCiOl2jwBCkBceMgF7wyUTjelC21tRVHNGoEg4rcL7B6zMmdvptGqDg4mQWnMYN60pqyUatGWNvccbJjG3ifDc+8c4+gWEusz4JnDV0lCBOHh/Qu0aNf25llOE5qwnRjc4j/J3d46BZHTZsJrz9Efy9sdREmg/4jCfgWlX2STPvoa0ge93NNrKGC/ll9eQDFMn76o1O+Fi/JAM0xY8d8MfTGFB3dThiwpLoFe8jtIwyXEMILN1Fnf3Qi45APXwbif13zRO/WQ0sg== X-Microsoft-Antispam-PRVS: <BY1PR03MB1514E99CED0302A1FB783E79969E0@BY1PR03MB1514.namprd03.prod.outlook.com> X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(13023025)(13015025)(13018025)(13017025)(13024025)(8121501046)(5005006)(3002001)(10201501046); SRVR:BY1PR03MB1514; BCL:0; PCL:0; RULEID:; SRVR:BY1PR03MB1514; X-Forefront-PRVS: 0903DD1D85 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY1PR03MB1514; 23:rIGHSwR+uisa0zQ8/v/Z25ZolNSOnSaiN4ftvqqYm?= =?us-ascii?Q?pGr7dS/ILFy5H4iZnNs5FFMnBPpBOuUOz9a1hECQgcLOkFk7FtkTw5RfKNXF?= =?us-ascii?Q?uwUx+gYVIo1k+7b0f/gmCujRLMmQby5FO9DtMfZ5N69ODZSUXxgEgWDqB+i6?= =?us-ascii?Q?19lyi8MbhXRHwknUWoLqkhCxZKFzcNyiP837Yt83bD0H/K3Td7Y4YqHMfDeH?= =?us-ascii?Q?oTdTZgC2tyIzvlYDLlGYYwwm1GNCHOjNpFv93NACDWSKZhvBr3lO2C3pLrW8?= =?us-ascii?Q?9l5L9OrMIHh4dmKMCkiMg6jvUuKTq3KePs3WQKMk9kQfv0GKzb2NPellOxKw?= =?us-ascii?Q?WzjtCb5KldZNKoUTqjvTBJ4V0tW9QabT5Dk2+biYmDKtsOCgdjOrjocn3H7Q?= =?us-ascii?Q?Vw4btuZ0SXkWL9bXYfSh7a5s85UzDWxWuull6Wdw9mn0jUh5qrt+oAsPVbKq?= =?us-ascii?Q?jt2QJ9mYmNpKwLzpj97LG6YFc2Tmm6Hr8x7pHFNFpYkszxeZZBpvn92eJwOL?= =?us-ascii?Q?5KCcPqjb4jubYUmD9wV276my8BbEqYsUrnMCzCpEDFBjpiD+/SPXVrNJAzM6?= =?us-ascii?Q?TeKW0VptrHRmB8S+Y6mD4E3MyxPUbEDziusb2ADrONEeL5f+Os1A8e3mT/Ys?= =?us-ascii?Q?e6oEx3nAzZMC/a/bXbjTje3sfe78NCDgb1YjcP9ttOGUCSWKGqA7E4QT+Dmf?= =?us-ascii?Q?mgmOjrqC9U8bU9mgH7kuFPRfrnDZlwHWOmxF12W8ImxWQpqC+spQOUwkiJXm?= =?us-ascii?Q?BpKedvpqeDYVK4GgqTqwuuu+2fsKKD8ROv8sBqPCblrPjvpl8j4HFx5myJ1y?= =?us-ascii?Q?bUaFfNO9LQAvhf8h+niS3FGmFkx94rb/2Uw6KiOGfZcPvA2N/wARJ9DARot9?= =?us-ascii?Q?FShZS1f43zs29OmNDDPI17KfKArYJBepYNSQR1X+NZhQVwhHABe0vaebEA8X?= =?us-ascii?Q?A12PZVqxRBxvOObA58RI6WaZlsfg589TCi3qtxvMfHoAveMPoUvHuGnub8v2?= =?us-ascii?Q?5sEMbcKoKl/HP9yWRv4l2eRJbv4LpxM54gtn1DDCjIxEM1JlIHA3CtUZlmVR?= =?us-ascii?Q?c0DnLq/n6sZRmFs236qIpXOtG9ygTtFN5ZwWA3zwhfuT4bu5yzZhlu2V+TQr?= =?us-ascii?Q?dnJymXq0sQ=3D?= X-Microsoft-Exchange-Diagnostics: 1; BY1PR03MB1514; 5:drxIDsbYaMZeG/+vNj3ml7qxlzjoaOq6K+zp5ZAggaDcABFSiwnKp87Wd2fJzQijoELPBBMWGiM4kOQGsY76rPG2iaZAoYLLRBoAzJyp/tAZMggz/sKZYCkUteVIZ1Td3ZwlA5diEsLhe8KcdBLhXg==; 24:2/D2qvXeygJBLUKONbC4izXjGltHsZhTSnv1x9bJvNl0qVlto22dAQNH2yL2ZRqyRrdiwoEn4EgOa7rdj7l9446lpGo62ijayqIBK/Lq3j0= X-OriginatorOrg: freescale.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Apr 2016 10:16:02.2304 (UTC) X-MS-Exchange-CrossTenant-Id: 710a03f5-10f6-4d38-9ff4-a80b81da590d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=710a03f5-10f6-4d38-9ff4-a80b81da590d; Ip=[192.88.168.50]; Helo=[tx30smr01.am.freescale.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR03MB1514 |
Commit Message
Catalin Udma
April 5, 2016, 10:14 a.m. UTC
Starting with this commit:
commit e7ea3ec7c623be0b9be1eaf4929794652a84be11
Author: Catalin Udma <catalin.udma@freescale.com>
Date: Mon Feb 29 16:16:19 2016 +0200
python: Use console format for output of gdb.execute command
the python script would use console format for gdb.execute output.
This patch fixes py-mi-objfile to expect the console format when is
checking for gdb.execute printing.
gdb/testsuite/ChangeLog:
2016-04-05 Catalin Udma <catalin.udma@freescale.com>
* gdb.python/py-mi-objfile-gdb.py: Use "list main" command
* gdb.python/py-mi-objfile-gdb.exp: Match "list main"
output in console format.
Signed-off-by: Catalin Udma <catalin.udma@freescale.com>
---
gdb/testsuite/gdb.python/py-mi-objfile-gdb.py | 2 +-
gdb/testsuite/gdb.python/py-mi-objfile.exp | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
Comments
On 04/05/2016 11:14 AM, Catalin Udma wrote: > --- a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py > +++ b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py > @@ -24,4 +24,4 @@ import gdb > gdb.execute("set width 101", to_string=True) > # And finally a command that will use the original MI stream, which in a > # buggy gdb will use just-freed data. > -gdb.execute("list") > +gdb.execute("list main") Do the comments in the test still make sense? From the comment, sounds like the test might no longer be covering what it intended? I.e. do we "use the original MI stream" ? Thanks, Pedro Alves
> On 04/05/2016 11:14 AM, Catalin Udma wrote: > > --- a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py > > +++ b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py > > @@ -24,4 +24,4 @@ import gdb > > gdb.execute("set width 101", to_string=True) > > # And finally a command that will use the original MI stream, which in a > > # buggy gdb will use just-freed data. > > -gdb.execute("list") > > +gdb.execute("list main") > > Do the comments in the test still make sense? > From the comment, sounds like the test might no longer be covering > what it intended? I.e. do we "use the original MI stream" ? > > Thanks, > Pedro Alves [Catalin Udma] Indeed, the original crash is no longer reproducible: I manually reverted the fixes for that crash (gdb/cli/cli-logging.c, gdb/mi/mi-out.c) and the crash is not reproducible anymore when running py-mi-objfile.exp. It reproduces if I revert also this patch " python: Use console format for output of gdb.execute command" Updating the comments would be enough and let the test validate the same scenario? "+# And finally a command that will use the console stream without redirection" ?
On 04/05/2016 12:45 PM, Catalin-Dan Udma wrote: >> On 04/05/2016 11:14 AM, Catalin Udma wrote: >>> --- a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py >>> +++ b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py >>> @@ -24,4 +24,4 @@ import gdb >>> gdb.execute("set width 101", to_string=True) >>> # And finally a command that will use the original MI stream, which in a >>> # buggy gdb will use just-freed data. >>> -gdb.execute("list") >>> +gdb.execute("list main") >> >> Do the comments in the test still make sense? >> From the comment, sounds like the test might no longer be covering >> what it intended? I.e. do we "use the original MI stream" ? >> >> Thanks, >> Pedro Alves > > [Catalin Udma] Indeed, the original crash is no longer reproducible: I manually reverted the fixes > for that crash (gdb/cli/cli-logging.c, gdb/mi/mi-out.c) and the crash is not reproducible anymore > when running py-mi-objfile.exp. > It reproduces if I revert also this patch " python: Use console format for output of gdb.execute command" > > Updating the comments would be enough and let the test validate the same scenario? I think it's good to keep validating the same scenario. Though maybe there's something else we could add that uses the MI stream, that'd also expose the crash? Maybe gdb.execute ("interpreter-exec mi \"-gdb-show width\"") would work? > "+# And finally a command that will use the console stream without redirection" ? Thanks, Pedro Alves
> > On 04/05/2016 12:45 PM, Catalin-Dan Udma wrote: > >> On 04/05/2016 11:14 AM, Catalin Udma wrote: > >>> --- a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py > >>> +++ b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py > >>> @@ -24,4 +24,4 @@ import gdb > >>> gdb.execute("set width 101", to_string=True) > >>> # And finally a command that will use the original MI stream, which in a > >>> # buggy gdb will use just-freed data. > >>> -gdb.execute("list") > >>> +gdb.execute("list main") > >> > >> Do the comments in the test still make sense? > >> From the comment, sounds like the test might no longer be covering > >> what it intended? I.e. do we "use the original MI stream" ? > >> > >> Thanks, > >> Pedro Alves > > > > [Catalin Udma] Indeed, the original crash is no longer reproducible: I manually > reverted the fixes > > for that crash (gdb/cli/cli-logging.c, gdb/mi/mi-out.c) and the crash is not > reproducible anymore > > when running py-mi-objfile.exp. > > It reproduces if I revert also this patch " python: Use console format for > output of gdb.execute command" > > > > Updating the comments would be enough and let the test validate the same > scenario? > > I think it's good to keep validating the same scenario. > > Though maybe there's something else we could add that uses the > MI stream, that'd also expose the crash? Maybe > > gdb.execute ("interpreter-exec mi \"-gdb-show width\"") > > would work? > > > "+# And finally a command that will use the console stream without > redirection" ? > > Thanks, > Pedro Alves [Catalin Udma] gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True) would crash the gdb with or without any of the patches in discussion. (MI patch for crash redirection, and use console for python gdb.execute) I propose to log this new bug, and for now just update the comments in this test. When the new bug would be fixed, the this test would be updated with the new scenario.
On 04/05/2016 02:08 PM, Catalin-Dan Udma wrote: > [Catalin Udma] > gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True) > would crash the gdb with or without any of the patches in discussion. > (MI patch for crash redirection, and use console for python gdb.execute) Bah... > > I propose to log this new bug, and for now just update the comments in this test. > When the new bug would be fixed, the this test would be updated with the new > scenario. OK. Thanks, Pedro Alves
On 04/05/2016 02:11 PM, Pedro Alves wrote: > On 04/05/2016 02:08 PM, Catalin-Dan Udma wrote: > >> [Catalin Udma] >> gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True) >> would crash the gdb with or without any of the patches in discussion. >> (MI patch for crash redirection, and use console for python gdb.execute) > > Bah... Looking again, note I suggested: gdb.execute ("interpreter-exec mi \"-gdb-show width\"") not: gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True) TBC, does the former also likewise crash with or without patches? Thanks, Pedro Alves
> On 04/05/2016 02:11 PM, Pedro Alves wrote: > > On 04/05/2016 02:08 PM, Catalin-Dan Udma wrote: > > > >> [Catalin Udma] > >> gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True) > >> would crash the gdb with or without any of the patches in discussion. > >> (MI patch for crash redirection, and use console for python gdb.execute) > > > > Bah... > > Looking again, note I suggested: > > gdb.execute ("interpreter-exec mi \"-gdb-show width\"") > > not: > > gdb.execute ("interpreter-exec mi \"-gdb-show width\"", to_string = True) > > TBC, does the former also likewise crash with or without patches? > > Thanks, > Pedro Alves The former gdb.execute ("interpreter-exec mi \"-gdb-show width\"") does not crash the gdb in any combination of the two patches in discussion. Regards, Catalin
On 04/05/2016 02:36 PM, Catalin-Dan Udma wrote: > The former gdb.execute ("interpreter-exec mi \"-gdb-show width\"") does not crash the gdb > in any combination of the two patches in discussion. Thanks. Let's indeed just update the comments then. Thanks, Pedro Alves
diff --git a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py index 492d71c..ff1d983 100644 --- a/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py +++ b/gdb/testsuite/gdb.python/py-mi-objfile-gdb.py @@ -24,4 +24,4 @@ import gdb gdb.execute("set width 101", to_string=True) # And finally a command that will use the original MI stream, which in a # buggy gdb will use just-freed data. -gdb.execute("list") +gdb.execute("list main") diff --git a/gdb/testsuite/gdb.python/py-mi-objfile.exp b/gdb/testsuite/gdb.python/py-mi-objfile.exp index 073e4d9..bfa43a2 100644 --- a/gdb/testsuite/gdb.python/py-mi-objfile.exp +++ b/gdb/testsuite/gdb.python/py-mi-objfile.exp @@ -53,5 +53,6 @@ if [is_remote host] { # PR 18833. This will cause an unpatched gdb to crash. mi_gdb_test "-file-exec-and-symbols ${filename}" \ - ".*\\^done,line=.*${srcfile}\"" \ + ".*main \\(.*void\\).*\ + return 0;.*\\^done" \ "file-exec-and-symbols operation"