Question on NOTE()

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Question on NOTE()

jerry DeLisle-3
Hi all,

I noticed our source has been annotatated with numerous NOTE macro's (I assume).
Was this stuff added for improved debugging information. I managed to miss
whenever that happened.

Jerry
Reply | Threaded
Open this post in threaded view
|

Re: Question on NOTE()

Steve Kargl
On Fri, Nov 08, 2019 at 08:42:19AM -0800, Jerry DeLisle wrote:
> Hi all,
>
> I noticed our source has been annotatated with numerous NOTE macro's (I assume).
> Was this stuff added for improved debugging information. I managed to miss
> whenever that happened.
>
svn log suggests these came in with

r263750 | koenigni | 2018-08-21 11:48:59 -0700 (Tue, 21 Aug 2018) | 93 lines

This is the async IO patch from Nicholas and Thomas.
 
--
Steve
Reply | Threaded
Open this post in threaded view
|

Re: Question on NOTE()

Thomas Koenig-6
Am 08.11.19 um 18:37 schrieb Steve Kargl:
> On Fri, Nov 08, 2019 at 08:42:19AM -0800, Jerry DeLisle wrote:

>> I noticed our source has been annotatated with numerous NOTE macro's (I assume).
>> Was this stuff added for improved debugging information. I managed to miss
>> whenever that happened.
>>
> svn log suggests these came in with
>
> r263750 | koenigni | 2018-08-21 11:48:59 -0700 (Tue, 21 Aug 2018) | 93 lines
>
> This is the async IO patch from Nicholas and Thomas.

That is correct.

In normal configuration, they are a no-op. When investigating race
conditions (which is hard, almost by definition), you can set the
DEBUG_ASYNC macro to check what _really_ happens when.

Regards

        Thomas