| Subject | GUI version of FB Trace Manager (fbtracemgr) |
|---|---|
| Author | certfb |
| Post date | 2013-04-07T14:54:30Z |
Hello list!
I have implemented a very simple GUI version of the bundled trace tool fbtracemgr using wxWidgets.
If anyone is interested I am more than happy to upload or send them the code.
If I get the chance I will try to write a blog because some aspects of the trace API take a bit of digging to find the documentation ;)
The only problem that I have at the moment is that I am using the "isc_info_svc_timeout" command as part of a "isc_info_svc_line" isc_service_query() but instead of replying with "isc_info_svc_timeout" in the header the server replies with "isc_info_svc_line" but a zero length data block.
I looked through the source of fbtracemgr and although I think it expects "isc_info_svc_timeout" it probably doesn't give an error if it doesn't get it.
It isn't particularly important because I can just detect 0 length lines (for a normal response even an empty line provides a '\n') but I wondered if anyone has any ideas about this?
I have implemented a very simple GUI version of the bundled trace tool fbtracemgr using wxWidgets.
If anyone is interested I am more than happy to upload or send them the code.
If I get the chance I will try to write a blog because some aspects of the trace API take a bit of digging to find the documentation ;)
The only problem that I have at the moment is that I am using the "isc_info_svc_timeout" command as part of a "isc_info_svc_line" isc_service_query() but instead of replying with "isc_info_svc_timeout" in the header the server replies with "isc_info_svc_line" but a zero length data block.
I looked through the source of fbtracemgr and although I think it expects "isc_info_svc_timeout" it probably doesn't give an error if it doesn't get it.
It isn't particularly important because I can just detect 0 length lines (for a normal response even an empty line provides a '\n') but I wondered if anyone has any ideas about this?