On 24-Dec-15 19:46, Magnus Therning wrote:
I'm *not* mixing stuff built with `-g` and stuff built without it.
Actually I don't see anything bad about mixing `-g` code with code
without `-g`.
I'm
also *not* mixing linking with debug- and non-debug libraries.
Since we cover a lot of aspects
David Cole writes:
> Not only is it possible ... it WILL happen if you use the Microsoft
> C++ compiler and try to mix and match Release and Debug compilation
> units.
>
> The MS compiler has some very nice memory tracking facilities built
> into the Debug runtime libraries, but it is
Ruslan Baratov writes:
> On 22-Dec-15 04:07, Magnus Therning wrote:
>> Ruslan Baratov writes:
>>
>>> On 20-Dec-15 01:31, Magnus Therning wrote:
Ruslan Baratov writes:
> How about using RelWithDebInfo? See:
> http://stackoverflow.com/a/28124715/2288008
Hmm, I'm probably
On 22-Dec-15 04:07, Magnus Therning wrote:
Ruslan Baratov writes:
On 20-Dec-15 01:31, Magnus Therning wrote:
Ruslan Baratov writes:
How about using RelWithDebInfo? See:
http://stackoverflow.com/a/28124715/2288008
Hmm, I'm probably missing something but how does that solve the issue
with
Not only is it possible ... it WILL happen if you use the Microsoft
C++ compiler and try to mix and match Release and Debug compilation
units.
The MS compiler has some very nice memory tracking facilities built
into the Debug runtime libraries, but it is accomplished via different
structs for
On 20-Dec-15 01:31, Magnus Therning wrote:
Ruslan Baratov writes:
How about using RelWithDebInfo? See:
http://stackoverflow.com/a/28124715/2288008
Hmm, I'm probably missing something but how does that solve the issue
with some targets requiring NDEBUG to be *undefined* and other targets
Ruslan Baratov writes:
> On 20-Dec-15 01:31, Magnus Therning wrote:
>> Ruslan Baratov writes:
>>
>>> How about using RelWithDebInfo? See:
>>> http://stackoverflow.com/a/28124715/2288008
>> Hmm, I'm probably missing something but how does that solve the issue
>> with some targets requiring NDEBUG
Dave Flogeras writes:
> On Fri, Dec 18, 2015 at 9:55 AM, Magnus Therning wrote:
>>
>> I'm sure I'm not the first one to run into the conflict between a
>> desire to test the code shipped to customers and the desire to at the
>> same time define NDEBUG to make sure tests
Ruslan Baratov writes:
> How about using RelWithDebInfo? See:
> http://stackoverflow.com/a/28124715/2288008
Hmm, I'm probably missing something but how does that solve the issue
with some targets requiring NDEBUG to be *undefined* and other targets
requiring NDEBUG to be defined?
/M
> On
On Fri, Dec 18, 2015 at 9:55 AM, Magnus Therning wrote:
>
> I'm sure I'm not the first one to run into the conflict between a desire
> to test the code shipped to customers and the desire to at the same time
> define NDEBUG to make sure tests don't have their `assert` turned
I'm sure I'm not the first one to run into the conflict between a desire
to test the code shipped to customers and the desire to at the same time
define NDEBUG to make sure tests don't have their `assert` turned into
NOOPs.
Is there some nice way of handling this?
I can always remove -DNDEBUG
How about using RelWithDebInfo? See:
http://stackoverflow.com/a/28124715/2288008
Ruslo
On 18-Dec-15 20:55, Magnus Therning wrote:
I'm sure I'm not the first one to run into the conflict between a desire
to test the code shipped to customers and the desire to at the same time
define NDEBUG to
12 matches
Mail list logo