Syslog fixes a bug? - ReadList.com

4 msg	Extracting all functions from C++ source code
2 msg	Force GCC to unroll a loop?

Syslog fixes a bug?
\ Michael Wieher (7 May 2008)
. \ John Love-Jensen (8 May 2008)
. \ Atwood, Robert C (8 May 2008)
. \ candido lopez rodriguez (8 May 2008)
. \ Philipp Thomas (9 May 2008)

2 msg	gcc 4.2.x large file support
2 msg	Windows DEP problem with nested functions
8 msg	Porting GCC to 8051 Microcontroller
2 msg	Cleanup for thread local storage?
3 msg	GCC 4.3.2 Install into Cygwin
4 msg	gcno file doesn't include uncalled member funct...
3 msg	GCC 4.3.0 configure failure: libgcc
2 msg	lex/yacc
1 msg	Building trunk -- error msg instrucitons not qu...
2 msg	MIPS atomic builtins
3 msg	Enabling loop unrolling in small sections of code.
1 msg	#pragma warning
2 msg	Problems building gcc 4.3
8 msg	gcc 4.3.0 -- program search path issue
1 msg	Re: WELCOME to gcc
2 msg	Include paths for cpp/g++ (gcc 4.3.0)
2 msg	Linking a library and source file into another ...

Subject:	Syslog fixes a bug?
Group:	Gcc-help
From:	Michael Wieher
Date:	7 May 2008

Hey,

I have a program that dies mysteriously.

If I use syslog() to attempt to write data and see where it dies, it
lives and works perfectly.

If I comment out the syslog() function call, the program crashes every time.

This is entirely reliable, have tested it 10 times commented +
uncommented. It is a line of static text, ie:
syslog(LOG_INFO,"hello");

Why / how would this affect my program's execution?