From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9508 invoked by alias); 12 Aug 2010 17:52:48 -0000 Received: (qmail 9424 invoked by uid 48); 12 Aug 2010 17:52:32 -0000 Date: Thu, 12 Aug 2010 17:52:00 -0000 Message-ID: <20100812175232.9423.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/45264] Stack corruption with any function using frame In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "darkdragon2000 at hotmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-08/txt/msg01027.txt.bz2 ------- Comment #2 from darkdragon2000 at hotmail dot com 2010-08-12 17:52 ------- It's not a bug in the handler since when the interrupt fires at the point when the stack pointer is invalid (right after 0x50c), the program counter gets pushed onto the stack, which is an invalid location. When I tried to submit a report with the vendor, they pointed me back here. Maybe this should go to AVRLiBC? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45264