Open an issue for --enable-debug binaries?

["CHOU, PETER" <pc...@att.com>]

Hi,

Should I open an issue for a fault, such as an assertion failure, that only happens with binaries compiled with the '-enable-debug' option?

I thought this just affected the compiler optimization options, but perhaps something logically is being changed?

Although I usually only use this option on my development box, we have run binaries with this option in production for short periods of time to get better debug information within core-dumps.

Thanks,
Peter Chou

Re: Open an issue for --enable-debug binaries?

[Leif Hedstrom <zw...@apache.org>]

> On Jan 24, 2022, at 2:37 PM, CHOU, PETER <pc...@att.com> wrote:
> 
> Hi,
> 
> Should I open an issue for a fault, such as an assertion failure, that only happens with binaries compiled with the '-enable-debug' option?

Right, most of our assertions are (and should be!) debug only assertions. This is as intended. As a side note, we’ve been using “release asserts” to frivolously IMO :).

> 
> I thought this just affected the compiler optimization options, but perhaps something logically is being changed?

No, it’s always been this way, debug builds enables all asserts. If you are running into an assert, there’s almost certain to be a bug in the code. There *could* be assertions that are wrong, but that’s (hopefully) not very common, and if it is, we obviously need to remove that assertion.

— Leif


> 
> Although I usually only use this option on my development box, we have run binaries with this option in production for short periods of time to get better debug information within core-dumps.
> 
> Thanks,
> Peter Chou