log4cpp-devel — technical discussions about the development of log4cpp

Re: [Log4cpp-devel] Log4cpp thread-safety

[jinq0123 <jin...@gm...>]

SSB1c2UgbG9nNGNwcCAwLjMuNGIuDQpJIHRoaW5rIGl0IGlzIHRocmVhZHNhZmUuDQpCdXQgdGhl
IGluaXRpYWxpemF0aW9uIGFuZCBmaW5hbGl6YXRpb24gc2hvdWxkIGJlIGluIHRoZSBtYWluIHRo
cmVhZC4NCkFuZCBzaG91bGQgdXNlIGEgdGhyZWFkc2FmZSBTVEwgaW1wbGVtZW50YXRpb24uDQoN
Ci0tLS0tLS0tLS0tLS0tLS0tLQkJCQkgDQpqaW5xMDEyMw0KMjAwNy0wMy0wNg0KDQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQq3
orz+yMujulJvYmluc29uLCBEYXZpZCBOLg0Kt6LLzcjVxtqjujIwMDctMDMtMDUgMjM6MzU6MTUN
CsrVvP7Iy6O6bG9nNGNwcC1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCrOty82juk5lb2d5
LCBBYmhpaml0DQrW98zio7pbTG9nNGNwcC1kZXZlbF0gTG9nNGNwcCB0aHJlYWQtc2FmZXR5DQoN
CkxvZzRjcHAgc3VwcG9ydDoNCg0KSSBuZWVkIHRvIGNsYXJpZnkgZXhhY3RseSB3aGF0IGlzIG5l
ZWRlZCB0byBtYWtlIGxvZzRjcHAgdGhyZWFkLXNhZmUuDQoNCklzIGl0IGVzc2VudGlhbCB0byBz
cGVjaWZ5IGVpdGhlcg0KCS0td2l0aC1vbW5pdGhyZWFkc1s9PHBhdGgtdG8tb21uaU9SQj5dIA0K
b3INCgktLXdpdGgtcHRocmVhZHMgDQphcyBvcHRpb25zIGZvciAuL2NvbmZpZ3VyZSBpbiBvcmRl
ciBmb3IgbG9nNGNwcCB0byBiZSB0aHJlYWQtc2FmZT8NCg0KSXMgYW55dGhpbmcgZWxzZSBuZWVk
ZWQgZm9yIHRocmVhZC1zYWZldHk/DQoNCk5vdGUgdGhhdCBvbiBodHRwOi8vbG9nNGNwcC5zb3Vy
Y2Vmb3JnZS5uZXQvLCB0aGUgcXVlc3Rpb24NCgkzLjIuIElzIGxvZzRjcHAgdGhyZWFkLXNhZmU/
DQppcyBsZWZ0IHVuYW5zd2VyZWQuDQoNClRoYW5rcywNCglEYXZpZCBSb2JpbnNvbg0KCWRhdmlk
Lm4ucm9iaW5zb25AZm1yLmNvbQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGFrZSBTdXJ2ZXlzLiBFYXJu
IENhc2guIEluZmx1ZW5jZSB0aGUgRnV0dXJlIG9mIElUDQpKb2luIFNvdXJjZUZvcmdlLm5ldCdz
IFRlY2hzYXkgcGFuZWwgYW5kIHlvdSdsbCBnZXQgdGhlIGNoYW5jZSB0byBzaGFyZSB5b3VyDQpv
cGluaW9ucyBvbiBJVCAmIGJ1c2luZXNzIHRvcGljcyB0aHJvdWdoIGJyaWVmIHN1cnZleXMtYW5k
IGVhcm4gY2FzaA0KaHR0cDovL3d3dy50ZWNoc2F5LmNvbS9kZWZhdWx0LnBocD9wYWdlPWpvaW4u
cGhwJnA9c291cmNlZm9yZ2UmQ0lEPURFVkRFVg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCkxvZzRjcHAtZGV2ZWwgbWFpbGluZyBsaXN0DQpMb2c0Y3Bw
LWRldmVsQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KaHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5u
ZXQvbGlzdHMvbGlzdGluZm8vbG9nNGNwcC1kZXZlbA0KDQo=

Re: [Log4cpp-devel] Log4cpp thread-safety

[Konstantin L. <1da...@ma...>]

