Stripped PDB files for beta and RC releases?

[SnakeByte]

You know I've asked for PDB files in the past, and I never got a response, likely because there is concern it will get released to the public and allow for easy reverse engineering of the app (I guess, the worry being someone will disable the registration stuff).

Visual studio also has the ability to create stripped PDB files. Read here on how to create these special files:
http://msdn.microsoft.com/en-us/library/windows/desktop/ee416588(v=vs.85).aspx

Normally a full PDB file gives this info:

Public symbols (typically all functions, static and global variables)
A list of object files that are responsible for sections of code in the executable
Frame pointer optimization information (FPO)
Name and type information for local variables and data structures
Source file and line number information

However, a stripped pdb file only gives this:

Public symbols (typically only non-static functions and global variables)
A list of object files that are responsible for sections of code in the executable
Frame pointer optimization information (FPO)

Hopefully this will quiet any worries?

Otherwise, maybe release beta's and Rc's with an expiration date instead of including the registration code and then include the full PDB?

[SnakeByte]

Also, in reply to dexter not finding the eip and stack info I've been reporting that helpful, this may help to shed some light on how to find where the assembler is in the source code:

http://stackoverflow.com/questions/1020498/how-to-view-the-assembly-behind-the-code-using-visual-c

I haven't used Visual Studio in ages so maybe I'm not remembering this correctly, but I thought it was possible to set a breakpoint on EIP when viewing the assembler window?

I know you can do it with Window's free debugger.

[Quade]

Not ignoring this. Thinking about it.

[biosteel]

As a user preferring to run beta/rc builds when they do the job, please do not put expiration dates on them Quade, thanks!