[
https://issues.apache.org/jira/browse/LOG4NET-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868252#comment-13868252
]
Daniel Kugel commented on LOG4NET-287:
--------------------------------------
I would still suggest to try and [debug/remote
debug|http://msdn.microsoft.com/en-us/library/y7f5zaaa.aspx] to make sure the
correct PDB files are loaded.
The line offset is probably caused by optimizations made by the compiler. You
can test this by clearing the "Optimize Code" check box under the Build tab for
the Release configuration in the project properties window in Visual Studio and
creating an ini file with the name of each exe or dll file you have with the
extensions renamed to ini placing it in the same folder where the service is
loaded from.
That is if you have MyService.exe or MyService.dll file create a MyService.ini
file with the text:
{quote}
\[.NET Framework Debugging Control\]
GenerateTrackingInfo=1
AllowOptimize=0
{quote}
> Wrong line number for log
> --------------------------
>
> Key: LOG4NET-287
> URL: https://issues.apache.org/jira/browse/LOG4NET-287
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: Windows XP, .NET 3.5, Microsot Virsual Studio
> Reporter: Shuang yin Liu
>
> In our project, we use the line number function of log4net. Many of log line
> numbers are 1 line after the actual line. Other are 2 or 3 lines gap(when
> exception log is written or at the end of the main application).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
