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: Why no hwatch command in gdb ?

From: fche at redhat dot com (Frank Ch. Eigler)
To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
Cc: Eli Zaretskii <eliz at gnu dot org>, robertsong dot japan at gmail dot com, gdb at sourceware dot org
Date: Thu, 10 Mar 2011 09:47:11 -0500
Subject: Re: Why no hwatch command in gdb ?
References: <AANLkTimsE5nNEZ=EKo1wPs0BW9dNxdvVyu_5Fucts5K8@mail.gmail.com> <20110310081154.GA13603@host1.jankratochvil.net> <AANLkTi=5n0EebJQkWvXvCHnVxy5fEqrxSztdDhhcpCNR@mail.gmail.com> <20110310103409.GA29242@host1.jankratochvil.net> <E1Pxe0v-000453-AA@fencepost.gnu.org> <20110310115543.GA5414@host1.jankratochvil.net>

Jan Kratochvil <jan.kratochvil@redhat.com> writes:

> [...]
> But it being discussed for upstream kernel that the DR registers access via
> PTRACE_POKEUSER is broken anyway and GDB should use the existing hardware
> watchpoints support in Linux kernel perf via some higher level interface
> (still probably through the ptrace syscall).

While a new kernel interface wouldn't be able to fabricate any
hardware-watchpoint resources after they're exhausted, a properly
designed one should be able to evaluate software watchpoints much
faster.

- FChE

References:
- Why no hwatch command in gdb ?
  - From: robert song
- Re: Why no hwatch command in gdb ?
  - From: Jan Kratochvil
- Re: Why no hwatch command in gdb ?
  - From: robert song
- Re: Why no hwatch command in gdb ?
  - From: Jan Kratochvil
- Re: Why no hwatch command in gdb ?
  - From: Eli Zaretskii
- Re: Why no hwatch command in gdb ?
  - From: Jan Kratochvil

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