This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: backtrace when corrupt stack

From: Andreas Schwab <schwab at linux-m68k dot org>
To: Cristian Zamfir <cristian dot zamfir at epfl dot ch>
Cc: <gdb at sourceware dot org>
Date: Fri, 05 Feb 2010 21:27:08 +0100
Subject: Re: backtrace when corrupt stack
References: <33F51508-83E5-4791-ADA3-DA8591582C49@epfl.ch> <m2hbpvec59.fsf@igel.home> <251102A0-163B-4484-AEFF-D13133F6F1D8@epfl.ch>

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."

References:
- backtrace when corrupt stack
  - From: Cristian Zamfir
- Re: backtrace when corrupt stack
  - From: Andreas Schwab
- Re: backtrace when corrupt stack
  - From: Cristian Zamfir

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]