Re: [dev] [sic] Segfault

2010-03-23 Thread Claudio M. Alessi
What about removing (or commenting) line 45 by default? Who needs debug output can put (or remove comment) itself. -- JID: smoppy AT gmail.com WWW: http://cma.teroristi.org

Re: [dev] [sic] Segfault

2010-03-22 Thread Anselm R Garbe
On 20 March 2010 19:24, Rob wrote: >> sic segfaults when USER environment variable is not set (so >> getenv("USER") returns NULL): > > > This does the trick, at no line cost. I assume that when compiled, the > two getenv calls can be merged into one, optimisation wise. Not that > it's a major spee

Re: [dev] [sic] Segfault

2010-03-20 Thread Rob
> sic segfaults when USER environment variable is not set (so > getenv("USER") returns NULL): This does the trick, at no line cost. I assume that when compiled, the two getenv calls can be merged into one, optimisation wise. Not that it's a major speed problem. 169c169 < strncpy(nick, get

[dev] [sic] Segfault

2010-03-20 Thread Dmitry Maluka
sic segfaults when USER environment variable is not set (so getenv("USER") returns NULL): $ unset USER $ sic