<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>hi,
<br>
<br>thanks for the diagnosis, I'll look into applying the patch again.
<br>
<br>----- Original message -----
<br>> Hi,
<br>>
<br>> I also was able to reproduce the segfault. It always happened when a
<br>> "mark" was generated. So, in order to reproduce this, set the mark
<br>> intervall to a low value, i.e. mark(1).
<br>>
<br>> I don't think it's a Problem of the 32bit NVTable patch, though. The
<br>> following changes also made the segfault go away:
<br>>
<br>> --- a/lib/driver.c
<br>> +++ b/lib/driver.c
<br>> @@ -158,7 +158,7 @@ log_src_driver_queue_method(LogPipe *s, LogMessage
<br>> *msg, const LogPathOptions *p
<br>>  if (msg->flags & LF_LOCAL)
<br>>  afinter_postpone_mark(cfg->mark_freq);
<br>>
<br>> -  log_msg_set_value(msg, LM_V_SOURCE, self->super.group,
<br>> self->group_len); +  log_msg_set_value(msg, LM_V_SOURCE,
<br>> self->super.group, strlen(self->super.group));
<br>>  stats_counter_inc(self->super.processed_group_messages);
<br>>  stats_counter_inc(self->received_global_messages);
<br>>  log_pipe_forward_msg(s, msg, path_options);
<br>>
<br>> It seems that self->group_len is not initialized correctly, resulting in
<br>> some ridiculous large value_len being passed to nv_table_set value. I
<br>> just found this, but did not have any further time to investigate. I
<br>> suspect this has been there before the NVTable patch, but since the
<br>> value_len exceeded the old NVTable max value size, nothing was inserted.
<br>>
<br>>  Peter
<br>>
<br>>
<br>> Am 04.04.2012 19:44, schrieb Balazs Scheidler:
<br>> > I have reverted the changes for now.
<br>> >
<br>> > ----- Original message -----
<br>> > > On 04/03/2012 03:53 PM, Gergely Nagy wrote:
<br>> > > > Peter Czanik<<a href="mailto:czanik@balabit.hu">czanik@balabit.hu</a> <<a href="mailto:czanik@balabit.hu">mailto:czanik@balabit.hu</a>>>  writes:
<br>> > > >
<br>> > > > > Program terminated with signal 11, Segmentation fault.
<br>> > > > > #0  0x000000080142fb86 in memcpy () from /lib/libc.so.7
<br>> > > > > (gdb) thread apply all backtrace
<br>> > > > >
<br>> > > > > Thread 1 (Thread 8016041c0 (LWP 100064)):
<br>> > > > > #0  0x000000080142fb86 in memcpy () from /lib/libc.so.7
<br>> > > > > #1  0x00000008006884a8 in nv_table_add_value (self=0x803c00000,
<br>> > > > > handle=7, name=0x80161b1c8 "SOURCE", name_len=6,
<br>> > > > > value=0x80161b4c0 "s_local",
<br>> > > > > value_len=23133952, new_entry=0x7fffffffe424) at nvtable.c:464
<br>> > > > Interesting. Can you perhaps try with commit
<br>> > > > bb667115b80b24055dd1245084c7d2e26d01d184 reverted?
<br>> > > >
<br>> > > Yes, that solved the problem on FreeBSD 8.1.
<br>> > > Previously I wrote, that this problem does not seem to affect Linux.
<br>> > > I checked it again, and have some mixed results: I have some logs
<br>> > > from yesterday, even from after I installed the git version with
<br>> > > NVtable changes, but right now it's also segfaults on openSUSE 12.1.
<br>> > > Bye,
<br>> ______________________________________________________________________________
<br>> Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
<br>> Documentation:
<br>> <a href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a> FAQ:
<br>> <a href="http://www.balabit.com/wiki/syslog-ng-faq">http://www.balabit.com/wiki/syslog-ng-faq</a>
<br>>
<br><br></p>
</body>
</html>