cleaning up BASE RELOCATIONS in fre build

Greetings,

while looking at my driver free build with dumbin I see that it lists
internal function names in the BASE RELOCATIONS section of the header file.
I have have also tested the tracedrv ddk ( 3790 ) sample and which shows
similar information in its free build.

BASE RELOCATIONS #7
0 RVA, 78 SizeOfBlock
552 HIGHLOW 00010888 __imp__ExAllocatePoolWithTag@12
5C9 HIGHLOW 00010884 __imp__IoWMIWriteEvent@4
[…]
CFE HIGHLOW 00010C24 _TracedrvDriverUnload@4
D05 HIGHLOW 00010B56 _TracedrvDispatchDeviceControl@8

I have however seen drivers that do not show any name at all in the BASE
RELOCATIONS area. I have tested all compile/linker/build options I could
think of but I cannot seem to get rid of the names.

I’d like my free build driver to show as little information as possible;
ideas and comments and very welcome.

thanks,


Marco [www.neovalens.com]

One used to be able to do this using rebase.exe from the sdk. I have no
idea if it is still supported. Personally I think this is not a good
idea. System crashes containing your driver’s code in various stack
traces will be indecipherable.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Marco Peretti
Sent: Monday, December 12, 2005 11:54 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] cleaning up BASE RELOCATIONS in fre build

Greetings,

while looking at my driver free build with dumbin I see that it lists
internal function names in the BASE RELOCATIONS section of the header
file.
I have have also tested the tracedrv ddk ( 3790 ) sample and which shows

similar information in its free build.

BASE RELOCATIONS #7
0 RVA, 78 SizeOfBlock
552 HIGHLOW 00010888 __imp__ExAllocatePoolWithTag@12
5C9 HIGHLOW 00010884 __imp__IoWMIWriteEvent@4
[…]
CFE HIGHLOW 00010C24 _TracedrvDriverUnload@4
D05 HIGHLOW 00010B56 _TracedrvDispatchDeviceControl@8

I have however seen drivers that do not show any name at all in the BASE

RELOCATIONS area. I have tested all compile/linker/build options I could

think of but I cannot seem to get rid of the names.

I’d like my free build driver to show as little information as possible;

ideas and comments and very welcome.

thanks,


Marco [www.neovalens.com]


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Well, if they develop PERFECT code guaranteed to NEVER EVER throw a fit
and crash the system, then it is PERFECTLY ok. Of course, the alternative
is that their code is so crappy they want to make sure no one ever finds
them. :slight_smile:

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Monday, December 12, 2005 11:57 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] cleaning up BASE RELOCATIONS in fre build

One used to be able to do this using rebase.exe from the sdk. I have no
idea if it is still supported. Personally I think this is not a good
idea. System crashes containing your driver’s code in various stack
traces will be indecipherable.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Marco Peretti
Sent: Monday, December 12, 2005 11:54 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] cleaning up BASE RELOCATIONS in fre build

Greetings,

while looking at my driver free build with dumbin I see that it lists
internal function names in the BASE RELOCATIONS section of the header
file.
I have have also tested the tracedrv ddk ( 3790 ) sample and which shows

similar information in its free build.

BASE RELOCATIONS #7
0 RVA, 78 SizeOfBlock
552 HIGHLOW 00010888 __imp__ExAllocatePoolWithTag@12
5C9 HIGHLOW 00010884 __imp__IoWMIWriteEvent@4
[…]
CFE HIGHLOW 00010C24 _TracedrvDriverUnload@4
D05 HIGHLOW 00010B56 _TracedrvDispatchDeviceControl@8

I have however seen drivers that do not show any name at all in the BASE

RELOCATIONS area. I have tested all compile/linker/build options I could

think of but I cannot seem to get rid of the names.

I’d like my free build driver to show as little information as possible;

ideas and comments and very welcome.

thanks,


Marco [www.neovalens.com]


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Mark,

I have indeed used rebase when compiling with an older DDK but it does not
seem to work when using the latest DDK.

>System crashes containing your driver’s code in various stack
traces will be indecipherable<<

I did not know that. Sounds like good-enough argument to give up and leave
the free build as it is.

thanks,

Marco

“Roddy, Mark” wrote in message news:xxxxx@ntdev…
One used to be able to do this using rebase.exe from the sdk. I have no
idea if it is still supported. Personally I think this is not a good
idea. System crashes containing your driver’s code in various stack
traces will be indecipherable.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Marco Peretti
Sent: Monday, December 12, 2005 11:54 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] cleaning up BASE RELOCATIONS in fre build

Greetings,

while looking at my driver free build with dumbin I see that it lists
internal function names in the BASE RELOCATIONS section of the header
file.
I have have also tested the tracedrv ddk ( 3790 ) sample and which shows

similar information in its free build.

BASE RELOCATIONS #7
0 RVA, 78 SizeOfBlock
552 HIGHLOW 00010888 imp ExAllocatePoolWithTag@12
5C9 HIGHLOW 00010884 imp IoWMIWriteEvent@4
[…]
CFE HIGHLOW 00010C24 _TracedrvDriverUnload@4
D05 HIGHLOW 00010B56 _TracedrvDispatchDeviceControl@8

I have however seen drivers that do not show any name at all in the BASE

RELOCATIONS area. I have tested all compile/linker/build options I could

think of but I cannot seem to get rid of the names.

I’d like my free build driver to show as little information as possible;

ideas and comments and very welcome.

thanks,


Marco [www.neovalens.com]



Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Mark,

it turns out that the information is not in the driver. dumbin grabbed
function names, and other information, from the release directory. When I
delete all files but the sys file and run dumbin the output is what I
expected in the first place.

cheers,


Marco [www.neovalens.com]

“Roddy, Mark” wrote in message news:xxxxx@ntdev…
One used to be able to do this using rebase.exe from the sdk. I have no
idea if it is still supported. Personally I think this is not a good
idea. System crashes containing your driver’s code in various stack
traces will be indecipherable.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Marco Peretti
Sent: Monday, December 12, 2005 11:54 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] cleaning up BASE RELOCATIONS in fre build

Greetings,

while looking at my driver free build with dumbin I see that it lists
internal function names in the BASE RELOCATIONS section of the header
file.
I have have also tested the tracedrv ddk ( 3790 ) sample and which shows

similar information in its free build.

BASE RELOCATIONS #7
0 RVA, 78 SizeOfBlock
552 HIGHLOW 00010888 imp ExAllocatePoolWithTag@12
5C9 HIGHLOW 00010884 imp IoWMIWriteEvent@4
[…]
CFE HIGHLOW 00010C24 _TracedrvDriverUnload@4
D05 HIGHLOW 00010B56 _TracedrvDispatchDeviceControl@8

I have however seen drivers that do not show any name at all in the BASE

RELOCATIONS area. I have tested all compile/linker/build options I could

think of but I cannot seem to get rid of the names.

I’d like my free build driver to show as little information as possible;

ideas and comments and very welcome.

thanks,


Marco [www.neovalens.com]



Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com