This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS v6.1.2 loaded on Windows 7 64 bit filling event log

I have noticed that once the code composer studio vers 6.1.2 is opened on my windows 7 64 bit machine I see cmd.exe and conhost.exe in the Windows Security log. This is having some concern due to the fact that both of those exe's are hitting the log at a rate of twice per second for the entire duration that the studio is opened. Once I close it the logging stops. Is there a configuration or install step that was missed or does it really require this many modifications to the command line? A few hits would be expected but we are talking over 100,000 in an 8 hour shift. Can anyone help or explain this?

Simply clearing the log is not a viable solution in this case.

  • Hi,

    That is interesting; I see the same scenario here. I will double-check a few details and report back to you.

    Regards,
    Rafael
  • Hi,

    Thanks for reporting this; I found out this behavior is intentional. As per the developer's report:

    internal said:

    A feature was added a while ago to avoid data intensive DVT features (e.g. trace) using up all disk storage and locking-up user’s machine.

    If freespace on disk is less that some number (I believe 4GB) then DVT will stop logging data to disk. The check is done frequently enough to handle high data rates.

    We can look to see if there are ways to do this and avoid the security log but will have to be post CCS6.2.

    I filed an enhancement to discuss what would be the best approach to minimize the impact of this feature - which is pretty useful when using Trace or other graphing capabilities of CCS. Perhaps have this only active during a debug session, but at the moment this was not analyzed in deep detail.

    I apologize for the inconvenience,

    Rafael

  • Thanks for the update. I would like to have a way to limit it, even if I just need to run a different version. Your assistance is greatly appreciated.
  • Hi,

    Unfortunately at the moment there is no workaround for this. Sorry.

    I apologize for the inconvenience,
    Rafael
  • Thanks for checking. I will just keep the log file size at a bigger number and dig through the million entries.