From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11olkn2092.outbound.protection.outlook.com [40.92.18.92]) by sourceware.org (Postfix) with ESMTPS id DC796385843B for ; Tue, 22 Feb 2022 21:30:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DC796385843B ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KFyCy/scqRvYI71SpY9sc/31zuDSlX25rSAxMfWviFAIh3kP3rEXBwWVwFzZFELnfi1fL/COkdPlelK/iN0mS6jXTl9txuPT1MU9cO1AdltQBydXlW3PkURvoE+DJws3TSwYxw7g4YDpveLg+8OEF912XD1vexm3Vz2aaOAmfjAFPUgpQzBHNfnnp817OW5XyxpMtLfyMAaP1TMnNFG8sSOtltaV2cBpkLZZyt0g+VNlzqTORa666j3cDfLeR+bwOeAW63Uo7bo5FK1yyykkvU7Q2CsbR2cKwIJOoE/GbIqOPVW86Nbywr/lIchkNbkU2F/W3fEMhzExAyONet6hZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Ofi0DufqBh2juwclmnS3NJtMdgVJEwvg4ZbPBuH00JM=; b=aSE221JhER+MG8ZPrEyT4NRxOvB8pYdl1R9PBQx2bo6mSwgfwq67Nf12hRmBF7o0KMOQBYCKD+wwFlDVV8i3s3AMz77YmZ28gtwkajT1v2X6nYUWox/t0Vxf5eeORIDYUweRp1LmcyReWfOofgCfV7z0dRuvETQE7VoIwH61SKfoDGrYppNL1k7fLNEPUmGW6Dfagm5Jg3kpG2cF5ucknWXqV5ZHlpkQzKBSOqtLokltDAJTdBJFr1keONznlgD9/5iBgWAXUIN0dxXVsxFphw+QCpdJSAKq+7o4mU+z1skHMjCcu7Adjg+b2XD6wmT6lEKDPfvfh/KQIQHq3lTicw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none Received: from DM8PR16MB4357.namprd16.prod.outlook.com (2603:10b6:8:30::8) by BN0PR16MB4416.namprd16.prod.outlook.com (2603:10b6:408:153::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4995.27; Tue, 22 Feb 2022 21:30:26 +0000 Received: from DM8PR16MB4357.namprd16.prod.outlook.com ([fe80::35db:ffe6:afb0:5bdb]) by DM8PR16MB4357.namprd16.prod.outlook.com ([fe80::35db:ffe6:afb0:5bdb%8]) with mapi id 15.20.4975.019; Tue, 22 Feb 2022 21:30:26 +0000 From: Edgar Mobile To: Ruslan Kabatsayev CC: "gdb@sourceware.org" Subject: Re: Does gdb initialize uninitialized variables? Thread-Topic: Does gdb initialize uninitialized variables? Thread-Index: AQHYJwd7Af9LNIxpwUy1j0yuon+OmqyeRFSAgAHUHMg= Date: Tue, 22 Feb 2022 21:30:26 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [nzQYrcSkIW54yUnKwP3kkUR2cYFrDw8g] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 2137a25b-352a-449d-f847-08d9f64a8ae3 x-ms-traffictypediagnostic: BN0PR16MB4416:EE_ x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: QiWThvtxTXUjVFt8QWJcvXHw1Sq3HkHcWVYgTufFQhB2DyD2UkHNJ6b8JBhxRGywOTWKpUG8DO0BnL7ZREPvJRucI9Nch7IaDI8ykbNlItC2vEyfDEgNqWlxQj2cEvK549kUvil2jb3Atj5I7kbjpgWpGV44aGTGP6BFlOqrmb0ro+YjFcn5NKXW8PIWOHmMTUuFw3BNK6od0AGFP7D4CqINfkCQ8JH5WLj+8jJQOMrH2boGraMi1PnK8BpyCUtaV4DyQORuiMyr1K71Q4zDZ/alMHgfSy0MPiBJLtZj+jEmrzlWBpaQzQZ6guLu0xg0/9srxVBM9xVJwqhy+EcSCvpNkNbQHIev8TgsU89iD4VfHRWUVT59LZl3ro8v8wQPPwuds2JxiYF+ND9K0cMY2oRYnGUCpZLz8J8AclAf6FukRMabUhxPIDV7eKKqKstX/Bxn4zZDE/lNNJ7VwQvXWbgJ2PsDfbNtwyhTVGNqyHHcy3wwu+A1pJgfsKRHS49PdZXCzs8hAGw7GwFGzWrbADq9SNpS5i5XywjESvNMjFGOiWFU6K3WE7ql1Vg344GNUgr++q+ji23xZY9ib5Yxgg== x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: O1mBohNIhyyIBz9UZLzCQKoDM5DBTGzQBKruc8KPsTVbDJuCe41CzbNQP5m6wmMr/AGgmJTtJCFtYVSyAHzxOBJjz62KypsHYsrR72PackbNCFk0p7zwsDJLfONBnRXWChhyulozNgKMOZX5VeVEj4nSnJ0P2sWu/XzAcAweTwmQd3RxKAxXYyAEqrvz00+aB6c64gHqS9+NI7gjpZnA8CRLchGMmBRtTF2bFNFAoZtdH7Ya8RprZLgbGR1udx0orNQH3iAlPoojX7QK4DRcNJ+q4FJUtsHsrskmAmii0QzkakeK5wpK1/OSxNUglOyp974mSqXlGaSBWHGOCNh5nQRAzrIPkxTFiJA0sb7+eJSwtZcaR6LeP12jhF5PLQJh8uW1vWf+aLYH1yi7kTA9vLiYh6oB+ANeEpv3APCX4aRIxDM5NZJXSE5gh4zDGVqXG0jl0wdkrRzbMBZZ/UyIiWQ4hHcu2rbhWdd99XW4b7k4yjrkKkvYFoLomwnFFvasXXO4IKguznzh/y6XDHl/va57CX78J4HUDfkdbr3uCtsHMW/Q9fmW8byIUzsemj5IpLFqV8byE9hsoUAcmIs8BrNSfke+FVOC3jSb2CxnWznibwig0oxI7PXb5Y4tL3rkjVbsAvKX5CLU3dq4Yj4YjtYyvWD00dKOhMzTdhhbICD0D2EavKdsngZw4s4wirELyaKNkAue/UG/0iCfZCfrdhctN9EAQBOZbtTcYkAH2HfIh/yN8ve6NSyJSvn/HxA5kt90kKVFerji1moJovSgCDWKmPVY6CD4Ymx2G5AwegONQFYiiXM1HcAkXvCCRaSXAZQ6Zk83VdGidm2gQ1TbCBHmzodor1yeMVr6TYGeDxEdOxlng9C/htmUve0YaHBm5kckGtfhzQhWI4AIkwU1D7Fiu11V+4oQnNC1L2pxs1PM8Kag8dd+tvtnHSz+yg71 MIME-Version: 1.0 X-OriginatorOrg: sct-15-20-4755-11-msonline-outlook-5ce7b.templateTenant X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DM8PR16MB4357.namprd16.prod.outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 2137a25b-352a-449d-f847-08d9f64a8ae3 X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2022 21:30:26.7376 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN0PR16MB4416 X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2022 21:30:30 -0000 I tried it as the very first command even before run. Any more ideas? (tx a= lready) ________________________________ From: Ruslan Kabatsayev Sent: Monday, February 21, 2022 5:33 PM To: Edgar Mobile Cc: gdb@sourceware.org Subject: Re: Does gdb initialize uninitialized variables? Hi, On Mon, 21 Feb 2022 at 12:45, Edgar Mobile via Gdb wro= te: > > Greetings, > > I currently try to find a bug that might be caused by uninitialized varia= bles/memory. But it never appears when I use gdb. Does gdb change how memor= y is initialized in any way, be it on stack or via new/malloc? Memory-related bugs that don't happen when using GDB but do without GDB are often caused by GDB disabling ASLR. This is usually useful for reproducibility of debugging sessions, but may indeed make address space layout too predictable and fail to reproduce a bug. Try using the GDB command "set disable-randomization off" (without quotes) to undo this behavior and thus start your program in a normal, randomized, environment. Besides, if your problem is indeed with uninitialized variables, you might find Valgrind memory checker more useful than a debugger. > > Regards Regards, Ruslan