Am I then only one thinking that etckeeper should have post-install
script to request git user.name and user.email fields to be filled for
root if those are missing? I know how to do that manually but I guess
random etckeeper user may not know that those are needed and it would be
much better user
The justification for this fix is as follows:
- The patch is obviously safe (it does not touch code outside the
functions mentioned in the description and those functions are already
broken)
- The patch affects PostgreSQL library of PHP, no critical
infrastructure or kernel
- The bug may cause
Public bug reported:
(I think the package should be php5-pgsql but launchpad wants me to use
php5 for some reason.)
pg_send_query() fails because of an implementation error if connection
is done to remote host and query string is long OR transaction is very
long.
The problem is caused by the
Public bug reported:
See the attached test case. The Outer::runInner() throws a test
exception that is supposed to be catched in Outer::run(). However,
before this the destructor of Inner will run as a result of stack
unwinding while returning from Outer::runInner(). This, in turn, causes
the
** Attachment added: minimal test case
https://bugs.launchpad.net/bugs/1042711/+attachment/3280442/+files/throw-test.php
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1042711
It just occurred to me that the test case written a bit differently
could be program logic guarding authenticated session.
As a result, I'm marking this bug as security but keeping it still
public because I'm not aware of real world PHP program suffering from a
security issue because of this
*** This bug is a duplicate of bug 343870 ***
https://bugs.launchpad.net/bugs/343870
** Visibility changed to: Public
--
php5 crashed with SIGSEGV in _Unwind_ForcedUnwind()
https://bugs.launchpad.net/bugs/459048
You received this bug notification because you are a member of Ubuntu
Server
Checked against lucid inside VirtualBox OSE and could not reproduce the
problem anymore. I'm able to reproduce against karmic even inside
VirtualBox (and on real hardware, too).
--
php-cli segmentation fault with mysql extension
https://bugs.launchpad.net/bugs/343870
You received this bug
Reproduced with 64 bit Karmic. See bug 459048 for stack trace.
--
php-cli segmentation fault with mysql extension
https://bugs.launchpad.net/bugs/343870
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
To reproduce in Jaunty (may require at least two physical CPU cores
because this is a race condition) simply run the following bash command:
$ while true; do php -r ; done
(hit CTRL+C after seeing at least one Segmentation fault)
The above code repeatedly starts php interpreter and runs no code
Probably related (or same as) http://bugs.mysql.com/bug.php?id=42850
That bug is caused by http://bugs.mysql.com/bug.php?id=24507 which is a
(not so good) workaround for a glibc bug
(http://sourceware.org/bugzilla/show_bug.cgi?id=2644). If the glibc bug
is fixed in the currently distributed
Public bug reported:
Binary package hint: php5
This may be related to bug 259479.
Steps to reproduce (with command line php, see the attached file):
1) $ php test.php
Seems to be some kind of race condition because it only happens every
now and then. Here's a backtrace from a core dump:
(gdb)
** Attachment added: A simple PHP test file which causes a SIGSEGV sometimes
http://launchpadlibrarian.net/26070110/test.php
--
php5 crashed with SIGSEGV in _Unwind_ForcedUnwind()
https://bugs.launchpad.net/bugs/368585
You received this bug notification because you are a member of Ubuntu
13 matches
Mail list logo