Hello, Philippe!
You wrote to "Robinson, David N." <Dav...@FM...>; 
<log...@li...> on Mon, 5 Mar 2007 15:55:32 +0000 
(GMT):

PH> log4cpp's source code has some flaws as far as thread safety is
PH> concerned. I submitted a patch for a problem that was specially harmful
PH> for our project
PH> (http://sourceforge.net/tracker/index.php?func=detail&aid=1368387&group
PH> _id=15190&atid=315190) and noticed nothing else to correct in log4ccp
PH> 0.3.5rc3 concerning this issue.

    Philippe could you please clarify why we need those locks and what 
problems did you have without them.

With best regards, Konstantin Litvinenko. 

Re: [Log4cpp-devel] Log4cpp thread-safety

[Konstantin L. <1da...@ma...>]

Hello, Robinson,!
You wrote to <log...@li...> on Mon, 5 Mar 2007 
10:34:51 -0500:

RDN> Note that on http://log4cpp.sourceforge.net/, the question
RDN>  3.2. Is log4cpp thread-safe?
RDN> is left unanswered.

    As far as I know log4cpp is thread-safe. We use log4cpp 0.3.4b on havy 
loaded 27/7 windows/linux box without any problems. Both run with native 
thread implementation.

With best regards, Konstantin Litvinenko. 

[Log4cpp-devel] Re : Log4cpp thread-safety

[Philippe H. <phi...@ya...>]

Hello,=0A=0AYou can use either --with-omnithreads[=3D<path-to-omniORB>]  or=
 --with-pthreads but it is not just a matter of options for configure.=0Alo=
g4cpp's source code has some flaws as far as thread safety is concerned. =
=0AI submitted a patch for a problem that was specially harmful for our pro=
ject (http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1368387&=
group_id=3D15190&atid=3D315190) and noticed nothing else to correct in log4=
ccp 0.3.5rc3 concerning this issue.=0A=0ABest regards,=0A=0APH=0A----- Mess=
age d'origine ----=0ADe : "Robinson, David N." <Dav...@FM...>=
=0A=C0 : log...@li...=0ACc : "Neogy, Abhijit" <abhij=
it....@FM...>=0AEnvoy=E9 le : Lundi, 5 Mars 2007, 16h34mn 51s=0AObjet :=
 [Log4cpp-devel] Log4cpp thread-safety=0A=0ALog4cpp thread-safety=0A=0A=0A =
=0A =0A=0A=0A=0A=0ALog4cpp support:=0A=0A=0A=0AI need to clarify exactly wh=
at is needed to make log4cpp thread-safe.=0A=0A=0A=0AIs it essential to spe=
cify either=0A=0A=0A        --with-omnithreads[=3D<path-to-omniORB>] =0A=0A=
=0Aor=0A=0A=0A        --with-pthreads =0A=0A=0Aas options for ./configure i=
n order for log4cpp to be thread-safe?=0A=0A=0A=0AIs anything else needed f=
or thread-safety?=0A=0A=0A=0ANote that on http://log4cpp.sourceforge.net/, =
the question=0A=0A=0A        3.2. Is log4cpp thread-safe?=0A=0A=0Ais left u=
nanswered.=0A=0A=0A=0AThanks,=0A=0A=0A        David Robinson=0A=0A=0A      =
  dav...@fm...=0A=0A=0A=0A-------------------------------------=
------------------------------------=0ATake Surveys. Earn Cash. Influence t=
he Future of IT=0AJoin SourceForge.net's Techsay panel and you'll get the c=
hance to share your=0Aopinions on IT & business topics through brief survey=
s-and earn cash=0Ahttp://www.techsay.com/default.php?page=3Djoin.php&p=3Dso=
urceforge&CID=3DDEVDEV=0A_______________________________________________=0A=
Log4cpp-devel mailing list=0AL...@li...=0Ahttps://=
lists.sourceforge.net/lists/listinfo/log4cpp-devel=0A=0A=0A=0A=0A=0A=0A=0A=
=09=0A=0A=09=0A=09=09=0A___________________________________________________=
________________________ =0AD=E9couvrez une nouvelle fa=E7on d'obtenir des =
r=E9ponses =E0 toutes vos questions ! =0AProfitez des connaissances, des op=
inions et des exp=E9riences des internautes sur Yahoo! Questions/R=E9ponses=
 =0Ahttp://fr.answers.yahoo.com

[Log4cpp-devel] Log4cpp thread-safety

[Robinson, D. N. <Dav...@FM...>]

Log4cpp support:

I need to clarify exactly what is needed to make log4cpp thread-safe.

Is it essential to specify either
	--with-omnithreads[=3D<path-to-omniORB>]=20
or
	--with-pthreads=20
as options for ./configure in order for log4cpp to be thread-safe?

Is anything else needed for thread-safety?

Note that on http://log4cpp.sourceforge.net/, the question
	3.2. Is log4cpp thread-safe?
is left unanswered.

Thanks,
	David Robinson
	dav...@fm...

[Log4cpp-devel] cross compiling log4cpp from cygwin to mingw

[Bob R. <bob...@co...>]

Hi,

I've successfully cross compiled log4cpp on cygwin to mingw. I had to
make some changes, as it didn't compile out of the box.

The changes are attached. For some reason, the mingw compiler didn't
recognize the wstring type. Does this make sense? Also, it didn't
recongnize the in_addr_t type. Not sure what the correct solution for
that is. Would these changes, or something like them, be welcome upstream?

Thanks,
Bob Rossi

Re: [Log4cpp-devel] Seeking help with adapting log4cppwithnewloggingAPI library

[Matthew W. <ma...@sy...>]

I do want to stress that Pantheios is not conceived as a replacement for
other logging libraries, since it has only rudimentary transport of its own.
The intention is that the flexibility, robustness and performance is a
complement to the rich transport facilities of ACE, log4cpp, log4cplus,
log4cxx, etc.

In other words, we're not trying to trespass on log4cpp or steal its users.
:-)

Cheers

Matthew

Re: [Log4cpp-devel] Seeking help with adapting log4cpp withnewloggingAPI library

[Matthew W. <ma...@sy...>]

> Hello, Matthew!
> You wrote to "Konstantin Litvinenko"
> <Kon...@ma...>;
> <log...@li...> on Thu, 30 Nov 2006 21:02:29 +1100:
>
>  MW> Ah, silly me!
>
>  ??>>  Where can I get perfomance test sources?
>
>  MW> I've been meaning to add that into the distro for ages, but keep
>  MW> forgetting. I'm planning another beta (1.0.1. beta 10)
> tomorrow. I will
>  MW> include it with that.
>
>     Ok. Waiting.... :)

I've uploaded it just now, in a package imaginatively entitled "Performance
Tests".

Cheers

Matthew

Re: [Log4cpp-devel] Seeking help with adapting log4cpp with newloggingAPI library

[Konstantin L. <Kon...@ma...>]

SGVsbG8sIE1hdHRoZXchDQpZb3Ugd3JvdGUgdG8gIktvbnN0YW50aW4gTGl0dmluZW5rbyIgPEtv
bnN0YW50aW4uTGl0dmluZW5rb0BtYWx2YS51YT47IDxsb2c0Y3BwLWRldmVsQGxpc3RzLnNvdXJj
ZWZvcmdlLm5ldD4gb24gVGh1LCAzMCBOb3YgMjAwNiAyMTowMjoyOSArMTEwMDoNCg0KIE1XPiBB
aCwgc2lsbHkgbWUhDQoNCiA/Pz4+ICBXaGVyZSBjYW4gSSBnZXQgcGVyZm9tYW5jZSB0ZXN0IHNv
dXJjZXM/DQoNCiBNVz4gSSd2ZSBiZWVuIG1lYW5pbmcgdG8gYWRkIHRoYXQgaW50byB0aGUgZGlz
dHJvIGZvciBhZ2VzLCBidXQga2VlcA0KIE1XPiBmb3JnZXR0aW5nLiBJJ20gcGxhbm5pbmcgYW5v
dGhlciBiZXRhICgxLjAuMS4gYmV0YSAxMCkgdG9tb3Jyb3cuIEkgd2lsbA0KIE1XPiBpbmNsdWRl
IGl0IHdpdGggdGhhdC4NCg0KICAgIE9rLiBXYWl0aW5nLi4uLiA6KQ0KDQogPz8+PiAgIEkgcmVh
bGx5IGNhbid0IHVuZGVyc3RlbmQgaG93IHlvdSBsaWJyYXJ5IGNhbiBvdXRwZXJmb3JtIGxvZzRj
cHAgaW4gDQogPz8+PiBhbnkNCiBNVz4gdGVzdCBwcm92aWRlZC4NCg0KIE1XPiBXZWxsLCBpZiBh
IGdpdmVuIGxvZ2dpbmcgbGV2ZWwgaXMgc3dpdGNoZWQgb2ZmLCB0aGVyZSdyZSBubw0KIE1XPiBj
b252ZXJzaW9ucywgbm8gc3RybGVuKCksIG5vIHN0cmNweSgpLCBubyBtZW1vcnkgYWxsb2NhdGlv
bnM6IGluIGZhY3QsIA0KIE1XPiBubyBhY3Rpb25zIG9mIGFueSBraW5kLCBvdGhlciB0aGFuIHRo
ZSBzZXZlcml0eSB0ZXN0IGl0c2VsZiAtDQogTVc+IHBhbnRoZWlvczo6aXNTZXZlcml0eUxvZ2dl
ZCgpLg0KDQogICAgU2FtZSBhcyBsb2c0Y3BwLiBTbywgSSB3aWxsIHdhaXQgdW50aWwgdG9tb3Jy
b3cgdG8gZXhhbWluZSB0ZXN0IHNvdXJjZXMuDQoNCldpdGggYmVzdCByZWdhcmRzLCBLb25zdGFu
dGluIExpdHZpbmVua28u

