mturk 2005/02/06 05:45:11
Modified:jk/native/common jk_ajp13_worker.c jk_ajp14.h
jk_ajp14_worker.c jk_ajp_common.c
Log:
Remove unneeded strdup's by changing some properties to const char..
Revision ChangesPath
1.23 +2 -10
jakarta-tomcat
mturk 2004/11/26 08:59:52
Modified:jk/native/common jk_ajp13_worker.c jk_ajp14.c
jk_ajp14_worker.c jk_ajp_common.c jk_jni_worker.c
jk_lb_worker.c
Log:
Use calloc instead malloc for initalizing stucts, so we can use default zeros
TAKE MY EMAIL OFF OF YOUR LIST. THANK YOU
Costin Manolache <[EMAIL PROTECTED]> wrote:Mladen Turk wrote:
> jean-frederic clere wrote:
>
>> Mladen Turk wrote:
>>
>>> Costin Manolache wrote:
>>>
Are you joking :-) ?
>>>
>>>
>>> If we can not alloc couple of bytes from the system, then the
>>> e
mturk 2004/11/11 09:28:59
Modified:jk/native/common jk_ajp13_worker.c
Log:
Add new trace macros and clean up some log messages.
Revision ChangesPath
1.19 +23 -14
jakarta-tomcat-connectors/jk/native/common/jk_ajp13_worker.c
Index: jk_ajp13_worker.c
==
Mladen Turk wrote:
jean-frederic clere wrote:
Mladen Turk wrote:
Costin Manolache wrote:
Are you joking :-) ?
If we can not alloc couple of bytes from the system, then the
entire system is unstable.
Or that the process that makes the malloc() has reached a configurable
limit of the amount of mem
jean-frederic clere wrote:
Mladen Turk wrote:
Costin Manolache wrote:
Are you joking :-) ?
If we can not alloc couple of bytes from the system, then the
entire system is unstable.
Or that the process that makes the malloc() has reached a configurable
limit of the amount of memory it is allowed to
Mladen Turk wrote:
Costin Manolache wrote:
Mladen Turk wrote:
David Rees wrote:
Are you sure it's a good idea to wait until it crashes rather than
fail in a controlled method? How much overhead is there to check
aw->name for NULL? Can't be much...
Yes I am.
Look, if the system can not alloc 10
Costin Manolache wrote:
Mladen Turk wrote:
David Rees wrote:
Are you sure it's a good idea to wait until it crashes rather than
fail in a controlled method? How much overhead is there to check
aw->name for NULL? Can't be much...
Yes I am.
Look, if the system can not alloc 1000 bytes of memory
Mladen Turk wrote:
David Rees wrote:
Are you sure it's a good idea to wait until it crashes rather than
fail in a controlled method? How much overhead is there to check
aw->name for NULL? Can't be much...
Yes I am.
Look, if the system can not alloc 1000 bytes of memory what's
the purpose to co
David Rees wrote:
Are you sure it's a good idea to wait until it crashes rather than fail
in a controlled method? How much overhead is there to check aw->name
for NULL? Can't be much...
Yes I am.
Look, if the system can not alloc 1000 bytes of memory what's
the purpose to continue?
Mt.
---
[EMAIL PROTECTED] wrote, On 11/10/2004 7:24 AM:
mturk 2004/11/10 07:24:17
Modified:jk/native/common jk_ajp13_worker.c
Log:
Use new TRACE/DEBUG logging.
Also skip checking for memory allocation.
If we can not allocate enough memory it's better to core dump
then try to continue.
mturk 2004/11/10 07:47:56
Modified:jk/native/common jk_ajp13_worker.c jk_ajp14.c jk_logger.h
Log:
Use new TRACE macros.
Revision ChangesPath
1.17 +6 -6
jakarta-tomcat-connectors/jk/native/common/jk_ajp13_worker.c
Index: jk_ajp13_worker.c
==
mturk 2004/11/10 07:24:17
Modified:jk/native/common jk_ajp13_worker.c
Log:
Use new TRACE/DEBUG logging.
Also skip checking for memory allocation.
If we can not allocate enough memory it's better to core dump
then try to continue. At some point we'll core dump anyhow, so
why
13 matches
Mail list logo
