Re: Any writef or writefln produces segmentation fault on DMD 2.049 on OS X 10.5.8
I tried recompiling DMD and Phobos, too. Didn't change anything.
Any writef or writefln produces segmentation fault on DMD 2.049 on OS X 10.5.8
Hello. Maybe something's wrong with my configuration, but... I had been working on a project under DMD 2.046. It was correctly running under that. Then I upgraded to 2.047. Suddenly the project produced segmentation faults with not much of an explanation. Frustrated, I left the project and returned to it today, upgrading to 2.049. I did a little more investigating and created a simple hello world program, and found that writef and writefln were what was producing the segmentation fault. Just plain write worked. GDB produces this error when I use writef: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x 0xe3c5 in __tls_get_addr () Incidentally, the new readf function produces segmentation faults as well. Here's what happens: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x 0xea55 in __tls_get_addr () I don't know if these errors are really bugs or if something's wrong with my configuration (which, as far as I can tell, is the default). All I know is that up until 2.046 everything worked and all of a sudden now the formatted i/o functions produce segmenation faults.
Re: Any writef or writefln produces segmentation fault on DMD 2.049 on OS X 10.5.8
Bug reports should be posted at http://d.puremagic.com/issues/ This digitalmars.D.bugs newsgroup is just a place where the reports get mirrored to. RedZone908 kilpa...@cmich.edu wrote in message news:i8r2q4$2nj...@digitalmars.com... Hello. Maybe something's wrong with my configuration, but... I had been working on a project under DMD 2.046. It was correctly running under that. Then I upgraded to 2.047. Suddenly the project produced segmentation faults with not much of an explanation. Frustrated, I left the project and returned to it today, upgrading to 2.049. I did a little more investigating and created a simple hello world program, and found that writef and writefln were what was producing the segmentation fault. Just plain write worked. GDB produces this error when I use writef: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x 0xe3c5 in __tls_get_addr () Incidentally, the new readf function produces segmentation faults as well. Here's what happens: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x 0xea55 in __tls_get_addr () I don't know if these errors are really bugs or if something's wrong with my configuration (which, as far as I can tell, is the default). All I know is that up until 2.046 everything worked and all of a sudden now the formatted i/o functions produce segmenation faults.
