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.
Re: bugzilla email
Brad Roberts bra...@puremagic.com wrote in message news:mailman.33.1241944005.13405.digitalmars-d-b...@puremagic.com... A while ago the inbound mail into bugzilla from replies to this group broke. I figured out why, but the fix wasn't pleasant -- the perl code wasn't compatible with a perl upgrade (5.8 - 5.10). The migration I did tonight ought to make it possible for me to put that mechanism back together.. however I figured I'd take a poll. Who found it useful and/or desirable? It's been disabled long enough that I figured I should see if it's worth re-instating. Thanks, Brad I didn't know there was ever such a feature :) Personally, I'm fairly accustomed to adding replies on the actual web-page interface.
Re: Bugzilla Downtime
Brad Roberts bra...@puremagic.com wrote in message news:mailman.31.1241943078.13405.digitalmars-d-b...@puremagic.com... Brad Roberts wrote: Tonight I'm going to update bugzilla to the current release and move it to a new host. I'll put the existing copy in read-only mode at around 10 or 11pm Seattle time. The process shouldn't take all that long, but I'll estimate an hour just to give myself some padding time. Later, Brad Ok.. I've changed the dns entry to the new server, so as soon as it propagates around the world, the new site will be active. I'm sure it's not perfect yet.. but it's good enough to open up. Please file bug reports against puremagic.com if you find something wrong or missing. I haven't fully incorporated all of the customizations I'd made to the previous version, but at least the posting to the newsgroups part works again. Later, Brad Whooo, it's very pretty :)
