Steven Dake escribió:
>
> On Tue, Nov 10, 2009 at 4:34 AM, Adrian Chapela 
> <[email protected] <mailto:[email protected]>> 
> wrote:
>
>     Andrew Beekhof escribió:
>     > On Tue, Nov 10, 2009 at 10:34 AM, Adrian Chapela
>     > <[email protected]
>     <mailto:[email protected]>> wrote:
>     >
>     >> Maybe I need some more,
>     >>
>     >
>     > You mean like the ones for the packages you're trying to debug?
>     > Yes, installing the -dbg packages for corosync + pacemaker would
>     sound
>     > like a good idea.
>     >
>
>     OK, I have a better output in the other node:
>     (gdb) where
>     #0  0x00007f9f00e56151 in getenv () from /lib/libc.so.6
>     #1  0x00007f9f00eb1689 in tzset_internal () from /lib/libc.so.6
>     #2  0x00007f9f00eb1a60 in tzset () from /lib/libc.so.6
>     #3  0x00007f9f00eb7425 in __strftime_internal () from /lib/libc.so.6
>     #4  0x00007f9f019a6cd1 in log_printf_to_logs (rec_ident=<value
>     optimized
>     out>, file_name=0x414a8730 "utils.c", function_name=0x414a873c
>     "config_find_init", file_line=546,
>        buffer=0x414a8754 "info: config_find_init: Local handle:
>     1003584061500817409 for logging") at logsys.c:493
>     #5  0x00007f9f019a73a0 in logsys_worker_thread (data=<value optimized
>     out>) at logsys.c:650
>     #6  0x00007f9f0137ffc7 in start_thread () from /lib/libpthread.so.0
>     #7  0x00007f9f00ef15ad in clone () from /lib/libc.so.6
>     #8  0x0000000000000000 in ?? ()
>
>     Could this help ?
>
>
> I recommend turning off timestamps in your logging configuration to 
> work around this problem.  This will avoid the code from running that 
> is causing the segfault.
OK, I will try your option.
>
> (timestamp: on should be timestamp: off)
>
> File a bugzilla at bugzilla.redhat.com <http://bugzilla.redhat.com> 
> against corosync component rawhide version.
>
> As to why this core happens, I can't explain it.  We can work through 
> the bz off list on bugzilla.
>
> One thing we will need is libc-debuginfo packages installed on your 
> system when running the backtrace (in this case libc is segfaulting so 
> having its data would be helpful).
I think that I have this package installed. I have the next package 
installed on my debian:
libc6-dbg - GNU C Library: Libraries with debugging symbols
>  
>
>     _______________________________________________
>     Openais mailing list
>     [email protected]
>     <mailto:[email protected]>
>     https://lists.linux-foundation.org/mailman/listinfo/openais
>
>

_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to