You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am investigating a bug in our code regarding __syscall_send in pthreads proxied builds. Code works in singlethreaded builds, but doesn't in multithreaded. To quickly be able to figure out what is the discrepancy between ST and MT builds, I want to enable -sSOCKET_DEBUG=1 to be able to dump the WebSockets comms in each.
However, when I do that, I get a build that spams to me all sorts of other debug info and the interesting information that I want to debug with WebSockets is drowned in the noise:
making it impossible to find the actual sockets debug prints.
I see there's this construct:
and hence
Locally I can get rid of this by deleting the line
but it doesn't seem that SOCKET_DEBUG (or any of those xxx_DEBUGs for that matter?) should imply RUNTIME_DEBUG, that is counterproductive?
The text was updated successfully, but these errors were encountered:
I am investigating a bug in our code regarding __syscall_send in pthreads proxied builds. Code works in singlethreaded builds, but doesn't in multithreaded. To quickly be able to figure out what is the discrepancy between ST and MT builds, I want to enable
-sSOCKET_DEBUG=1
to be able to dump the WebSockets comms in each.However, when I do that, I get a build that spams to me all sorts of other debug info and the interesting information that I want to debug with WebSockets is drowned in the noise:
making it impossible to find the actual sockets debug prints.
I see there's this construct:
and hence
Locally I can get rid of this by deleting the line
but it doesn't seem that
SOCKET_DEBUG
(or any of thosexxx_DEBUG
s for that matter?) should implyRUNTIME_DEBUG
, that is counterproductive?The text was updated successfully, but these errors were encountered: