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: Disabling stack access for remote targets?

From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
To: Joakim Tjernlund <joakim dot tjernlund at transmode dot se>
Cc: gdb at sourceware dot org
Date: Sun, 3 Jun 2012 17:16:03 +0200
Subject: Re: Disabling stack access for remote targets?
References: <OF32191D46.36EDC2F3-ONC1257A10.004B2D80-C1257A10.004F9867@transmode.se>

On Fri, 01 Jun 2012 16:29:23 +0200, Joakim Tjernlund wrote:
> This can be devastating for a board that hasn't initialized RAM yet.
> Would it be possible for a remote target to inform gdb not to touch the
> stack? In its simplest form one could just test for sp == 0

I guess you want:
	$ info '(gdb)Memory Region Attributes'


Regards,
Jan

Follow-Ups:
- Re: Disabling stack access for remote targets?
  - From: Joakim Tjernlund

References:
- Disabling stack access for remote targets?
  - From: Joakim Tjernlund

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