This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch]: x64 windows about red-zone-area
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Kai Tietz <Kai dot Tietz at onevision dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 1 Feb 2010 11:52:08 +0400
- Subject: Re: [patch]: x64 windows about red-zone-area
- References: <OF8BDB58FC.D3F0F89F-ONC12576B6.003FD2BC-C12576B6.00404C31@onevision.de>
> Question is, if for x64 windows target the red-zone size shouldn't be set
> to zero. It is possible to use SYSV via attribute switching in x64
> windows code, but by default x64 windows ABI doesn't have red-zone area at
> all. So I think it makes sense to set it to zero in amd64-windows-tdep.c
That makes sense, but... Just wondering, though - is creating a red zone
harmful in GDB? As far as I can tell, this information is only used during
inferior function calls (functions called from GDB), and just causes us
to waste a few byes. Have you run out of stack space that saving these
few bytes made a difference?
I'm thinking of the case where a user tries to debug an application
on x64 windows that does actually use a red zone. Wouldn't your change
break inferior function calls in this case?
--
Joel