www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.bugs - Any "writef" or "writefln" produces segmentation fault on DMD 2.049 on OS X 10.5.8

reply RedZone908 <kilpa1kb cmich.edu> writes:
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: 0x00000000
0x0000e3c5 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: 0x00000000
0x0000ea55 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.
Oct 09 2010
next sibling parent RedZone908 <kilpa1kb cmich.edu> writes:
I tried recompiling DMD and Phobos, too.  Didn't change anything.
Oct 09 2010
prev sibling parent "Nick Sabalausky" <a a.a> writes:
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" <kilpa1kb cmich.edu> wrote in message 
news:i8r2q4$2nj6$1 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: 0x00000000
 0x0000e3c5 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: 0x00000000
 0x0000ea55 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. 
Oct 09 2010