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: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: 慕冬亮 <mudongliangabcd at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Sun, 5 Nov 2017 21:10:42 +0100
- Subject: Re: why does assert(0) corrupt the stack trace?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jan dot kratochvil at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com EA793267D5
- References: <CAD-N9QVbDJNJXrnsS3PNTvRXvvUK=pB6f+Gpj4WGTSjMoYR9pg@mail.gmail.com> <20171105195410.GA29185@host1.jankratochvil.net> <CAD-N9QX17JssrU=Eo5whDFzLLQVUUb1RidHWwqzUC3ZFY6LGJw@mail.gmail.com>
On Sun, 05 Nov 2017 21:05:04 +0100, 慕冬亮 wrote:
> If I compile the program with "-O0", this problem may be solved. Yes?
You would need to recompile glibc with -g -O0. Which I am not sure if it is
even possible.
Jan