lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Van Den Berghe, Vincent" <>
Subject release mode
Date Mon, 12 Jun 2017 13:55:00 GMT
Hello everyone,

I'm seeing the following in AssemblyInfo.cs:

// LUCENENET NOTE: This attribute is required to disable optimizations so the
// Lucene.Net.Tests.Index.TestIndexWriterExceptions.TestExceptionsDuringCommit() test
// can read the stack trace information, otherwise the test fails.
[assembly: Debuggable(DebuggableAttribute.DebuggingModes.Default | DebuggableAttribute.DebuggingModes.DisableOptimizations)]

This effectively disables optimizations in release mode.
However, removing this attribute is removed doesn't seem to affect the "TestExceptionsDuringCommit"
test. Moreover, this test doesn't seem to read stack trace information, unless there is something
that I'm missing.

If stack trace information is needed in release mode, one could consider generating PDB information.
Yes, optimization will sometimes cause the information to be incorrect, but the probability
of having bugs in release mode that can't be reproduced in debug mode is relatively small,

What say the esteemed colleages?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message