I prefer debugging the situation live.Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a slight tweak in the project settings.
On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski <[email protected]>wrote: > Have you tried specifying a custom error handler on the appender to track > down when it enters a failed state? > > <appender name=".." > > ... > <errorHandler type="Your.ErrorHandler, YourAssembly" /> > </appender> > > You would write one that sends an email when the file can't be created. > > ------------------------------ > *From:* Omer Mor <[email protected]> > *To:* [email protected] > *Sent:* Thursday, August 6, 2009 3:02:17 AM > *Subject:* Debugging log4net source > > Hi, > to research a (rare) bug we have with log4net (log file is not being > created) we wanted to debug its source. > However, the release build of 1.2.10 is supplied without a pdb file. > And since it is a signed assembly we can't compile it ourself and replace > it. > Also - the debug build of 1.2.10 is supplied with a pdb, but is not signed, > so it is not substitutable. > What I'd like to ask is that one of the developers compile a release build > of 1.2.10 and enable pdb creation, so that we could debug the source. > > Using a non-signed copy of log4net is not an option for us, because some of > our 3rd-party assemblies are compiled against the signed 1.2.10 log4net > assembly. > > The files could be sent irectly to me at [email protected] . > > Thanks in advance, > Omer Mor. >
