I have an application that sends mesages (hints) about program execution to a console style window.
Application when run via VS2005 debug environment reports messages fine in this dedicated window.
As you would expect, Inspector XE when has the Radio button set in the Option\\Intel Inspector XE 2011 Properties set to Separate Console (last of the 3 - Default), Window does the same thing (fine).
For clarity the messages still appear fine when they go to the sameseparate window.
Switchradio button to "Collection Log Window" (Top Radio button of the 3)
All my threads are up an running by over 30 minutes
This application uses 15 threads:10 waiting for events of different kind to arrive before they begin any work
The others, are sleeping on timely fashion (5 to 100 nSec) interval. No big deal.
The summary comfirm the threads were created.
I confirmed their readiness via someevent logger messages.
The application isbasically idleing waiting for a command to arrive via a port before starts any work.
CPU usage is 11% top (utilized)
How is possible that the Inspector XE thread that writes to the Application Window has no chance to write a single message there after 30 minutes?
I calculated the number of messages that should have been appearing - 42 lines of text with the longest line65 characters long.
Tried a simpler single program, using a couple of threads (Main application thread + 1 Single thread)
Both threads send some messages, but a different rate.
For this programit takes about 10 minutes before I see the first group of messages which appear to update at ramdom rate. (Strange)
Nothing else is going on that I can tell.
CPU usage is 9% top (utilized)
Q1: What is going on with the Inspector XE ability of reporting messages to the application window?
Is there a way to have it more responsive at the cost of more time for the inspection?
I obviously will be running the test overnight...
One possibility could be to give the user abutton so hecan raise the priority of the thread that drives the show, or run the defaulty priority as shipped. (Wish)
Not knowing what else to do and understanding fully the logging capability of the tool, since I need to log messages operation for inspection after the run, I tried to use the Middle Radio button selection: marked "Microsoft Visual Studio* Output Window" radio button
StartInspector XE with thethesimple "Hello World" been displayed forever at 1 second interval.
I see no output in any Visual Studio Window Pane inside Microsoft.
I tought that after 10 minutes or so, something would be showing up, somewhere
No such luck.
Warning: If you try this mode of operation you will not be able to quit, without crashing the IDE (or so appears)
Probably, it is because since V7 update, it is required to confirm the desire of quitting the run via the keyboard input once "Hit any key to continue..." appears
Sincethere is no window in focus containing the message, my keyboard entry is lost.
If you click the Close button while the program still runs, instead of Stop followed by Close, you do more damage. The IDE appear to lock-up with all the Run arrows been disabled. My program is obviously still running).
So, I must be doing something wrong with the tool.
Q2: What is then this display message option for?
Where the "Hello World" messages went to?
I believe I answered this question on my own...
I reviewed thedocumentation about the XE inspector demonstration chapters and I came across the statement that basically says that when using the "Microsoft Visual Studio* output window" the user generated messages will appear there.
Wrong. They do not. (Does this mean that this feature is broken?)
Has anybody seen this operate?
I use the lastest update 7 insive VS2005
The MS Output Combo box lists only the following:
Intel Inspector XE 2011 Messages
Intel Parallel Debugger Extension
I might need to click on something that is not listed
Thanks to anyone that can tell me what is going on with my 2 questions (now 1).