On Tue, Jun 20, 2006 at 06:46:07PM +0200, Mattia Dongili wrote: > Linus says that maybe > echo 0 > /proc/sys/kernel/randomize_va_space > can workraround the problem. > > Can you try it?
This didn't seem to make any difference. I should add that it doesn't always trigger the kernel message, but in any case it never starts successfully (so presumably segfaults without kernel message). When tracing the program in gdb, I noticed that the cpufreqd_log() function was opening syslog above (ie. log_opened == 0, so it calls openlog() to do so). I'm beginning to think it's suspicious that adding -V4 to the arguments makes a difference. In fact weirdly enough, adding -V 4,5 or 2 helps, but -V3 doesn't. I presume adding that alters what gets output and thus exactly when syslog is opened. Since it's crashing on the vfprintf() perhaps it's also possible this is a bug in libc? -- Vincent Ho "If we hit that bullseye, the rest of the dominos will fall like a house of cards. Checkmate." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
