• =?UTF-8?B?Tm9yZGzDtnc=?= (5/5) Jan 28 2016 After upgrading to 2.070.0 I get an assert failure in my
• Vladimir Panteleev (4/10) Jan 28 2016 You can use Digger to find the exact compiler change that caused
• =?UTF-8?B?Tm9yZGzDtnc=?= (3/17) Jan 28 2016 My "app" is ca 30klines...
• =?UTF-8?B?Tm9yZGzDtnc=?= (6/10) Jan 28 2016 Thanks, I'm aware of these tools.
• Benjamin Thaut (6/10) Jan 29 2016 Which platform are you on? Are all your binaries compiled with

=?UTF-8?B?Tm9yZGzDtnc=?= <per.nordlow gmail.com> writes:

After upgrading to 2.070.0 I get an assert failure in my 
application that wasn't there before:

core.exception.AssertError knet/linking.d(235): Assertion failure

Why isn't there any stacktrace? I thought has been fixed.

Please help.

Vladimir Panteleev <thecybershadow.lists gmail.com> writes:

On Thursday, 28 January 2016 at 18:01:09 UTC, Nordlöw wrote:
 After upgrading to 2.070.0 I get an assert failure in my 
 application that wasn't there before:

 core.exception.AssertError knet/linking.d(235): Assertion 
 failure

 Why isn't there any stacktrace? I thought has been fixed.

 Please help.

You can use Digger to find the exact compiler change that caused 
this assert to manifest, and Dustmite to find the minimal program 
which behaves differently in two compiler versions.

=?UTF-8?B?Tm9yZGzDtnc=?= <per.nordlow gmail.com> writes:

On Thursday, 28 January 2016 at 18:13:59 UTC, Vladimir Panteleev 
wrote:
 On Thursday, 28 January 2016 at 18:01:09 UTC, Nordlöw wrote:
 After upgrading to 2.070.0 I get an assert failure in my 
 application that wasn't there before:

 core.exception.AssertError knet/linking.d(235): Assertion 
 failure

 Why isn't there any stacktrace? I thought has been fixed.

 Please help.

 You can use Digger to find the exact compiler change that 
 caused this assert to manifest, and Dustmite to find the 
 minimal program which behaves differently in two compiler 
 versions.

My "app" is ca 30klines...

=?UTF-8?B?Tm9yZGzDtnc=?= <per.nordlow gmail.com> writes:

On Thursday, 28 January 2016 at 18:13:59 UTC, Vladimir Panteleev 
wrote:
 You can use Digger to find the exact compiler change that 
 caused this assert to manifest, and Dustmite to find the 
 minimal program which behaves differently in two compiler 
 versions.

Thanks, I'm aware of these tools.

But it's easier to use the stacktrace...if I only get one. The 
function where the assert() is called is, in turn, called in 
hundreds of places.

Benjamin Thaut <code benjamin-thaut.de> writes:

On Thursday, 28 January 2016 at 18:33:19 UTC, Nordlöw wrote:
 Thanks, I'm aware of these tools.

 But it's easier to use the stacktrace...if I only get one. The 
 function where the assert() is called is, in turn, called in 
 hundreds of places.

Which platform are you on? Are all your binaries compiled with 
debug symbols? If one or multiple functions on the stack are 
within phobos or druntime you might not have debug symbols for 
phobos or druntime. Using inline asm might also destroy your 
stack frames.