From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93939 invoked by alias); 5 Nov 2017 19:46:33 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 93930 invoked by uid 89); 5 Nov 2017 19:46:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=3.4 required=5.0 tests=AWL,BAYES_40,BODY_8BITS,GARBLED_BODY,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=corrupted, =ac=e4=ba=ae, H*M:140, H*F:U*paul?= X-HELO: gproxy4-pub.mail.unifiedlayer.com Received: from gproxy4-pub.mail.unifiedlayer.com (HELO gproxy4-pub.mail.unifiedlayer.com) (69.89.23.142) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 05 Nov 2017 19:46:32 +0000 Received: from cmgw2 (unknown [10.0.90.83]) by gproxy4.mail.unifiedlayer.com (Postfix) with ESMTP id 78022175BFF for ; Sun, 5 Nov 2017 12:21:11 -0700 (MST) Received: from box5008.bluehost.com ([50.116.64.19]) by cmgw2 with id WKM81w0040QvKlu01KMBzF; Sun, 05 Nov 2017 12:21:11 -0700 X-Authority-Analysis: v=2.2 cv=dZfw5Tfe c=1 sm=1 tr=0 a=gch/BGY/Gm5DEW28s2kmlQ==:117 a=gch/BGY/Gm5DEW28s2kmlQ==:17 a=IkcTkHD0fZMA:10 a=sC3jslCIGhcA:10 a=7HgrdYJii-XEhYkUMycA:9 a=QEXdDO2ut3YA:10 Received: from pool-74-104-137-100.bstnma.fios.verizon.net ([74.104.137.100]:58680 helo=homebase) by box5008.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1eBQTj-001cOE-Rl; Sun, 05 Nov 2017 12:21:08 -0700 Message-ID: <1509909666.2456.140.camel@mad-scientist.net> Subject: Re: why does assert(0) corrupt the stack trace? From: Paul Smith Reply-To: paul@mad-scientist.net To: =?UTF-8?Q?=E6=85=95=E5=86=AC=E4=BA=AE?= , gdb@sourceware.org Date: Sun, 05 Nov 2017 19:46:00 -0000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BWhitelist: no X-Exim-ID: 1eBQTj-001cOE-Rl X-Source-Sender: pool-74-104-137-100.bstnma.fios.verizon.net (homebase) [74.104.137.100]:58680 X-Source-Auth: paul@mad-scientist.us X-Email-Count: 1 X-Source-Cap: bWFkc2NpZTE7bWFkc2NpZTE7Ym94NTAwOC5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-SW-Source: 2017-11/txt/msg00001.txt.bz2 On Sun, 2017-11-05 at 14:13 -0500, 慕冬亮 wrote: > I have a question about debugging assert in gdb. When one program > crash at one assert statement, the stack trace shown in the gdb is > corrupted. Is it normal? No, that's not normal. Cheers!