From: Andreas Schwab <schwab@linux-m68k.org>
To: Cristian Zamfir <cristian.zamfir@epfl.ch>
Cc: <gdb@sourceware.org>
Subject: Re: backtrace when corrupt stack
Date: Fri, 05 Feb 2010 20:27:00 -0000 [thread overview]
Message-ID: <m28wb7e8df.fsf@igel.home> (raw)
In-Reply-To: <251102A0-163B-4484-AEFF-D13133F6F1D8@epfl.ch> (Cristian Zamfir's message of "Fri, 5 Feb 2010 20:58:03 +0100")
Cristian Zamfir <cristian.zamfir@epfl.ch> writes:
> I am pretty sure that the function in frame #5 should be vsprintf() which is passed a buffer with insufficiently allocated space. But on the stack I see __stack_chk_fail () instead of vsprintf ().
vsprintf is expanded inline. The real vsprintf is not called when the
fortify check fails.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-02-05 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 15:24 Cristian Zamfir
2010-02-05 17:16 ` Robert Dewar
2010-02-05 17:36 ` Tom Tromey
2010-02-05 19:05 ` Andreas Schwab
2010-02-05 19:58 ` Cristian Zamfir
2010-02-05 20:27 ` Andreas Schwab [this message]
2010-02-05 19:56 ` Dave Korn
2010-02-05 20:05 ` Cristian Zamfir
2010-02-05 20:39 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m28wb7e8df.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=cristian.zamfir@epfl.ch \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox