Subject: Re: [boost] Interest check: Boost.Debug
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-06-06 07:53:59
Gennadiy Rozental wrote
On Saturday, June 06, 2009 3:15 AM
> I also have following functions in this module:
> debugger_break - cause program to break execution in debugger
> at call point
> break_memory_alloc - cause program to break execution in debugger at
> specific allocation point
The function name connotes causing the following memory allocation(s) to fail, which is useful in its own right for testing error handling.
How is break_memory_alloc() different from debugger_break() in practical terms? IOW, if break_memory_alloc() causes a break at the next allocation, it doesn't seem any different than preceding the allocation call with debugger_break().
Rob Stewart robert.stewart_at_[hidden]
Software Engineer, Core Software using std::disclaimer;
Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk