• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 632
  • Last Modified:

How to create a release build with debug set to pdbonly

Hello experts:

I am trying to isolate some trouble areas in an application that is currently in production and I've been advised to set debug equal to pdbonly so that I will have line numbers returns in my exception logging.  I currently have the production build in release mode with optimization, but I'm not sure how to change the debug value to pdbonly.

I am developing using C# in the 2.x Framework.

Any help is greatly appreciated...
0
escheider
Asked:
escheider
  • 3
  • 2
1 Solution
 
gregoryyoungCommented:
A release build is by default pdbonly the question is whether you copy over the .pdb files or not.
0
 
escheiderAuthor Commented:
The .pdb files are currently in our test and qa environments, but are not in the production environment.   If pdbonly is the default, then how can I extract the stack trace that will contain the line number of the offending line of code [although I am aware that optimization will not make this an exact science]?

I am using a custom webservice to handle the logging, but here is what I am using to obtain the information I'm logging:
private void LogLastError()
        {
            string pageName = Request.Url.Segments[Request.Url.Segments.Length - 1];
            objErr = Server.GetLastError().GetBaseException();
 
            string err = pageName.PadRight(50) + "|" + Session["sessionid"] + "|" + objErr.Message + "|" + objErr.StackTrace;
 
            Logger.LogError(objErr, err);
            Server.ClearError();
        }

Open in new window

0
 
gregoryyoungCommented:
"The .pdb files are currently in our test and qa environments, but are not in the production environment.  "

Copy the pdbs to your production ... The simplest mechanism is to temporarily copy them to production

personally I would not do this ... I would take a memory dump at the offending time then load it up with the pdbs in the debugger but this is a pretty complex process and probably not one you want to learn....


Cheers,

Greg
0
 
escheiderAuthor Commented:
Greg:

If the pdbs are the answer, then why am I not getting the line numbers in the test and qa environments running the identical release build?  Test, QA and Prod are identical environments.
0
 
escheiderAuthor Commented:
Greg:

I have moved the pdbs to production and I am now receiving the stack trace I desired.  Thanks for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now