sybrandy wrote:
> 1) I use the current core.thread library and put all my messages in a
> buffer that the thread checks periodically, pulls off a new message, and
> then writes it to a file. There will be some work to make sure nothing
> collides with each other, but I think I can manage it.
Woul
strtr Wrote:
> dmd(1.048/55/56) crashed on me:
> I've also tried finding which part of the code is responsible, but I haven't
> found it yet.
I keep forgetting my best method yet : compiling module by module until
something strange comes up, or in this case, the compiler chokes.
Seems to be r
Hello Strtr,
-v ended like this :
semantic Cg_shader
semantic abgr
semantic bgra
seman
This is code within Derelict I think.
Strange sudden break..
Stopping mid word makes me think that the output buffer didn't get flushed
so something failed after the next to last line, but you don't know
BCS Wrote:
> Hello Strtr,
>
>
> If you can try it on linux it's not to hard to build a debug version of dmd
> and run it under the debugger. That will at least give you a filename/line
> number for the bug report and with a little thinking and a stack trace you
> can take a guess at what code
Don Wrote:
> strtr wrote:
> > dmd(1.048/55/56) crashed on me:
> > AppName: dmd.exe AppVer: 0.0.0.0 ModName: unknown
> > ModVer: 0.0.0.0 Offset: 0002
> > There is a lot of crash data but I do not know where to start looking.
> > I've also tried finding which part of the code is
Lutger wrote:
Does anybody get this with 2.040? I couldn't find a bug report about it,
so maybe it is due to my setup.
// in file test.d:
assert(false);
output: core.exception.asserter...@l(5): Assertion failure
^ not the right file
There has been a bug wit
Hello,
Since I'm continuing to write software in D (no, nothing special...just
pet projects) I felt that I needed to create a library to handle logging
to a file. I have a good start and it seems to work pretty well. I
even have a couple ideas left to implement to make it better, however
I'
Do I understand module level access rights correctly, or is there a dmd bug?
Instead of coming up with an example, I will use a Phobos class:
std.demangle.MangleException is private in its module; yet I can use it
in my program:
import std.demangle;
void main()
{
auto me = new MangleExce
Hello Strtr,
dmd(1.048/55/56) crashed on me:
AppName: dmd.exe AppVer: 0.0.0.0 ModName: unknown
ModVer: 0.0.0.0 Offset: 0002
There is a lot of crash data but I do not know where to start looking.
I've also tried finding which part of the code is responsible, but I
haven't fou
strtr wrote:
dmd(1.048/55/56) crashed on me:
AppName: dmd.exe AppVer: 0.0.0.0 ModName: unknown
ModVer: 0.0.0.0 Offset: 0002
There is a lot of crash data but I do not know where to start looking.
I've also tried finding which part of the code is responsible, but I haven't
fou
Does anybody get this with 2.040? I couldn't find a bug report about it,
so maybe it is due to my setup.
// in file test.d:
assert(false);
output: core.exception.asserter...@l(5): Assertion failure
^ not the right file
// in file test.d:
assert(false, "ok");
11 matches
Mail list logo
