On Tuesday, 11 June 2013 at 12:40:23 UTC, Andrei Alexandrescu
wrote:
Well Jerry can help. Jerry? Nazriel, if you want me to attach
the binary I produced, sure, I can do that. But that works...
Andrei
Thanks to your authority, your posts are more visible than mine
that's why I asked for hel
"nazriel" writes:
> On Tuesday, 11 June 2013 at 06:00:01 UTC, Andrei Alexandrescu wrote:
>> On 6/11/13 12:22 AM, Andrei Alexandrescu wrote:
>>> On 6/10/13 6:10 PM, Jerry wrote:
[pid 23169]
open("/home/jlquinn/dmd2/linux/bin64/../lib64/libphobos2.a",
O_RDONLY|O_CLOEXEC) = 11
>>>
>>>
On 6/11/13 5:17 AM, nazriel wrote:
On Tuesday, 11 June 2013 at 06:00:01 UTC, Andrei Alexandrescu wrote:
On 6/11/13 12:22 AM, Andrei Alexandrescu wrote:
On 6/10/13 6:10 PM, Jerry wrote:
[pid 23169]
open("/home/jlquinn/dmd2/linux/bin64/../lib64/libphobos2.a",
O_RDONLY|O_CLOEXEC) = 11
OK, so it
On Tuesday, 11 June 2013 at 06:00:01 UTC, Andrei Alexandrescu
wrote:
On 6/11/13 12:22 AM, Andrei Alexandrescu wrote:
On 6/10/13 6:10 PM, Jerry wrote:
[pid 23169]
open("/home/jlquinn/dmd2/linux/bin64/../lib64/libphobos2.a",
O_RDONLY|O_CLOEXEC) = 11
OK, so it seems this is the cause. I'm trying
On 6/11/13 12:22 AM, Andrei Alexandrescu wrote:
On 6/10/13 6:10 PM, Jerry wrote:
[pid 23169]
open("/home/jlquinn/dmd2/linux/bin64/../lib64/libphobos2.a",
O_RDONLY|O_CLOEXEC) = 11
OK, so it seems this is the cause. I'm trying to repro it on a fresh
Ubuntu 12.10 VM. So at least two bugs:
1. We
Walter Bright writes:
> On 6/10/2013 9:52 AM, Jerry wrote:
>>> 5. Does gdb reveal anything interesting?
>>
>> Unfortunately there's no debugging symbols in _d_dso_registry(). I
>> assume the compiler is writing asm directly.
>
> Use the 'disassemble' command starting at _d_dso_registry, and poin
On 6/10/13 6:10 PM, Jerry wrote:
[pid 23169] open("/home/jlquinn/dmd2/linux/bin64/../lib64/libphobos2.a",
O_RDONLY|O_CLOEXEC) = 11
OK, so it seems this is the cause. I'm trying to repro it on a fresh
Ubuntu 12.10 VM. So at least two bugs:
1. We link dynamically by default at least on some s
On 6/9/2013 11:41 PM, Jerry wrote:
LD_LIBRARY_PATH is empty. I've now reproduced this segfault on a Debian
testing machine as well as my Ubuntu one. I'm pretty confused.
LD_LIBRARY_PATH only applies to shared libraries.
On 6/10/2013 9:52 AM, Jerry wrote:
5. Does gdb reveal anything interesting?
Unfortunately there's no debugging symbols in _d_dso_registry(). I
assume the compiler is writing asm directly.
Use the 'disassemble' command starting at _d_dso_registry, and point out which
instruction is faulting.
I just started having this problem as well, however it appears
whether I'm using the latest DMD or older versions (I only tried
as far back as 2.060). Like others, the program compiled with
2.063 dies at _d_dso_registry(). The programs compiled with
previous versions die at gc_init().
I've
Walter Bright writes:
> On 6/10/2013 2:56 PM, Walter Bright wrote:
>> On 6/10/2013 2:38 PM, nazriel wrote:
>>> On Monday, 10 June 2013 at 21:33:20 UTC, Walter Bright wrote:
On 6/10/2013 2:28 PM, nazriel wrote:
>> program was compiled with dmd (2.063) using the following flags: -g
>>
On 6/10/2013 2:38 PM, nazriel wrote:
On Monday, 10 June 2013 at 21:33:20 UTC, Walter Bright wrote:
On 6/10/2013 2:28 PM, nazriel wrote:
program was compiled with dmd (2.063) using the following flags: -g -debug
-unittest
I suspected it may be the problem with shared libraries.
Can you try com
On 6/10/2013 2:56 PM, Walter Bright wrote:
On 6/10/2013 2:38 PM, nazriel wrote:
On Monday, 10 June 2013 at 21:33:20 UTC, Walter Bright wrote:
On 6/10/2013 2:28 PM, nazriel wrote:
program was compiled with dmd (2.063) using the following flags: -g -debug
-unittest
I suspected it may be the pr
On Monday, 10 June 2013 at 21:33:20 UTC, Walter Bright wrote:
On 6/10/2013 2:28 PM, nazriel wrote:
program was compiled with dmd (2.063) using the following
flags: -g -debug
-unittest
I suspected it may be the problem with shared libraries.
Can you try compiling that hello world with static l
On 6/10/2013 2:28 PM, nazriel wrote:
program was compiled with dmd (2.063) using the following flags: -g -debug
-unittest
I suspected it may be the problem with shared libraries.
Can you try compiling that hello world with static libphobos?
Or can you attach your segfaulting binary?
Staticall
On Monday, 10 June 2013 at 18:50:21 UTC, Brandon wrote:
On Monday, 10 June 2013 at 16:52:51 UTC, Jerry wrote:
No, same problem. BTW, it's segfaulting in _d_dso_registry()
before
main() gets run.
4. If you make any other calls into the stdlib aside from
I/O, do they
work?
It doesn't matter
On Monday, 10 June 2013 at 16:52:51 UTC, Jerry wrote:
No, same problem. BTW, it's segfaulting in _d_dso_registry()
before
main() gets run.
4. If you make any other calls into the stdlib aside from I/O,
do they
work?
It doesn't matter. The following program segfaults:
void main() {}
5.
Andrei Alexandrescu writes:
> On 6/10/13 2:41 AM, Jerry wrote:
>> "Andrei Alexandrescu" writes:
>>
>>> On Sunday, 9 June 2013 at 17:23:16 UTC, Andrei Alexandrescu wrote:
On Sunday, 9 June 2013 at 17:22:36 UTC, Andrei Alexandrescu wrote:
> On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry
"John Colvin" writes:
> On Monday, 10 June 2013 at 06:41:39 UTC, Jerry wrote:
>>
>> LD_LIBRARY_PATH is empty. I've now reproduced this segfault on a Debian
>> testing machine as well as my Ubuntu one. I'm pretty confused.
>>
>> Jerry
>
> I can't reproduce this anywhere. What's the output for th
On Tuesday, 4 June 2013 at 18:03:53 UTC, Jerry wrote:
Hi folks,
I've downloaded the current dmd 2.063 zip and tried it out.
This is
Ubuntu 12.10 x86_64. Every program I compile segfaults when I
try to
run it. As a simple example:
jlquinn@wyvern:~/re/test$ cat junk.d
import std.stdio;
void
On 6/10/13 2:41 AM, Jerry wrote:
"Andrei Alexandrescu" writes:
On Sunday, 9 June 2013 at 17:23:16 UTC, Andrei Alexandrescu wrote:
On Sunday, 9 June 2013 at 17:22:36 UTC, Andrei Alexandrescu wrote:
On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry wrote:
jlquinn@wyvern:~/re/test$ /home/jlquin
On Monday, 10 June 2013 at 06:41:39 UTC, Jerry wrote:
"Andrei Alexandrescu" writes:
On Sunday, 9 June 2013 at 17:23:16 UTC, Andrei Alexandrescu
wrote:
On Sunday, 9 June 2013 at 17:22:36 UTC, Andrei Alexandrescu
wrote:
On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry wrote:
jlquinn@wyvern:~/r
"Andrei Alexandrescu" writes:
> On Sunday, 9 June 2013 at 17:23:16 UTC, Andrei Alexandrescu wrote:
>> On Sunday, 9 June 2013 at 17:22:36 UTC, Andrei Alexandrescu wrote:
>>> On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry wrote:
jlquinn@wyvern:~/re/test$ /home/jlquinn/dmd2/linux/bin64/dmd -v
On Sunday, 9 June 2013 at 17:23:16 UTC, Andrei Alexandrescu wrote:
On Sunday, 9 June 2013 at 17:22:36 UTC, Andrei Alexandrescu
wrote:
On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry wrote:
jlquinn@wyvern:~/re/test$ /home/jlquinn/dmd2/linux/bin64/dmd
-v -w junk.d
binary/home/jlquinn/dmd2/l
On Sunday, 9 June 2013 at 17:22:36 UTC, Andrei Alexandrescu wrote:
On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry wrote:
jlquinn@wyvern:~/re/test$ /home/jlquinn/dmd2/linux/bin64/dmd
-v -w junk.d
binary/home/jlquinn/dmd2/linux/bin64/dmd
version v2.063
[snip]
I've done a clean room atte
On Wednesday, 5 June 2013 at 02:30:37 UTC, Jerry wrote:
jlquinn@wyvern:~/re/test$ /home/jlquinn/dmd2/linux/bin64/dmd -v
-w junk.d
binary/home/jlquinn/dmd2/linux/bin64/dmd
version v2.063
[snip]
I've done a clean room attempt at reproducing the bug, was unable
to. Jerry, anything you can
On 6/4/13 10:30 PM, Jerry wrote:
jlquinn@wyvern:~/re/test$ /home/jlquinn/dmd2/linux/bin64/dmd -v -w junk.d
binary/home/jlquinn/dmd2/linux/bin64/dmd
version v2.063
config/home/jlquinn/dmd2/linux/bin64/dmd.conf
parse junk
importall junk
importobject
(/home/jlquinn/dmd2/lin
On 06/04/2013 08:03 PM, Jerry wrote:
Hi folks,
I've downloaded the current dmd 2.063 zip and tried it out. This is
Ubuntu 12.10 x86_64. Every program I compile segfaults when I try to
run it. As a simple example:
jlquinn@wyvern:~/re/test$ cat junk.d
import std.stdio;
void main() {
writeln
"Gary Willoughby" writes:
> On Tuesday, 4 June 2013 at 18:03:53 UTC, Jerry wrote:
>> Hi folks,
>>
>> I've downloaded the current dmd 2.063 zip and tried it out. This is
>> Ubuntu 12.10 x86_64. Every program I compile segfaults when I try to
>> run it. As a simple example:
>>
>> jlquinn@wyvern:
"Rob T" writes:
> On Tuesday, 4 June 2013 at 18:03:53 UTC, Jerry wrote:
>> Hi folks,
>>
>> I've downloaded the current dmd 2.063 zip and tried it out. This is
>> Ubuntu 12.10 x86_64. Every program I compile segfaults when I try to
>> run it. As a simple example:
>
> Is this a clean install?
>
On Tuesday, 4 June 2013 at 18:03:53 UTC, Jerry wrote:
Hi folks,
I've downloaded the current dmd 2.063 zip and tried it out.
This is
Ubuntu 12.10 x86_64. Every program I compile segfaults when I
try to
run it. As a simple example:
jlquinn@wyvern:~/re/test$ cat junk.d
import std.stdio;
void
On Tuesday, 4 June 2013 at 18:03:53 UTC, Jerry wrote:
Hi folks,
I've downloaded the current dmd 2.063 zip and tried it out.
This is
Ubuntu 12.10 x86_64. Every program I compile segfaults when I
try to
run it. As a simple example:
jlquinn@wyvern:~/re/test$ cat junk.d
import std.stdio;
void
On Tuesday, 4 June 2013 at 18:03:53 UTC, Jerry wrote:
Hi folks,
I've downloaded the current dmd 2.063 zip and tried it out.
This is
Ubuntu 12.10 x86_64. Every program I compile segfaults when I
try to
run it. As a simple example:
jlquinn@wyvern:~/re/test$ cat junk.d
import std.stdio;
void
Hi folks,
I've downloaded the current dmd 2.063 zip and tried it out. This is
Ubuntu 12.10 x86_64. Every program I compile segfaults when I try to
run it. As a simple example:
jlquinn@wyvern:~/re/test$ cat junk.d
import std.stdio;
void main() {
writeln("Hi");
}
jlquinn@wyvern:~/re/test$ /ho
34 matches
Mail list logo
