There is any way to give options to ddk build to stop generating .debug section type information? In Free Build we don’t want debugging, so why is .pdb path string built into binary?
BA
You need to add /DEBUG:NO to your linker command line. How you do this in
BUILD without generating warnings, I’m not sure.
If all you are worried about is the pdb path in a RELEASE build, that can be
removed by binplace (and maybe EDITBIN; not sure).
If you really don’t want to debug a fre build, you need to rethink things.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Wednesday, August 25, 2010 9:56 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] stop .debug section generation?
There is any way to give options to ddk build to stop generating .debug
section type information? In Free Build we don’t want debugging, so why is
.pdb path string built into binary?
BA
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I just love the username - it looks like I have pissed this particular poster off really well…
Anton Bassov
No anton. I’m your biggest fan. Imitation == flatery you know. I have Anton Bassov Fan Club Membership Card #1.
Why would I not want to debug free build of driver? If I want to debug I use checked build.
BA
What about debugging you fee driver when you have a customer crash? Making them use a chk driver is typically not an option. What info are you afraid of leaking with a .debug section in a release driver?
d
dent from a phpne with no keynoard
-----Original Message-----
From: xxxxx@yahoo.com
Sent: August 25, 2010 7:48 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] stop .debug section generation?
No anton. I’m your biggest fan. Imitation == flatery you know. I have Anton Bassov Fan Club Membership Card #1.
Why would I not want to debug free build of driver? If I want to debug I use checked build.
BA
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
You need to test both and you need symbols to do that.
On Aug 25, 2010 10:48 PM, wrote:
> No anton. I’m your biggest fan. Imitation == flatery you know. I have
Anton Bassov Fan Club Membership Card #1.
>
> Why would I not want to debug free build of driver? If I want to debug I
use checked build.
>
> BA
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Indeed true. You can encounter timing issues in release builds that you
cannot see in checked builds. I don’t hesitate to open my release drivers if
I need to and step into code. Yeah, the topology is quite different but I’ve
found and fixed many problems after the driver was released.
So, to he who wants to remove that capability: I do hope in your perfection
that you know for an absurdity that your code is perfect. 
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, August 25, 2010 9:51 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] stop .debug section generation?
What about debugging you fee driver when you have a customer crash? Making
them use a chk driver is typically not an option. What info are you afraid
of leaking with a .debug section in a release driver?
d
dent from a phpne with no keynoard
-----Original Message-----
From: xxxxx@yahoo.com
Sent: August 25, 2010 7:48 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] stop .debug section generation?
No anton. I’m your biggest fan. Imitation == flatery you know. I have Anton
Bassov Fan Club Membership Card #1.
Why would I not want to debug free build of driver? If I want to debug I use
checked build.
BA
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
> Why would I not want to debug free build of driver? If I want to debug I use checked build.
If you WLK your driver and then get crash reports from WER you want to
be able to debug the minidumps you get. The dumps will obviously come
for the release version of the driver.
Problem: cl/link can not generate matching debug symbols for a build if
“/debug” was not set during compilation (it shuffles the function order
around). I have seen this for applications (see other thread), but
strongly assume it does the same for drivers.
Microsoft does not regard this as a problem, because their software (VS
and build.exe) sets the “/debug” switch by default.
bantonassov write perfect code.
or debug paths provide way too much information?
Mark Roddy
On Thu, Aug 26, 2010 at 3:51 AM, Hagen Patzke wrote:
>
> > Why would I not want to debug free build of driver? If I want to debug I
> use checked build.
>
> If you WLK your driver and then get crash reports from WER you want to
> be able to debug the minidumps you get. The dumps will obviously come
> for the release version of the driver.
>
> Problem: cl/link can not generate matching debug symbols for a build if
> “/debug” was not set during compilation (it shuffles the function order
> around). I have seen this for applications (see other thread), but
> strongly assume it does the same for drivers.
>
> Microsoft does not regard this as a problem, because their software (VS
> and build.exe) sets the “/debug” switch by default.
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Mark Roddy: yes “bantonassov write perfect code.” “bantonassov smash!!!” “bantonassov is the strongest one there is!”…when you are tri-lingual, come on over to my neighborhood of the net so I can make fun of your Russian or French.
Mr. Man: I added LINKER_FLAGS=$(LINKER_FLAGS) /DEBUG:NO to my sources file, but got “LINK : error LNK1117: syntax error in option ‘DEBUG:NO’” I tried /DEBUG=NO, and that parsed, but it didn’t change anything. So if it was just warnings, I could live with it, but it’s actual errors.
Ultimately I just changed the path of my build directory so that it no longer had my obscene username in it, but the point was, I wanted know whether it was *even possible* to get rid of the debug info. It looks like it’s not, or just no one knows how, which is fine. I accept the logic of the people who said it is good to have in there for if I need to debug a free build, but really this is just a hobby hardware interface project, so I’m not responsible for supporting anyone. I guess the all the time-clock punchers who write drivers for a living have forgotten what it is to be curious.
BA
> Mr. Man: I added LINKER_FLAGS=$(LINKER_FLAGS) /DEBUG:NO to my sources file, but got
“LINK : error LNK1117: syntax error in option ‘DEBUG:NO’” I tried /DEBUG=NO, and that parsed, but
Also try /debug:none
All of this was never documented and so MS is considering that people rely on VS’s project settings or the documented BUILD macros.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
>Ultimately I just changed the path of my build directory so that it no
longer had my obscene username in it, but the point >was, I wanted know
whether it was *even possible* to get rid of the debug info.
You can get rid of the path to the PDB, just look at any image from MS.
Once you drop the stupid act and post from your real name someone might even
tell you how.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@ntdev…
> Mark Roddy: yes “bantonassov write perfect code.” “bantonassov smash!!!”
> “bantonassov is the strongest one there is!”…when you are tri-lingual,
> come on over to my neighborhood of the net so I can make fun of your
> Russian or French.
>
> Mr. Man: I added LINKER_FLAGS=$(LINKER_FLAGS) /DEBUG:NO to my sources
> file, but got “LINK : error LNK1117: syntax error in option ‘DEBUG:NO’” I
> tried /DEBUG=NO, and that parsed, but it didn’t change anything. So if it
> was just warnings, I could live with it, but it’s actual errors.
>
> Ultimately I just changed the path of my build directory so that it no
> longer had my obscene username in it, but the point was, I wanted know
> whether it was even possible to get rid of the debug info. It looks like
> it’s not, or just no one knows how, which is fine. I accept the logic of
> the people who said it is good to have in there for if I need to debug a
> free build, but really this is just a hobby hardware interface project, so
> I’m not responsible for supporting anyone. I guess the all the time-clock
> punchers who write drivers for a living have forgotten what it is to be
> curious.
>
> BA
>
I accept the logic of the people who said it is good to have in there for if
I need to debug a free build, but really this is just a hobby hardware
interface project, so I’m not responsible for supporting anyone. I guess the
all the time-clock punchers who write drivers for a living have forgotten
what it is to be curious.
I encourage your curiosity and suggest you start with setenv.bat in the WDK
looking at how NTDEBUG and NTDEBUGTYPE get setup and the related
information. Then you can go look into MAKEFILE.NEW in the WDK to see how
all of that ends up influencing the compile and link process.
You might discover along the way like many of us time-clock punchers that we
really don’t mind the debug information even when we don’t think we might
need it (which amounts in practice to zero percent of the time).
Our curiosities are quite healthy. They are just not bogged down in trying
to shut off debug information that gets placed into an auxiliary file
separate from the target binary and thus does not actually effect the binary
in any way. You are, however, perfectly in your right to try and find a
solution to this.
Or you might after all of that just have read this bit of doc from the WDK
documentation:
USE_PDB
The USE_PDB macro is obsolete. All binaries built by the Build utility are
built with .pdb symbol files.
Which is a hint that some of the less curious among us and perhaps more gray
haired knew exactly how to shut this off in say, the NT4 DDK, but also know
that it is not longer functional today (and for really good reasons).
But please, don’t label people as “… have[ing] forgotten what it is to be
curious.” just because they are not curious about the same topics as you;
or that they don’t choose to give of their time freely in service of your
curiosity.
Regards,
Dave Cattley
Offtopic:
WTH?
There was a guy called Anton Bassov who posted here. Who is this guy
Banton Assov?!?
–
Aram Hăvărneanu
“Aram Hăvărneanu” wrote in message news:xxxxx@ntdev…
> There was a guy called Anton Bassov who posted here. Who is this guy
> Banton Assov?!?
It’s like a joke, only smaller. Someone clearly has way too much time on
their hands (maybe now that school has started again in the US they won’t be
around as much).
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Aram Hăvărneanu” wrote in message news:xxxxx@ntdev…
> Offtopic:
>
> WTH?
>
> There was a guy called Anton Bassov who posted here. Who is this guy
> Banton Assov?!?
>
> –
> Aram Hăvărneanu
>
I dunno, but I think AB shares the same asshole as BA.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Aram Havarneanu
Sent: Friday, September 03, 2010 9:53 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] stop .debug section generation?
Offtopic:
WTH?
There was a guy called Anton Bassov who posted here. Who is this guy Banton Assov?!?
–
Aram Hăvărneanu
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Scott Noone wrote:
> Ultimately I just changed the path of my build directory so that it no
> longer had my obscene username in it, but the point >was, I wanted
> know whether it was *even possible* to get rid of the debug info.You can get rid of the path to the PDB, just look at any image from MS.
Once you drop the stupid act and post from your real name someone might
even tell you how.
Someone already has told him how to do that, he’s just not noticed or
ignored it.
Note: I’m rapidly tiring of this cute little name game.
Peter
OSR
wrote in message news:xxxxx@ntdev…
> Mark Roddy: yes “bantonassov write perfect code.” “bantonassov smash!!!”
> “bantonassov is the strongest one there is!”…when you are tri-lingual,
> come on over to my neighborhood of the net so I can make fun of your
> Russian or French.
>
> Mr. Man: I added LINKER_FLAGS=$(LINKER_FLAGS) /DEBUG:NO to my sources
> file, but got “LINK : error LNK1117: syntax error in option ‘DEBUG:NO’” I
> tried /DEBUG=NO, and that parsed, but it didn’t change anything. So if it
> was just warnings, I could live with it, but it’s actual errors.
>
> Ultimately I just changed the path of my build directory so that it no
> longer had my obscene username in it, but the point was, I wanted know
> whether it was even possible to get rid of the debug info. It looks like
> it’s not, or just no one knows how, which is fine. I accept the logic of
> the people who said it is good to have in there for if I need to debug a
> free build, but really this is just a hobby hardware interface project, so
> I’m not responsible for supporting anyone. I guess the all the time-clock
> punchers who write drivers for a living have forgotten what it is to be
> curious.
>
> BA
>
Well. just get this thingie and run with /rpdb switch. It will remove the
pdb path.
http://www.codeproject.com/KB/install/verpatch.aspx
–pa
I’m all for using Pavel’s tool over the close to incomprehensible binpath,
but just for the sake of completeness, binpath can be used to do this.
Somehow.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Friday, September 03, 2010 3:29 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] stop .debug section generation?
wrote in message news:xxxxx@ntdev…
> Mark Roddy: yes “bantonassov write perfect code.” “bantonassov smash!!!”
> “bantonassov is the strongest one there is!”…when you are
> tri-lingual, come on over to my neighborhood of the net so I can make
> fun of your Russian or French.
>
> Mr. Man: I added LINKER_FLAGS=$(LINKER_FLAGS) /DEBUG:NO to my sources
> file, but got “LINK : error LNK1117: syntax error in option
> ‘DEBUG:NO’” I tried /DEBUG=NO, and that parsed, but it didn’t change
> anything. So if it was just warnings, I could live with it, but it’s
actual errors.
>
> Ultimately I just changed the path of my build directory so that it no
> longer had my obscene username in it, but the point was, I wanted know
> whether it was even possible to get rid of the debug info. It looks
> like it’s not, or just no one knows how, which is fine. I accept the
> logic of the people who said it is good to have in there for if I need
> to debug a free build, but really this is just a hobby hardware
> interface project, so I’m not responsible for supporting anyone. I
> guess the all the time-clock punchers who write drivers for a living
> have forgotten what it is to be curious.
>
> BA
>
Well. just get this thingie and run with /rpdb switch. It will remove the
pdb path.
http://www.codeproject.com/KB/install/verpatch.aspx
–pa
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer