This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: why does assert(0) corrupt the stack trace?
- From: Paul Smith <paul at mad-scientist dot net>
- To: 慕冬亮 <mudongliangabcd at gmail dot com>, gdb at sourceware dot org
- Date: Sun, 05 Nov 2017 14:21:06 -0500
- Subject: Re: why does assert(0) corrupt the stack trace?
- Authentication-results: sourceware.org; auth=none
- References: <CAD-N9QVbDJNJXrnsS3PNTvRXvvUK=pB6f+Gpj4WGTSjMoYR9pg@mail.gmail.com>
- Reply-to: paul at mad-scientist dot net
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!