Below is the report we had created describing the resolution to a
series of sporadic Apache child process segfaults. It is being posted
here so that, as the message has it, "it will be archived and
Googlable".
++
Executive Summar
Quick patch to add a function dio_modemget() to the DirectIO extension.
Does an ioctl(TIOCMGET) to get the status of the modem control lines.
array dio_modemget(fd descriptor)
Returns an array with elements "dsr", "cts", etc equal to 1 or 0.
Example output:
array(6) {
["dsr"]=>
int(0)
yes you right again , but as i suggested , adn thinking that problem is
existin in this scenatrio
cert.cpp (main file with all PHP required defitions and becoming a big
source file; all php includes surrounded by extern "C" {})
php_TPKCS12.cpp have only functions related to PKCS#12 treating
(en
No, that only prevents the file being included twice in the same .cpp file.
The solution to this problem is to move the function bodies into their own
.cpp file:
foo.h:
class Foo {
Foo();
~Foo();
};
fooclass.cpp:
Foo::Foo() { ... }
Foo::~Foo() { ... }
--Wez.
- Original Message -
From:
you are right , and for those cases there a preprocessor protection
#ifndef DO_NOT_MAKE_BOBO
#define DO_NOT_MAKE_BOBO
class Foo{
Foo(){...}
~Foo(){...}
};
#endif
isn't it?
Wez Furlong wrote:
This sounds like the "rookie" mistake of declaring your functions inline in
the class defin
This sounds like the "rookie" mistake of declaring your functions inline in
the class definition in the header files, and then including those headers
in multiple files.
eg: foo.h:
class Foo {
Foo() { ... }
~Foo() { ... }
};
foo.cpp:
#include "foo.h"
bar.cpp:
#include "foo.h"
== linker pro
I'm assuming "delete" isn't a function but the C++ operator delete. You're
probably #including the same file more than once, but I doubt it's in Zend.
If all else fails, you can try passing "/FORCE" to the linker options and
it'll try to force the linkage. It might result in a broken binary, tho
CVS maintainance for my PEAR package Image_GraphViz
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I developing some extension on m$ platform with M$VC6.0 ( it's a OpenSSL crypto
capabilities, more advanced than OpenSSL extension providing, when i fill it
ready i will try to publish to PHP site) when core language for internals is a
C++, meaning inside implementation of PHP functions there ca
I want to be part of developing the www.php.net site. I mean maintaining it.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
At 13:54 17/09/2003, Marcus Börger wrote:
Here you go :-)
As you can see i need one additional emalloc in compile which should be ok
but also one additional emalloc/lowercase operation for dynamic function
calls with static function names. That is you are going to use a function
prior to declaring
Hello Andi,
Wednesday, September 17, 2003, 6:07:40 AM, you wrote:
> At 10:10 PM 9/16/2003 +0200, Marcus Börger wrote:
>>Hello Andi,
>>
>>Tuesday, September 16, 2003, 9:37:40 PM, you wrote:
>>
>> > I think this patch is fine.
>> > I think (1) can be fixed quite easily. What do you mean when you sa
12 matches
Mail list logo