Re: [Log4cpp-devel] Seeking help with adapting log4cpp with newloggingAPI library

[Matthew W. <ma...@sy...>]

Ah, silly me!

>  Where can I get perfomance test sources?

I've been meaning to add that into the distro for ages, but keep forgetting.
I'm planning another beta (1.0.1. beta 10) tomorrow. I will include it with
that.

>   I really can't understend how you library can outperform log4cpp in any
test provided.

Well, if a given logging level is switched off, there're no conversions, no
strlen(), no strcpy(), no memory allocations: in fact, no actions of any
kind, other than the severity test itself - pantheios::isSeverityLogged().

Cheers

Matthew

Re: [Log4cpp-devel] Seeking help with adapting log4cpp with new loggingAPI library

[Konstantin L. <Kon...@ma...>]

SGVsbG8sIE1hdHRoZXchDQpZb3Ugd3JvdGUgdG8gPGxvZzRjcHAtZGV2ZWxAbGlzdHMuc291cmNl
Zm9yZ2UubmV0PiBvbiBUaHUsIDMwIE5vdiAyMDA2IDE0OjAzOjIxICsxMTAwOg0KDQogTVc+IEFz
IHRoZSB3ZWJzaXRlIGV4cGxhaW5zLCB0aGlzIGNvbWVzIHdpdGggaXRzIG93biBiYXNpYyBsb2dn
aW5nDQogTVc+IHRyYW5zcG9ydCBmYWNpbGl0aWVzLiBCdXQgaXQgaXMgcmVhbGx5IGEgZmxleGli
bGUvZXh0ZW5zaWJsZSwgMTAwJQ0KIE1XPiB0eXBlLXNhZmUsIGFuZCB2ZXJ5IGVmZmljaWVudCAo
c2VlDQogTVc+IGh0dHA6Ly9wYW50aGVpb3Muc291cmNlZm9yZ2UubmV0L3BlcmZvcm1hbmNlLmh0
bWwpIGxheWVyIHRoYXQgY2FuIGJlDQogTVc+IHVzZWQgb3ZlciB0aGUgcmljaCB0cmFuc3BvcnQg
ZmFjaWxpdGllcyBvZiBhbnkgZXhpc3RpbmcgbG9nZ2luZw0KIE1XPiBsaWJyYXJ5LCBpbmNsdWRp
bmcgbG9nNGN4eCBvciBsb2c0Y3BwLg0KDQogICAgV2hlcmUgY2FuIEkgZ2V0IHBlcmZvbWFuY2Ug
dGVzdCBzb3VyY2VzPyBJIHJlYWxseSBjYW4ndCB1bmRlcnN0ZW5kIGhvdyB5b3UgbGlicmFyeSBj
YW4gb3V0cGVyZm9ybSBsb2c0Y3BwIGluIGFueSB0ZXN0IHByb3ZpZGVkLg0KDQpXaXRoIGJlc3Qg
cmVnYXJkcywgS29uc3RhbnRpbiBMaXR2aW5lbmtvLg==

[Log4cpp-devel] Seeking help with adapting log4cpp with new logging API library

[Matthew W. <ma...@sy...>]

Hi

I don't know if this is the done thing or not, but since the subject of
moribundity and other libraries has come up in the log4cxx mailing-list, I'd
like to draw people's attention to a new logging _API_ library that myself
and a colleague have recently released to the public domain: Pantheios
(http://pantheios.sourceforge.net/).

As the website explains, this comes with its own basic logging transport
facilities. But it is really a flexible/extensible, 100% type-safe, and very
efficient (see http://pantheios.sourceforge.net/performance.html) layer that
can be used over the rich transport facilities of any existing logging
library, including log4cxx or log4cpp.

We've an article coming out soon on The C++ Source
(http://artima.com/cppsource/) which will introduce it to the C++ world, so
to speak. But since the subject's been raised in the log4cxx forum, I
thought I'd give it a mention now.

The current beta contains two examples in which log4cxx
(examples/cpp/example_cpp_wrap_3pty_log_lib) and log4cplus
(examples/cpp/example_cpp_wrap_log4cplus) are wrapped. If anyone with
particular expertise with log4cxx, log4cplus and log4cpp would be willing to
lend a hand in producing actual bindings to these libraries, we'd be very
grateful. (Note: you can still use NDC's and all that stuff from within
application code, so Pantheios+log4XYZ offers the best of both worlds.)


Thanks for listening.

Matthew Wilson

Author: "Extended STL", Addison-Wesley, 2006
    http://www.extendedstl.com
Author: "Imperfect C++", Addison-Wesley, 2004
    http://www.imperfectcplusplus.com

"I can't sleep nights till I found out who hurled what ball through
what apparatus" -- Dr Niles Crane

[Log4cpp-devel] new account request

[Nasser O. <nos...@bl...>]

Please open an account for me. please use nossareh as my id.

 

Regards

nossareh

Re: [Log4cpp-devel] Adding appender and layout factories

[Konstantin L. <Kon...@ma...>]

SGVsbG8sIFBoaWxpcHBlIQ0KWW91IHdyb3RlIHRvICJLb25zdGFudGluIExpdHZpbmVua28iIDxL
b25zdGFudGluLkxpdHZpbmVua29AbWFsdmEudWE+IG9uIFR1ZSwgMTkgU2VwIDIwMDYgMTM6MTU6
NTkgKzAwMDAgKEdNVCk6DQoNCiBQSD4gIEl0IHN1cmUgd291bGQgYmUgYSB3b3J0aHdoaWxlIGlt
cHJvdmVtZW50IHRvIHRoZSBsaWJyYXJ5IGJ1dCBpdHMNCiBQSD4gZGV2ZWxvcG1lbnQgc2VlbXMg
dW5mb3J0dW5hdGVseSBmcm96ZW4gZm9yIGEgd2hpbGUgbm93Lk1heWJlIHlvdSBjb3VsZCANCiBQ
SD4gcG9zdCB5b3VyIGNvZGUgdG8gdGhlIGxvZzRjcHAgIkZlYXR1cmUgUmVxdWVzdHMiIGFyZWEg
c28gdGhhdCBpdCBjYW4gYmUNCiBQSD4gaW5jb3Jwb3JhdGVkIGF0IGxhdGVyIHRpbWVzIGluIGFu
IG9mZmljaWFsIHJlbGVhc2UgYW5kIGludGVyZXN0ZWQNCiBQSD4gZGV2ZWxvcGVycyBjYW4gdXNl
IGl0IGltbWVkaWF0ZWx5Lg0KDQogICAgSSBoYXZlIGNyZWF0ZWQgc3VzaCBmZWF0dXJlIHJlcXVl
c3Qgd2l0aCBhdHRhY2hlZCBpbXBsZW1lbnRhdGlvbiBodHRwOi8vc291cmNlZm9yZ2UubmV0L3Ry
YWNrZXIvaW5kZXgucGhwP2Z1bmM9ZGV0YWlsJmFpZD0xNTYzMzM2Jmdyb3VwX2lkPTE1MTkwJmF0
aWQ9MzY1MTkwDQogICAgQWxzbyBJIHBsYW4gdG8gYWRkIGJ1ZmZlcmluZyBhcHBlbmRlciB0byBh
bGxvdyB3cml0aW5nIGxvZyBtZXNzYWdlcyBpbiBvbmUgc2hvdC4gVGhpcyBmYWNpbGl0eSB3aWxs
IGJlIHVzZWZ1bGwgdG8gc21wdCBhcHBlbmRlciBhbmQgZm9yIG90aGVycyBhcHBlbmRlcnMgZm9y
IHBlcmZvcm1hbmNlIHJlYXNvbnMuDQogICAgUGxlYXNlIGxvb2sgYXQgbXkgaW1wbGVtZW50YXRp
b24gYW5kIGNvbW1lbnQgaXQuDQogICAgVGhhbnguDQoNCldpdGggYmVzdCByZWdhcmRzLCBLb25z
dGFudGluIExpdHZpbmVua28u

Re: [Log4cpp-devel] Adding appender and layout factories

[Thomas W. <wa...@ho...>]

Hi Konstantin,

it would be nice to get such feature in. Have you CVS acess or can you
send me an patch? It would be the best to create a tracker item on
sourceforge and attach the patch to it, thus any developers of interest
can have a look at your suggestions.

Regards,

- waffel

On Mon, 2006-09-18 at 10:08 +0300, Konstantin Litvinenko wrote:
> Hello All!
> 
>     I use log4cpp over 3 past years and find it very helpfull. But I face up with a problem when extending it with additional appenders/layouts. Also I wrote xml configurator to configure log4cpp. But again, without factories for appenders and layouts I can't make configurator code independent of appender's/layout's creation code. So, I wrote these factories and that makes life much easy.
> 
>     Is there any interest to add these factionality into the library?
> 
> PS. Sory, about bad english :)
> 
> With best regards, Konstantin Litvinenko.
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel

[Log4cpp-devel] Adding appender and layout factories

[Konstantin L. <Kon...@ma...>]

SGVsbG8gQWxsIQ0KDQogICAgSSB1c2UgbG9nNGNwcCBvdmVyIDMgcGFzdCB5ZWFycyBhbmQgZmlu
ZCBpdCB2ZXJ5IGhlbHBmdWxsLiBCdXQgSSBmYWNlIHVwIHdpdGggYSBwcm9ibGVtIHdoZW4gZXh0
ZW5kaW5nIGl0IHdpdGggYWRkaXRpb25hbCBhcHBlbmRlcnMvbGF5b3V0cy4gQWxzbyBJIHdyb3Rl
IHhtbCBjb25maWd1cmF0b3IgdG8gY29uZmlndXJlIGxvZzRjcHAuIEJ1dCBhZ2Fpbiwgd2l0aG91
dCBmYWN0b3JpZXMgZm9yIGFwcGVuZGVycyBhbmQgbGF5b3V0cyBJIGNhbid0IG1ha2UgY29uZmln
dXJhdG9yIGNvZGUgaW5kZXBlbmRlbnQgb2YgYXBwZW5kZXIncy9sYXlvdXQncyBjcmVhdGlvbiBj
b2RlLiBTbywgSSB3cm90ZSB0aGVzZSBmYWN0b3JpZXMgYW5kIHRoYXQgbWFrZXMgbGlmZSBtdWNo
IGVhc3kuDQoNCiAgICBJcyB0aGVyZSBhbnkgaW50ZXJlc3QgdG8gYWRkIHRoZXNlIGZhY3Rpb25h
bGl0eSBpbnRvIHRoZSBsaWJyYXJ5Pw0KDQpQUy4gU29yeSwgYWJvdXQgYmFkIGVuZ2xpc2ggOikN
Cg0KV2l0aCBiZXN0IHJlZ2FyZHMsIEtvbnN0YW50aW4gTGl0dmluZW5rby4=

[Log4cpp-devel] Memory Leak patch

[Mark <mar...@ya...>]

Hello,

There was a message posted here about three years ago
with a patch that purported to fix some of the memory
leak on shutdown problems.

The link to the archived message is:

http://sourceforge.net/mailarchive/forum.php?thread_id=2007464&forum_id=2367

I was trying to implement it but all I had was what
was in the archive (it is not in CVS), which was cut
off.  There is at least one whole header file missing
(LoggerRepository.hh).

If anyone has this and can send it to me or post it I
would be grateful.

Thanks.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Log4cpp-devel] IP address bug in RemoteSyslogAppender

[Chris C. <Chr...@hi...>]

Hello all,

=20

I have experienced a bug using the RemoteSyslogAppender running on Win32
where it would improperly store ip addresses. On line #111 (version
.3.5rc3), _ipAddr =3D *(pent->h_addr); seems to only store the first two
bytes of the ip address.

