[
https://issues.apache.org/jira/browse/LOG4NET-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868025#comment-13868025
]
Paul H. Harder II commented on LOG4NET-287:
-------------------------------------------
Actually, it isn't a remote service. I'm running it as a Windows Service on my
PC while I develop it. It'll run on a server after release to production. So,
while I run on my PC, I can run the debug-compiled version and attach to it
from Visual Studio. When I do this, the breakpoints that I set are working as
expected and log4net records correct line numbers. When I do that, I make sure
to deploy the debug version of the PDB files. When I build the release version
and deploy the release version PDB files, I can't attach to the service with
Visual Studio (naturally) and the line numbers that get recorded are incorrect.
Just on a whim, I tried deploying the debug version PDB files with the release
version DLLs, and (of course) all of the line numbers were recorded as zero.
So this gives me confidence that, when I think I'm deploying the release
version PDBs with the release version DLLs, then that is actually what is
happening. But log4net records incorrect line numbers.
> 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)
