Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hi,

I'm working on networked applications that uses both TCP and UDP connections and of course relied heavily on the ISockets interface/functions etc. I have a problem with the text output generated by the BREW networking code when a connection is established and receiving/sending data. It is absolutely spamming the Output Window. It is printing and printing all these ineligible msgs almost as soon as a packet is received/sent and this can happen many times a second. This renders the output window useless for catching any other important custom error/warning msgs.

Is there a way to shutup or toggle these noisy BREW networking code debug msgs?

On SDK 3.1.5 simulator, you'll get messages such as:
*sim_dssocket2.:1606 - DSIFace_BringUpPhysLink pif=6443852, state=UP
*sim_dssocket2.:1606 - DSIFace_BringUpPhysLink pif=6443852, state=UP
*sim_dssocket2.:1606 - DSIFace_BringUpPhysLink pif=6443852, state=UP
*sim_dssocket2.:1606 - DSIFace_BringUpPhysLink pif=6443852, state=UP
*sim_dssocket2.:1606 - DSIFace_BringUpPhysLink pif=6443852, state=UP

On SDK 3.1.4 simulator, its even worst, i'm getting spammed bad:
*AEENet.c:746 - # 32746828 (Socket)
*AEESockPort.c:1997 - * 32746828:2 ST_OPEN
*AEENet.c:746 - # 32746828 (Socket)
*AEESockPort.c:1997 - * 32746828:2 ST_OPEN
*AEENet.c:746 - # 32746828 (Socket)
*AEESockPort.c:1997 - * 32746828:2 ST_OPEN
*AEENet.c:746 - # 32746828 (Socket)
*AEESockPort.c:1997 - * 32746828:2 ST_OPEN
*AEENet.c:746 - # 32746828 (Socket)
*AEESockPort.c:1997 - * 32746828:2 ST_OPEN

Lower version simulators are not an option due to other extension requirements.

I've also faced similar "spamming" of the output window.
I think there is no easier way for removing the output messages unless you recompile those code.
If you cannot live with it and must need a solution, I can give you one (which would involve changing some libs/dlls in hex mode, understanding the COFF format etc...)
-empeegee.

I've also faced similar "spamming" of the output window.
I think there is no easier way for removing the output messages unless you recompile those code.
If you cannot live with it and must need a solution, I can give you one (which would involve changing some libs/dlls in hex mode, understanding the COFF format etc...)
-empeegee.

empeegee wrote:I've also faced similar "spamming" of the output window.
I think there is no easier way for removing the output messages unless you recompile those code.
If you cannot live with it and must need a solution, I can give you one (which would involve changing some libs/dlls in hex mode, understanding the COFF format etc...)
-empeegee.
You can write a windows app to hook the output window and
filter the messages.

empeegee wrote:I've also faced similar "spamming" of the output window.
I think there is no easier way for removing the output messages unless you recompile those code.
If you cannot live with it and must need a solution, I can give you one (which would involve changing some libs/dlls in hex mode, understanding the COFF format etc...)
-empeegee.
You can write a windows app to hook the output window and
filter the messages.

I just use one of the Brew 2.x emulators -- there were two available and I know one of them spams, but the other version does not.

I just use one of the Brew 2.x emulators -- there were two available and I know one of them spams, but the other version does not.