=20

By changing that line to the following line:

memcpy(&_ipAddr, pent->h_addr, pent->h_length);

I was able to get the correct behavior.

=20

Please let me know if you need more information on duplicating this
behavior or any assistance in applying this bugfix.

=20

--Christopher Conroy

=20

[Log4cpp-devel] Linker trubles in Builder C++ 5

[Dorin M. <Dor...@da...>]

Hi all ! I got a realy bad day..

Downloading sources for log4cpp-0.3.5rc3

And trying to compile test projects I always get Linker problems:

=20

[C++ Warning] CategoryStream.cpp(46): W8060 Possibly incorrect
assignment

[C++ Warning] FixedContextCategory.hh(171): W8022
'FixedContextCategory::ownsAppender() const throw()' hides virtual
function 'Category::ownsAppender(Appender *,__rwstd::__rb_tree<Appender
*,std::pair<Appender *
const,bool>,__rwstd::__select1st<std::pair<Appender *
const,bool>,Appender *>,std::less<Appender
*>,std::allocator<std::pair<Appender * const,bool> > >::iterator &)
throw()'

[C++ Warning] PatternLayout.cpp(367): W8030 Temporary used for parameter
'x' in call to 'std::vector<PatternLayout::PatternComponent
*,std::allocator<PatternLayout::PatternComponent *>
>::push_back(PatternLayout::PatternComponent * const &)'

