JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.2p0 | CONFIDENTIAL | CodeSecure Inc |
同じ動的オブジェクトを、2回初期化しようとしています。
| クラス名 | Double Initialization | ||||||
|---|---|---|---|---|---|---|---|
| 日本語クラス名 | 二重初期化 | ||||||
| クラス分類 | 信頼性 (reliability) | ||||||
| ニーモニック | ALLOC.DI | ||||||
| カテゴリー |
|
||||||
| 対応言語 | C および C++ で利用可能です。 |
||||||
| 有効/無効設定 | このワーニングクラスのチェックはデフォルトで有効になっています。チェックを無効にするにはプロジェクト設定ファイル
(configuration file)に以下の WARNING_FILTER ルールを追加してください。
WARNING_FILTER += discard class="Double Initialization" |
CodeSonar ships with library models that allow it to functions such as Win32 InitializeCriticalSection() that initialize a dynamic object. If one of these functions is called to initialize a dynamic object that is definitely already initialized by an earlier call, a warning will be issued.
If you have created a custom library model for some function f() in terms of one of these existing models, calls to f() will also be capable of triggering Double Initialization warnings.
#include <windows.h>
void double_init(void){
CRITICAL_SECTION cs;
/* ... */
InitializeCriticalSection(&cs);
DeleteCriticalSection(&cs);
InitializeCriticalSection(&cs); /* ok because of intervening DeleteCriticalSection() */
InitializeCriticalSection(&cs); /* warning issued here */
DeleteCriticalSection(&cs);
}
設定ファイルの以下のパラメータがこのワーニングクラスのチェックに影響します。
To report problems with this documentation, please visit https://support.codesecure.com/.