From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37638 invoked by alias); 5 Nov 2017 19:13:55 -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 37629 invoked by uid 89); 5 Nov 2017 19:13:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=HX-HELO:sk:mail-ua, H*RU:sk:mail-ua, Hx-spam-relays-external:sk:mail-ua, HX-Received:10.159.35.107 X-HELO: mail-ua0-f177.google.com Received: from mail-ua0-f177.google.com (HELO mail-ua0-f177.google.com) (209.85.217.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 05 Nov 2017 19:13:53 +0000 Received: by mail-ua0-f177.google.com with SMTP id b11so5047044uae.12 for ; Sun, 05 Nov 2017 11:13:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5DmWmceHTIVwwZi2LLpfSoN2CGs3s1VpXRHItjIFHwo=; b=pojr64TF6+T6iUCnHv0enHHKpTMarIOi4D5f39evAG6rZhCdRqKzCUtqXV83DlR69P e2+fHPxfIsv6cMSTlAtET7fY8dv6I6AupTmiJhO2HZ3MAIQMPqVY8fCTUpYoe13EwipX rPP0FC/+OzJzdPUv+GTL6LEGvQSAopq3M2QLjxZtSGSKAJsbcje4A6uaozbv0Tor8nmN gkugYx7bQsZec3Y1i7ZIFMpmA7bJC+YvjDFi3qn1skUQsAN+aYuJet64tDAluSj5IwKX 8XH2JE4U4x/qqv/G9EhyejETvmPGDMlGJHIN30mcTixpN36hW++fy/3czcAVMZTSSmPE jvBQ== X-Gm-Message-State: AJaThX7RXc0KNQrJeQQ2f0JhCrcFUG4d353NwAp3pX8Vjjcz0U2c+SSH EBZXqosXY/ho1Q2Tm/vMCydImm/kF+isQkT9Z2A= X-Google-Smtp-Source: ABhQp+S+27lY2dWhDVTFeO1ro79wO/rHhcg6ZbKf0fIx8/6+7w0BUneLDHCh2T5VVsUBoDDqrk0IH5V+XvNswhSJ42I= X-Received: by 10.159.35.107 with SMTP id 98mr9685095uae.190.1509909230985; Sun, 05 Nov 2017 11:13:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.146.29 with HTTP; Sun, 5 Nov 2017 11:13:20 -0800 (PST) From: =?UTF-8?B?5oWV5Yas5Lqu?= Date: Sun, 05 Nov 2017 19:13:00 -0000 Message-ID: Subject: why does assert(0) corrupt the stack trace? To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-11/txt/msg00000.txt.bz2 Hi all, 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? -- My best regards to you. No System Is Safe! Dongliang Mu