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: argc - cant access memory

From: "Dave Korn" <dave dot korn at artimi dot com>
To: "'Daniel Jacobowitz'" <drow at false dot org>
Cc: "'Hadron'" <rileyrg at googlemail dot com>, "'Nick Roberts'" <nickrob at snap dot net dot nz>, "'Jim Blandy'" <jimb at codesourcery dot com>, "'Hadron'" <hadronquark at googlemail dot com>, <gdb at sourceware dot org>
Date: Tue, 10 Jul 2007 20:50:22 +0100
Subject: RE: argc - cant access memory
References: <87ejjhg137.fsf@gmail.com> <m3r6nh70gm.fsf@codesourcery.com> <18066.47080.812496.129394@kahikatea.snap.net.nz> <87hcoc5uef.fsf@gmail.com> <00a401c7c32a$567046f0$2e08a8c0@CAM.ARTIMI.COM> <20070710194642.GA27388@caradoc.them.org>

On 10 July 2007 20:47, Daniel Jacobowitz wrote:

> On Tue, Jul 10, 2007 at 08:41:40PM +0100, Dave Korn wrote:
>>   This is normal behaviour.  It's nothing to do with optimisation:
> 
> Actually, I expect this is the problem specific to "main" that we've
> seen before; it is caused by stack alignment code that recent GCCs
> emit on x86, to accomodate SSE.

  Ah, is the stack adjustment code not marked as frame-related?  I guess that
would do it ...

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

References:
- argc - cant access memory
  - From: Hadron
- Re: argc - cant access memory
  - From: Jim Blandy
- Re: argc - cant access memory
  - From: Nick Roberts
- Re: argc - cant access memory
  - From: Hadron
- RE: argc - cant access memory
  - From: Dave Korn
- Re: argc - cant access memory
  - From: Daniel Jacobowitz

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