RejectedSoftware Forums

Sign up

Segfault somehow related to core.log

Hello,

I get after about 24h of running the following segfault:

http://dpaste.dzfl.pl/8409386a83b6

Problem is, this stack trace is quite useless. At this point I don't even know if this is a bug in my or in vibes code. Does anyone have any hints for me on how to get more information about this problem?

It says an assert failed but neither which file nor in which line :/

cheers,

--Marenz

Re: Segfault somehow related to core.log

On Thu, 04 Dec 2014 20:33:45 GMT, Marenz wrote:

Hello,

I get after about 24h of running the following segfault:

http://dpaste.dzfl.pl/8409386a83b6

Problem is, this stack trace is quite useless. At this point I don't even know if this is a bug in my or in vibes code. Does anyone have any hints for me on how to get more information about this problem?

It says an assert failed but neither which file nor in which line :/

cheers,

--Marenz

Which version of windows / are you using ?
Did you compile in release or debug mode ? From the stack trace, it looks like release, so is it a possibility to reproduce (or try to) the same bug in debug mode ?

Re: Segfault somehow related to core.log

param1=<error reading variable: Cannot access memory at address 0xffffffffffffffe0>, fmt=<error reading variable: Cannot access memory at address 0xfffffffffffffff0>) at ../../.dub/packages/vibe-d-0.7.21-rc.3/source/vibe/core/log.d:116

There's a warning commented about 2 lines below:

116: foreach (l; getLoggers())
117: if (l.minLevel <= level) { // WARNING: TYPE SYSTEM HOLE: accessing field of shared class!

Might be a good idea to fix this before looking into it more

Re: Segfault somehow related to core.log

On Fri, 05 Dec 2014 08:14:47 GMT, Mathias LANG wrote:

On Thu, 04 Dec 2014 20:33:45 GMT, Marenz wrote:

Hello,

I get after about 24h of running the following segfault:

http://dpaste.dzfl.pl/8409386a83b6

Problem is, this stack trace is quite useless. At this point I don't even know if this is a bug in my or in vibes code. Does anyone have any hints for me on how to get more information about this problem?

It says an assert failed but neither which file nor in which line :/

cheers,

--Marenz

Which version of windows / are you using ?
Did you compile in release or debug mode ? From the stack trace, it looks like release, so is it a possibility to reproduce (or try to) the same bug in debug mode ?

I was using a 64bit linux (debian).
I just checked and while I had

"buildOptions" : ["debugInfoC"]

enabled, that apparently is still not the real debug mode which requires

"buildOptions" : ["debugInfoC", "debugMode"]

At least I believe so.