The second call fails with a cause clause exception.
You'll observe the same exception by:
> dbg:start().
> dbg:start().
Ultimately, this may be a bug in OTP, but since dbg:start/0 is undocumented I'm inclined to give it the benefit of the doubt. Regardless, since the documentation clearly states that calling dbg:tracer/0 is the proper way to start the default tracer message receiver, I argue that calling dbg:start/0 is a bug in gun.
This fixes a bug in
gun
when trying to open 2 connections with tracing enabled.You can recreate it like so:
The second call fails with a cause clause exception.
You'll observe the same exception by:
Ultimately, this may be a bug in OTP, but since
dbg:start/0
is undocumented I'm inclined to give it the benefit of the doubt. Regardless, since the documentation clearly states that callingdbg:tracer/0
is the proper way to start the default tracer message receiver, I argue that callingdbg:start/0
is a bug ingun
.