On Tue, Jun 20, 2006 at 08:47:30AM +0200, Mattia Dongili wrote: Hi Mattia,
> No other kernel messages (see dmesg)? No, there's no other kernel messages; dmesg just contains the same line above. > Also, could you run cpufreqd through gdb[1] and send me the backtrace of > the crash? Ah now this is interesting. It seems to run OK if I tell it not to run in the background, whether or not I'm in gdb. I rebuilt the package with DEB_BUILD_OPTIONS=nostrip, and set gdb to follow the child process using "set follow-fork-mode child". It then dies in the child as follows: (gdb) set follow-fork-mode child (gdb) run -f /etc/cpufreqd.conf Starting program: /usr/sbin/cpufreqd -f /etc/cpufreqd.conf [tcsetpgrp failed in terminal_inferior: Operation not permitted] [Thread debugging using libthread_db enabled] [New Thread 47634791996128 (LWP 13959)] [New Thread 1082132832 (LWP 13960)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47634791996128 (LWP 13959)] 0x00002b52d6adb4b0 in strlen () from /lib/libc.so.6 (gdb) bt #0 0x00002b52d6adb4b0 in strlen () from /lib/libc.so.6 #1 0x00002b52d6aad22b in vfprintf () from /lib/libc.so.6 #2 0x0000000000405abd in cpufreqd_log (prio=3, fmt=0x2aaaaaaac08c "%-25s: %s: %s\n") at cpufreqd_log.c:70 #3 0x00002aaaaaaabf5b in apm_init () at cpufreqd_apm.c:51 #4 0x00000000004063ca in load_plugin_list (plugins=0x50b468) at plugin_utils.c:128 #5 0x0000000000404c11 in init_configuration (configuration=0x50b010, info=0x50b480) at config_parser.c:630 #6 0x00000000004033ff in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:679 The line in question is vfprintf(stderr, fmt, argp); but I'm not sure why it should be segfaulting. Using various -V options at runtime also seems to help. Vince -- 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]