dyninstAPI: Make sure dominator nullNode always looks initialized
authorJosh Stone <jistone@redhat.com>
Tue, 21 Jan 2014 01:21:52 +0000 (17:21 -0800)
committerJosh Stone <jistone@redhat.com>
Tue, 21 Jan 2014 01:21:52 +0000 (17:21 -0800)
commitb27b44234a0a0044bde85f868be638ce8b5db225
treefa49cb2daca36e28d560031cda8b4fd71a5e182b
parent90637f7257e2d2a0d26de1228706338925372373
dyninstAPI: Make sure dominator nullNode always looks initialized

There's a mutual dependency between dominatorCFG and dominatorBB in how
nullNode is initialized.  To the analyzer, it looks like the uninitialized
pointer is used in BB, even though CFG straightens it out immediately.
Letting nullNode start NULL clears up the confusion.

Reported by coverity as UNINIT.
dyninstAPI/src/dominator.C