Alternatively, you could write the stuff into files, instead of to stderr. This is useful especially for operators executing in multiple ESP processes.
Method ExOperStats::addMessage() is for such purpose. On Wed, Apr 13, 2016 at 11:47 AM, Eric Owhadi <[email protected]> wrote: > Hi Trafodionners, > > I see in the code some debugging statement logging stuff in stderr. > > Like > > fprintf(stderr, > > " Attr(%d): dataType: %d nullable: %d variable: %d " > > "offset: %d voaOff: %d align: %d\n", > > k, attr->getDatatype(), attr->getNullFlag(), > > (attr->getVCIndicatorLength() > 0 ? 1 : 0), > attr->getOffset(), > > attr->getVoaOffset(), attr->getDataAlignmentSize()); > > > > However, I tried to sqlci 2> err.out > > No success. > > > > I tried to run it with debugger in Eclipse (internally using gdb), and > usually when I debug java programs this way, stderr is redirected to the > Console view in eclipse. But not with this. > > > > So question, how do I redirect or view stderr when debugging trafodion cpp > code? > > Eric > -- Regards, --Qifan
