Hi,
I used the $DBGMT/dynamic_debug/control to control printing debuginfo.But When i wote multiple queries which has at least one didn't match,
the result is ok which no error can return.
So i think i wrote correct queries.But until using dmesg, i only found error.
And if parm verbose of dynamic_debug is zero, i can't find the result by dmesg.
So i think it's not convenient.
If it did not found any query,it should return error.
Thanks!????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m????????????I?
On Wed, Aug 22, 2012 at 07:42:14PM +0800, Jianpeng Ma wrote:
> Hi,
> I used the $DBGMT/dynamic_debug/control to control printing debuginfo.But When i wote multiple queries which has at least one didn't match,
> the result is ok which no error can return.
> So i think i wrote correct queries.But until using dmesg, i only found error.
> And if parm verbose of dynamic_debug is zero, i can't find the result by dmesg.
> So i think it's not convenient.
> If it did not found any query,it should return error.
>
> Thanks!
Hi,
You can verify what changes have occured by looking in the
$DBGMT/dynamic_debug/control file, and verifying what statements have
been matched. For example, we add a 'p' when printing is enabled.
Does that address your concern?
As these debug statements come and go, I think I'd prefer not to error
out in this case.
Thanks,
-Jason