[haiku-bugs] Re: [Haiku] #9773: Add exception breakpoint support

  • From: "anevilyak" <trac@xxxxxxxxxxxx>
  • Date: Fri, 14 Jun 2013 17:17:10 -0000

#9773: Add exception breakpoint support
-------------------------------------+----------------------------
   Reporter:  bonefish               |      Owner:  anevilyak
       Type:  enhancement            |     Status:  in-progress
   Priority:  normal                 |  Milestone:  Unscheduled
  Component:  Applications/Debugger  |    Version:  R1/Development
 Resolution:                         |   Keywords:
 Blocked By:  9713                   |   Blocking:
Has a Patch:  0                      |   Platform:  All
-------------------------------------+----------------------------

Comment (by anevilyak):

 Replying to [comment:3 bonefish]:
 > Absolutely. Theoretically one setting per language would be needed.
 Though, IMO focusing on C++ only is fine ATM.

 As far as this goes, since exception configuration would be team-wide, it
 seems the ideal approach would be to enumerate the languages used in the
 current team in order to find all possible languages that might need
 exception settings. Correspondingly, SourceLanguage would need to be
 extended to add the following capabilities:
 - indicate if the language in question supports exceptions and/or
 configuring them at all.
 - generate a language-specific exception settings configuration view.
 - provide functions that handle the corresponding exception breakpoint
 installation/removal.
 - exception settings persistence/restoration.

 However, currently we only store references to the source languages on the
 source files that the functions reference, which is a bit unwieldy for
 quickly finding them all. My initial thought is to also keep a list of
 references on TeamDebugInfo itself in order to conveniently be able to
 discover/enumerate them quickly for purposes like the above, and anything
 else that might later need to access a particular language such as
 expression evaluation, though the latter's more likely to be in the
 context of a particular stack frame/function so that would implicitly know
 the correct language anyways I suppose.

 As a starting point so we'll have something to work with initially, I have
 a simpler configuration window that just handles the C++ case for now, but
 the above pretty much outlines the direction I envision going to handle it
 properly in the long term. Feedback/design improvements would be
 appreciated.

--
Ticket URL: <http://dev.haiku-os.org/ticket/9773#comment:11>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: