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: Reporting 'out of hardware breakpoints' situation

From: Eli Zaretskii <eliz at gnu dot org>
To: Daniel Jacobowitz <drow at false dot org>
Cc: ddaney at caviumnetworks dot com, vladimir at codesourcery dot com, gdb at sources dot redhat dot com
Date: Wed, 24 Jun 2009 20:55:49 +0300
Subject: Re: Reporting 'out of hardware breakpoints' situation
References: <200906241558.23737.vladimir@codesourcery.com> <4A4263F1.6060209@caviumnetworks.com> <20090624174653.GA12412@caradoc.them.org>
Reply-to: Eli Zaretskii <eliz at gnu dot org>

> Date: Wed, 24 Jun 2009 13:46:54 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
> 
> So figuring out how many breakpoints are available is pretty
> complex.

I think it's pretty much impossible.  (We have a similar problem with
hardware watchpoints.)  Several breakpoints can be set to the same
address, in which case a single register can serve all of them, but
deciding that this is the case is tricky at best.

I think the way of throwing an exception and then handling it to
revert to the original state is much more promising.

References:
- Reporting 'out of hardware breakpoints' situation
  - From: Vladimir Prus
- Re: Reporting 'out of hardware breakpoints' situation
  - From: David Daney
- Re: Reporting 'out of hardware breakpoints' situation
  - From: Daniel Jacobowitz

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