Path: news.mitre.org!blanket.mitre.org!agate!logbridge.uoregon.edu!newsfeed.direct.ca!news.he.net!newshub.cts.com!newsfeed.cts.com!cmkrnl!jeh
From: jeh@cmkrnl.com (Jamie Hanrahan)
Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode
Subject: Re: How do I set a breakpoint in DriverEntry()?
Message-ID: <1998Jan3.190524.8385@cmkrnl>
Date: 3 Jan 98 19:05:24 PST
References: <j7hg82b0eq.fsf@amazonia.efn.org>  <01bd189f$153bf700$917f10ac@orland>
Organization: Kernel Mode Systems, San Diego, CA
Lines: 22

In article <01bd189f$153bf700$917f10ac@orland>, "Michael A. Crawford" <michaelc@travsoft.com> writes:
> You can also conditionally call DbgBreakPoint() using a DEBUG registry
> entry in your driver code.  If the registry entry exists and is set to the
> proper debug value or level, call DbgBreakPoint().  If not, skip it and
> continue loading.  You may even decide to leave this code in for production
> since you don't necessarily have to document it 

Yep - in fact you can see this in a few of the MS examples. 

> and the code is
> automatically unloaded after DriveEntry completes.

Only if you declare it with #pragma alloc_text(INIT,DriverEntry)
I know this is a nit, but I wouldn't want people to think it happens 
with no effort on our part. 

	--- Jamie Hanrahan, Kernel Mode Systems, San Diego CA
        Internet: jeh@cmkrnl.com (JH645)  CompuServe: 74140,2055  
drivers, internals, networks, applications, and training for VMS and Windows NT
NT driver FAQ, links, and other information:  http://www.cmkrnl.com/

If you post a reply in news, please don't e-mail it too.