<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to support-requests</title><link href="https://sourceforge.net/p/log4c/support-requests/" rel="alternate"/><link href="https://sourceforge.net/p/log4c/support-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/log4c/support-requests/</id><updated>2015-08-04T05:59:18.444000Z</updated><subtitle>Recent changes to support-requests</subtitle><entry><title>#4 Log4c giving segmentation fault when changing the priority.</title><link href="https://sourceforge.net/p/log4c/support-requests/4/?limit=25#1c25" rel="alternate"/><published>2015-08-04T05:59:18.444000Z</published><updated>2015-08-04T05:59:18.444000Z</updated><author><name>terry yuan</name><uri>https://sourceforge.net/u/terryatsource/</uri></author><id>https://sourceforge.net538666a6f3553874f7f0e0c598352455f274cf55</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;the solution provided above does work!&lt;br/&gt;
thanks!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#9 Specific String crashes logger. Reproducible</title><link href="https://sourceforge.net/p/log4c/support-requests/9/?limit=25#ccb2" rel="alternate"/><published>2014-12-05T07:14:37.185000Z</published><updated>2014-12-05T07:14:37.185000Z</updated><author><name>František Dvořák</name><uri>https://sourceforge.net/u/valtri/</uri></author><id>https://sourceforge.netde59fe05fdd4698ea083c7cbab7363436b9dc380</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#9 Specific String crashes logger. Reproducible</title><link href="https://sourceforge.net/p/log4c/support-requests/9/?limit=25#8ca8" rel="alternate"/><published>2014-12-05T07:08:00.773000Z</published><updated>2014-12-05T07:08:00.773000Z</updated><author><name>zbeck</name><uri>https://sourceforge.net/u/zbeckerman/</uri></author><id>https://sourceforge.net9711c81848ec1d560a2209a6e5029864f99711c3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;that worked a lot better.&lt;br /&gt;
Thanks&lt;br /&gt;
/Z&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#8 possible deadlock in log4c</title><link href="https://sourceforge.net/p/log4c/support-requests/8/?limit=25#69fe" rel="alternate"/><published>2014-12-05T06:58:25.870000Z</published><updated>2014-12-05T06:58:25.870000Z</updated><author><name>František Dvořák</name><uri>https://sourceforge.net/u/valtri/</uri></author><id>https://sourceforge.neta1982abc820603f28127e17f921da1164ca5c2bf</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;blockquote&gt;
&lt;p&gt;Has anyone noticed anything similar?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We use log4c in multithread environment and haven't noticed this problem yet. I'll try to reproduce it, or pass it through hellgrind.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I notice this is no longer supported. Is there a recommended logger for c? I can try log4c++ I guess.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I adopt log4c after some time of its inactivity. I can't do much user support or development, but I'm interested in critical bugs and/or patches. :-)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#9 Specific String crashes logger. Reproducible</title><link href="https://sourceforge.net/p/log4c/support-requests/9/?limit=25#2e8b" rel="alternate"/><published>2014-12-05T06:22:24.446000Z</published><updated>2014-12-05T06:22:24.446000Z</updated><author><name>František Dvořák</name><uri>https://sourceforge.net/u/valtri/</uri></author><id>https://sourceforge.netdf1f3f3da474df58197961d44638c82b6adc14f6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;You should use:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;log4c_category_log(logger, LOG4C_PRIORITY_INFO, "%s", "any string with % here...");&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;The "%s" format string is needed also when logging string variable (as it can contains % characters too).&lt;/p&gt;
&lt;p&gt;Also I recommend to switch on the warnings (-Wformat -Wformat-security, or -Wall -Wformat-security). gcc should catch this problem already during compilation.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Specific String crashes logger. Reproducible</title><link href="https://sourceforge.net/p/log4c/support-requests/9/" rel="alternate"/><published>2014-12-05T05:26:29.408000Z</published><updated>2014-12-05T05:26:29.408000Z</updated><author><name>zbeck</name><uri>https://sourceforge.net/u/zbeckerman/</uri></author><id>https://sourceforge.nete4aa8b1d339e78f50c53d514d4d984beb7d2f171</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A specific String crashes logger. Reproducible every time and easy to test&lt;/p&gt;
&lt;p&gt;Try to log this string below. &lt;/p&gt;
&lt;p&gt;Example&lt;br /&gt;
log4c_category_log(logger, LOG4C_PRIORITY_INFO,&lt;br /&gt;
"BAS011ACAA01501170C10039True30$BookingTime \n $FirstName $LastName Id=$RPINTest&lt;strong&gt;&lt;em&gt; Enter ID &lt;/em&gt;&lt;/strong&gt;%m/%d/%Y%I:%M %pFalse0True-4806013943484001414911600FalseFalseFalse0");&lt;/p&gt;
&lt;p&gt;Note that this crashes. The problem seems to stem from '%m/%d/%Y%I:%M %p' part of the text. I am happy to help to contribute but I need some pointers on where to look and how to get this tested.&lt;/p&gt;
&lt;p&gt;Please assist, this is a critical bug. I simply had to remove some of the loggers.&lt;br /&gt;
/Z&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Specific String crashes logger. Reproducible</title><link href="https://sourceforge.net/p/log4c/support-requests/9/" rel="alternate"/><published>2014-12-05T05:26:29.408000Z</published><updated>2014-12-05T05:26:29.408000Z</updated><author><name>zbeck</name><uri>https://sourceforge.net/u/zbeckerman/</uri></author><id>https://sourceforge.net60d92458dcce2e8592aa4c76a9b0ddffe4d0cb4a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 9 has been modified: Specific String crashes logger. Reproducible&lt;br /&gt;
Edited By: František Dvořák (valtri)&lt;br /&gt;
Status updated: u'open' =&amp;gt; u'closed'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>possible deadlock in log4c</title><link href="https://sourceforge.net/p/log4c/support-requests/8/" rel="alternate"/><published>2014-11-14T18:55:29.283000Z</published><updated>2014-11-14T18:55:29.283000Z</updated><author><name>zbeck</name><uri>https://sourceforge.net/u/zbeckerman/</uri></author><id>https://sourceforge.net220295f4da055433d4e4b9245d969fa376665669</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I noticed in some case that some of our threads were just hanging. After adding hundreds of printf statements, I came to the conclusion that log4c was the probable cause.&lt;/p&gt;
&lt;p&gt;I changed my utility log method to do a printf instead of use log4c and viola, all the hanging stopped.&lt;/p&gt;
&lt;p&gt;There is some critical bug in this framework that causes a hang/deadlock when utilized with a highly multi-threaded app with high transaction usage.&lt;/p&gt;
&lt;p&gt;Has anyone noticed anything similar? I notice this is no longer supported. Is there a recommended logger for c? I can try log4c++ I guess.&lt;/p&gt;
&lt;p&gt;My test case was simple. start an app, open 15 threads. each thread does a log statement, printf("thread number") and sleep(1) and runs forever. monitor the console for any thread that is not outputting the printf and you know that you are hung. now increase to 30 threads and retest.&lt;/p&gt;
&lt;p&gt;when it runs for 10 hours without problems, you know the issue is solved.&lt;br /&gt;
/Z&lt;/p&gt;
&lt;p&gt;/Z&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>rollongpolicy triggering event</title><link href="https://sourceforge.net/p/log4c/support-requests/7/" rel="alternate"/><published>2013-10-18T05:35:49.776000Z</published><updated>2013-10-18T05:35:49.776000Z</updated><author><name>joe333</name><uri>https://sourceforge.net/u/joseph333/</uri></author><id>https://sourceforge.netb56a7b996ab80757f145ef284829a0e3f4381816</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I've a doubt about log4c_rollingpolicy_is_triggering_event() i did not understand the log4c_logging_event_t * evtp parameter. How could i get the evtp parameter.&lt;br /&gt;
Is this function supposed to be used only for internal purpose? &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>logging to server.</title><link href="https://sourceforge.net/p/log4c/support-requests/6/" rel="alternate"/><published>2013-04-17T07:58:49Z</published><updated>2013-04-17T07:58:49Z</updated><author><name>san1079</name><uri>https://sourceforge.net/u/san1079/</uri></author><id>https://sourceforge.netcdb800210ef511b50e6f4824cfee94939661054a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am new to log4c. Could someone explain how can i use log4c to send my logs to &lt;br /&gt;
a server?&lt;br /&gt;
Thanks on advance.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>