[haiku-development] Re: Odd errors messages while building DEBUG=1
- From: Rene Gollent <anevilyak@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 14 Apr 2013 18:42:39 -0400
On Sun, Apr 14, 2013 at 6:10 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> Since get_thread_info() for the current thread normally cannot fail, if a
> pointer to valid storage for the thread info is provided, the easiest
> solution is probably to change the code in the BReferenceable destructor to
> skip the debugger call when get_thread_info() fails. OTOH it is worth
Will do that, was afraid of potentially allowing valid failures to
pass through by doing so but that shouldn't be an issue if that's
correct.
> checking why the heuristic doesn't work in this case, since neither
> resume_thread() nor the Signal destructor seem to use a lot of stack.
Will see what I can find out :).
Thanks for the answer,
Rene
Other related posts:
