Ok, I’ve read the Symantec web-site, which seems to indicate that there’s
no (simple) solution to this problem.
But I would like to hear what your exact problems are, rather than discuss
the Symantec web-site. Are you seeing a blue-screen, the system stops, or
what happens?
I suspect the problem with WinDBG is that Symantec are “hooking” something
in their product, which makes them incompatible with debuggers of this
type. Perhaps SoftICE works better, but that is also a kernel debugger
(technically), but it may use different techniques to access it.
Another way to solve the problem is of course to not use a kernel debugger,
but rather use other debug methods, typically dumping data from the code
without the use of a debugger. You can either open a debug output file and
use a combination of sprintf and WriteFile to write the data, or use the
serial port directly from your driver [using a simple busy-wait loop] to
indicate what’s going on inside your driver. This method works fine until
you need to debug other parts of the system than those that you’ve written.
It can of course be done, but it does beomce much more difficult.
A third way would be to find out what Symantec are hooking that causes
problems with these types of debuggers, and patch that bit of hooking out
of their executable, so that it’s not being done…
I’m unsure of which is the best solution. Fortunately, when writing display
drivers, we don’t see these type of interaction problems very often.
–
Mats
-------- Notice --------
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying or distribution of the message, or any
action taken by you in reliance on it, is prohibited and may be unlawful.
If you have received this message in error, please delete it and contact
the sender immediately. Thank you.
xxxxx@lists.osr.com wrote on 01/11/2005 01:55:52 PM:
Thank you Mats for your advice.
Anyway, NAV is not compatible with WinDBG and it is described on Symantec
HP. And I would like to know why you are pretty sure it works with
WinDBG?
In addition, I setup NAV with default configuration which NAV setup
recommend.
I really appreciate your advice.
Thank you,
Hideyuki Inamasu.
“Mats PETERSSON” wrote in message
> news:xxxxx@ntdev…
> >
> >
> >
> >
> >
> > Can you explain exactly what your setup is, and what the problem is. We
> > don’t use NAV, but I’m pretty sure that it would work with WinDBG…
> >
> > –
> > Mats
> >
> > xxxxx@lists.osr.com wrote on 01/11/2005 01:28:40 PM:
> >
> >> Hello,
> >>
> >> Now I am developing TDI filter driver and have a problem with Norton
> >> AntiVirus 2004/2005. I tried to run WinDbg and Norton AntiVirus
software
> > is
> >> installed to target PC, then… I found that Kernel debugger is not
> >> compatible with that software in Symantic HP, but I do not found how
to
> > go
> >> with such problem.
> >>
> >> Is there any workaround for this problem? Or is there any good way to
> > debug
> >> my problem?
> >>
> >> Please give me your advice.
> >>
> >> Thank you,
> >> Hideyuki Inamasu.
> >>
> >>
> >> —
> >> Questions? First check the Kernel Driver FAQ at http://www.
> >> osronline.com/article.cfm?id=256
> >>
> >> You are currently subscribed to ntdev as: xxxxx@3dlabs.com
> >> To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >> ForwardSourceID:NT0000AA12
> >
> >
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.
> osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@3dlabs.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
> ForwardSourceID:NT0000AA1E