[C++ Warning] PatternLayout.cpp(382): W8030 Temporary used for parameter
'x' in call to 'std::vector<PatternLayout::PatternComponent
*,std::allocator<PatternLayout::PatternComponent *>
>::push_back(PatternLayout::PatternComponent * const &)'

[C++ Warning] PropertyConfiguratorImpl.cpp(128): W8004 'value' is
assigned a value that is never used

[C++ Warning] RemoteSyslogAppender.cpp(115): W8008 Condition is always
false

[Linker Error] Unresolved external
'log4cpp::AbortAppender::~AbortAppender()' referenced from
D:\TMP\LOG4CPP-0.3.5RC3\BCB5\LOG4CPP\PROPERTYCONFIGURATORIMPL.OBJ

[Linker Error] Unresolved external
'log4cpp::Win32DebugAppender::~Win32DebugAppender()' referenced from
D:\TMP\LOG4CPP-0.3.5RC3\BCB5\LOG4CPP\PROPERTYCONFIGURATORIMPL.OBJ

[Linker Error] Unresolved external
'log4cpp::NTEventLogAppender::~NTEventLogAppender()' referenced from
D:\TMP\LOG4CPP-0.3.5RC3\BCB5\LOG4CPP\PROPERTYCONFIGURATORIMPL.OBJ

[Linker Error] Unresolved external
'log4cpp::AbortAppender::AbortAppender(const std::basic_string<char,
std::char_traits<char>, std::allocator<char> >&)' referenced from
D:\TMP\LOG4CPP-0.3.5RC3\BCB5\LOG4CPP\PROPERTYCONFIGURATORIMPL.OBJ

[Linker Error] Unresolved external
'log4cpp::Win32DebugAppender::Win32DebugAppender(const
std::basic_string<char, std::char_traits<char>, std::allocator<char>
>&)' referenced from
D:\TMP\LOG4CPP-0.3.5RC3\BCB5\LOG4CPP\PROPERTYCONFIGURATORIMPL.OBJ

[Linker Error] Unresolved external
'log4cpp::NTEventLogAppender::NTEventLogAppender(const
std::basic_string<char, std::char_traits<char>, std::allocator<char> >&,
const std::basic_string<char, std::char_traits<char>,
std::allocator<char> >&)' referenced from
D:\TMP\LOG4CPP-0.3.5RC3\BCB5\LOG4CPP\PROPERTYCONFIGURATORIMPL.OBJ

=20

P.S. I compiling testConfig project

RE: [Log4cpp-devel] few questions on log4cpp

[Philippe H. <phi...@ya...>]

Hello,

>    1. where can I find the whole list of specifiers
> like (%R, %x, %m etc.)?
It is associated with the PatternLayout class in
doxygen generated documentation and looks like this :
# %c - the category
# %d - the date
# %D - seconds since 1970
# %m - the message
# %n - the platform specific line separator
# %p - the priority
# %r - milliseconds since this layout was created.
# %R - seconds since Jan 1, 1970
# %u - clock ticks since process start
# %x - the NDC

>    2. what is the difference between the files
> log4cpp.init and log4cpp.properties? and How to
> write those files?
The best documentation we found for this was in the
PropertyConfiguratorImpl.cpp source file, which gives
you the list of existing appenders and the associated
properties.

>    4. which version of log4cpp is thread-safe.
None.
We submitted a patch (id 1368387) for a blatant
problem about thread safety in log4cpp 0.3.5rc3
CategoryStream class several months ago but got no
answer.

Regards,

PH







	

	
		
___________________________________________________________________________ 
Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. 
Rendez-vous sur http://fr.yahoo.com/set

[Log4cpp-devel] few questions on log4cpp

[girish h. <gir...@ya...>]

Hello Everybody,
                                                      
                                                      
                                 
   I have some questions in regard to log4cpp:
   1. where can I find the whole list of specifiers
like (%R, %x, %m etc.)?
   2. what is the difference between the files
log4cpp.init and log4cpp.properties? and How to write
those files?
   3. how to pass some extra arguments like
'thread-id', 'ip-address', 'port' etc. to the error(),
warn() functions so that we can rearrange them in the
final log line.
   4. which version of log4cpp is thread-safe.
                                                      
                                                      
                                 
   5. I downloaded the version 'log4cpp-0.3.5rc3' but
the command "./configure --with-threads" is giving
following error :
   [girish@malgudi log4cpp-0.3.5rc3]$ ./configure
--with-threads
   checking for a BSD-compatible install...
/usr/bin/install -c
   checking whether build environment is sane... yes
   checking for gawk... gawk
   checking whether make sets $(MAKE)... ./configure:
line 1: ac_make
                                                      
                                                      
                                 
   checking build system type... config/config.guess:
line 1:s: line 1: 31mLIBC=gnu: command not found
   config/config.guess: line 1:s: line 1: 31mLIBC=gnu:
command not found
   Invalid configuration `i686-pc-linux-': machine
`i686-pc-linux' not recognized
   configure: error: /bin/sh config/config.sub
i686-pc-linux- failed
                                                      
                                                      
                                 
   I will be thankful if anybody could help me in this
regard.
                                                      
                                                      
                                 
Thanks,
Girish

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Log4cpp-devel] extra semicolon in Manipulator.hh

[Robert H. <rha...@sl...>]

Hi,
 log4cpp wouldn't build under gcc 3.4.3 because Manipulator.hh had an
extra semicolon at the end of the namespace's final brace (older versions
of gcc were more forgiving of such spurious semicolons).

-robert


Robert W. Hatcher   | rha...@fn...   630-840-3102
FNAL CD/EXP (MINOS) | MS 220, PO Box 500, Batavia IL 60510

Re: [Log4cpp-devel] log4cpp 0.3.4b in debian unstable

[Thomas W. <tho...@ho...>]

Many Thanks Fathi!

Because I MUST! :-( currently work under windows I will check your sugestions later ...

Regards,

- waffel

> hi,
> 
> log4cpp 0.3.4b is now in debian unstable.
> 
> cheers,
> 
> Fathi
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel


---
This mail was sent with the Java email client Columba. Read more at http://columbamail.org

[Log4cpp-devel] log4cpp 0.3.4b in debian unstable

[Fathi B. <fb...@fr...>]

hi,

log4cpp 0.3.4b is now in debian unstable.

cheers,

Fathi

Re: [Log4cpp-devel] log4cpp 0.3.4b build system

[Fathi B. <fb...@fr...>]

> after the cvs commit I will check it for myself and then we should create a
> minor release :-)

hi thomas,

i'm not registred to log4cpp project so i can't commit my minor update.
for the next time, my sourceforge id : fboudra

anyway to update build system, you only need to do (i used automake 1.9 series 
and libtool 1.5 series):
# bring configure script up to date
aclocal -I m4
autoconf
automake -a -c

# bring ltmain.sh, config.guess and config.sub scripts up to date
libtoolize --copy --force

also, i removed debian dir dependency. i join the patch.

cheers,

Fathi

PS: if you can delete the debian dir from source package, it will not be 
needed there anymore.