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: xtensa: reading privileged special registers

From: Max Filippov <jcmvbkbc at gmail dot com>
To: Marc Gauthier <marc at tensilica dot com>
Cc: Maxim Grigoriev <maxim2405 at gmail dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Mon, 18 Jul 2011 12:37:54 +0400
Subject: Re: xtensa: reading privileged special registers
References: <201107180028.54700.jcmvbkbc@gmail.com> <CAC3St3DkgTP_bAbpdSh6n3bVivik1tieUopy-jd-yNrEyE=C1A@mail.gmail.com> <522C1DF17AF50042AD8AE87F7887BD3D01E849DCB7@exch.hq.tensilica.com>

Maxim, Marc, thank you for the answers.

> To see privileged registers, you'd want a setup that can e.g. debug a kernel or raw hardware.

That's my case: I have a gdbserver built into qemu, it has full access
to the processor state.

> For simplicity, the same register set is generated both for user and kernel situations, so GDB lists privileged registers even for user processes (e.g. via gdbserver or Linux native), even though they're not accessible. ?Maybe one day we'll fix that.

I can try to fix it, but I'm not sure what's the right way. I'd query
these registers from within xtensa_pseudo_register_read and fall back
to returning 0 if that query fails. Does that makes sense?

-- 
Thanks.
-- Max

References:
- xtensa: reading privileged special registers
  - From: Max Filippov
- RE: xtensa: reading privileged special registers
  - From: Marc Gauthier

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