[haiku-commits] Re: r42080 - in haiku/trunk/src/apps/debugger: . model user_interface user_interface/gui user_interface/gui/inspector_window
- From: Rene Gollent <anevilyak@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Fri, 10 Jun 2011 11:20:12 -0400
On Fri, Jun 10, 2011 at 10:29 AM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
>> i.e. something like:
>>
>> class TeamMemoryBlockOwner {
>> public:
>> void RemoveBlock(TeamMemoryBlock* block);
>> }
>>
>> ?
>
> Yep.
>
Thanks, will deal with it tonight. On a related note, with these
fixes, do you want me to look at applying a similar solution to
LocatableEntry?
On a somewhat different tangent, do you think it would be
worthwhile/easily feasible to allow the debug API to look up the
protection bits on a page in the target team? The reason I ask is, the
next item on my list once the mem inspector is usable for viewing
target mem is to add edit support. Given that pages in the target team
might potentially be marked read only, I'd rather know that up front
and disable editing for that page in the inspector rather than
allowing the user to edit and notifying later that the write failed.
Thoughts?
Regards,
Rene
Other related posts:
