[syslog-ng] Syslog-ng-2.05 Segmentation Fault

[Shashank Vinchurkar]

Daniel,

I didn't try with older version of syslog-ng. You can get around the
first problem with the changes I had suggested.

The second problem seemed to be related to glib library. I could get
around it by hacking the value of the Gstring returned by the
g_string_printf. But it didn't seem to be right solution. I tried older
version of glib but it didn't seem to work.

I was cross compiling both syslog-ng and glib.

-Shashank

-----Original Message-----
From: syslog-ng-bounces at lists.balabit.hu
[mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Daniel
Szmandiuk
Sent: Thursday, November 08, 2007 2:33 PM
To: Syslog-ng users' and developers' mailing list
Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault

Shashank,

Did you successfully get any older version of syslog-ng compiled &
working on your mips64 system? I'm trying to get a syslog-ng system up
and running for testing fairly quickly at the moment.

Daniel


-----Original Message-----
From: syslog-ng-bounces at lists.balabit.hu
[mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Shashank
Vinchurkar
Sent: Friday, 9 November 2007 5:35 AM
To: Syslog-ng users' and developers' mailing list
Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault

I was hitting this issue on mips64 (had reported it on this list).
Debugging the issue the culprit seemed to be the call
g_free(self->re_matches) in function log_msg_clear_matches (logmsg.c).
The values of the self->re_matches was zero when it was getting segfault
but the pointer self->re_matches had a non-null value. Making the g_free
conditional seemed to work for me.

I was able to get past this issue but was seeing some other strange
behavior and could not get the syslog-ng to work on mips64. I was not
able to get the messages to log to the log file /var/log/messages
(reported it on this list). Debugging the issue it seemed the
g_string_printf in log_write_format_log function was not working
properly on 64bit mips and thus the log was never written to the file or
any other output device.


-----Original Message-----
From: syslog-ng-bounces at lists.balabit.hu
[mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Balazs
Scheidler
Sent: Thursday, November 08, 2007 7:21 AM
To: Syslog-ng users' and developers' mailing list
Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault

Hm.. the same has been reported on a mips64 system. This must be a 64
bit related issue, then. I'll try to get a 64 compile environment.

Anyone else who uses syslog-ng 2.0.x on 64 bit systems?

On Thu, 2007-11-08 at 23:34 +1100, Daniel Szmandiuk wrote:
> Here's the backtrace:
> GNU gdb Red Hat Linux (6.5-16.el5rh)
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and 
> you are welcome to change it and/or distribute copies of it under 
> certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for 
> details.
> This GDB was configured as "x86_64-redhat-linux-gnu"...Using host 
> libthread_db library "/lib64/libthread_db.so.1".

--
Bazsi

_______________________________________________
syslog-ng maillist  -  syslog-ng at lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

_______________________________________________
syslog-ng maillist  -  syslog-ng at lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html


This email and any attachments transmitted with it are confidential and
may contain legally privileged information.  If you are not the intended
recipient you are prohibited from disclosing, copying or using the
information contained in it.  If you have received this email in error,
please notify the sender immediately by return email and then delete all
copies of this transmission together with any attachments.

It is the addressee's/recipient's duty to virus scan and otherwise test
the email before loading it onto any computer system.  IMC
Communications does not accept liability in connection with any computer
virus, data corruption, delay, interruption, unauthorised access or
unauthorised amendment in relation to this email.

For information about our privacy policy, visit the IMC Communications
website at www.imc.net.au

This email has been checked by IMC's SMTP gateway.
-&-
_______________________________________________
syslog-ng maillist  -  syslog-ng at lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html