similar to: Compiling latest svn revision

g' day Configured with --disable-maintainer-mode. Compilation of revision 13824 is failing with: common/serialise-double.cc: In function ?double unserialise_double(const char**, const char*)?: common/serialise-double.cc:141: error: ?SerialisationError? is not a member of ?Xapian? common/serialise-double.cc:157: error: ?SerialisationError? is not a member of ?Xapian?

Greetings, I've been wondering about the index format and backwards compatibility. We're using the dev version (for chert) and each svn up means that any indexes created prior to this revision cannot be read. Is this purely a cautious move to prevent errors, and, barring any obvious index format changes, can I safely force the current revision to read existing indexes? eg, by

When a highly multi-threaded program such as nbdcopy encounters an error, there is a race condition in the library which can cause an assertion failure and thus a core dump: (1) An error occurs on one of the threads. nbdcopy calls exit(3). (2) In lib/errors.c, the destructor calls pthread_key_delete. (3) Another thread which is still running also encounters an error, and inside libnbd the

stubdom: fix and clean pthread minimal support Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r f4a293cbec1b extras/mini-os/include/posix/pthread.h --- a/extras/mini-os/include/posix/pthread.h Thu May 22 14:28:40 2008 +0100 +++ b/extras/mini-os/include/posix/pthread.h Thu May 22 16:08:29 2008 +0100 @@ -1,18 +1,56 @@ #ifndef _POSIX_PTHREAD_H #define _POSIX_PTHREAD_H

When a highly multi-threaded program such as nbdcopy encounters an error, there is a race condition in the library which can cause an assertion failure and thus a core dump: (1) An error occurs on one of the threads. nbdcopy calls exit(3). (2) In lib/errors.c, the destructor calls pthread_key_delete. (3) Another thread which is still running also encounters an error, and inside libnbd the

On 11/16/2017 09:13 PM, Eric Blake wrote: > We can't guarantee what storage duration the caller's request > for a thread name has; and in fact, if the caller uses > plugin_name() for their thread name, then the moment .unload > is called, our threadlocal storage is pointing to la-la-land > and we get a nice SEGV while trying to print any debug message. > So copy the

The plugin interface was impliticly using the last errno value as the source for any error code sent over the wire to the client. This is okay for C, but in other language bindings, it gets rather awkward when you can't guarantee what errno will even be set to by the time the binding glue has finished executing. The solution is to expose an explicit utility function for setting the preferred

Greets, WRT this discussion: http://lists.xapian.org/pipermail/xapian-discuss/2009-November/007300.html Richard recommends calling flush() before closing a index database segment, etc. Well, I can confirm that calling flush() is *required* before calling close() since close() on it's own does not commit/flush any pending writes/whatever unless the Perl script terminates, etc. So, for a

On Thu, Mar 09, 2023 at 09:50:00AM +0000, Richard W.M. Jones wrote: > When a highly multi-threaded program such as nbdcopy encounters an > error, there is a race condition in the library which can cause an > assertion failure and thus a core dump: > > (1) An error occurs on one of the threads. nbdcopy calls exit(3). > > (2) In lib/errors.c, the destructor calls

Hello all, I have been taking basic steps with DTrace and subscribed today to this list. I have written a simple DTrace script to trace all the function entry/exit from a given function: #pragma D option flowindent pid$1::*mysql_select*:entry { self -> start = vtimestamp ; } pid$1::*mysql_select*:return /self -> start/ { self -> start =0 ; } pid$1:::entry, pid$1:::return

Hi all, Since upgrading to perl 5.8.5-36.el4_5.2 I have had no end of problems, starting with needing compress::zlib which I got from rpmforge, then I had to reinstall scalar::util to get mailscanner working but now I can't install or upgrade any perl modules. Has anyone else had problems or can someone tell me what I've done wrong please? regards tom

When a highly multi-threaded program such as nbdcopy encounters an error, there is a race condition in the library which can cause an assertion failure and thus a core dump: (1) An error occurs on one of the threads. nbdcopy calls exit(3). (2) In lib/errors.c, the destructor calls pthread_key_delete. (3) Another thread which is still running also encounters an error, and inside libnbd the

When a highly multi-threaded program such as nbdcopy encounters an error, there is a race condition in the library which can cause an assertion failure and thus a core dump: (1) An error occurs on one of the threads. nbdcopy calls exit(3). (2) In lib/errors.c, the destructor calls pthread_key_delete. (3) Another thread which is still running also encounters an error, and inside libnbd the

We can't guarantee what storage duration the caller's request for a thread name has; and in fact, if the caller uses plugin_name() for their thread name, then the moment .unload is called, our threadlocal storage is pointing to la-la-land and we get a nice SEGV while trying to print any debug message. So copy the user's string instead. Signed-off-by: Eric Blake

On Tue, Aug 18, 2015 at 10:53 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 18 August 2015 at 19:57, Dmitry Vyukov <dvyukov at google.com> wrote: >> Hi Renato, >> >> What exactly hack/hacks do you mean? > > Hi Dmitry, > > The sanitizer code seems to be more accepting to adding complicated > pre-processor logic, as well as a number of

On 4/23/19 10:09 AM, Richard W.M. Jones wrote: > If the plugin .pread method did not fill the buffer with data then the > contents of the heap could be leaked back to the client. To avoid > this create a thread-local data buffer which is initialized to zero > and expanded (with zeroes) as required. > > This buffer is shared between pread and pwrite which makes the code a >

On Thu, Mar 09, 2023 at 08:44:51AM +0000, Richard W.M. Jones wrote: > When a highly multi-threaded program such as nbdcopy encounters an > error, there is a race condition in the library which can cause an > assertion failure and thus a core dump: > > (1) An error occurs on one of the threads. nbdcopy calls exit(3). > > (2) In lib/errors.c, the destructor calls

Hi, I found that building LLVM in single-threaded mode with CMake is failing because some object files still have references to pthread routines. There are two instances of the build failure happening. $ cmake .../llvm/ -DLLVM_ENABLE_THREADS=0 $ make -j8 check-all % Linking CXX executable IRTests ../../lib/libgtest.a(gtest.cc.o): In function

On Sun, Jul 3, 2011 at 9:07 AM, Chris Lattner <clattner at apple.com> wrote: > Hi Talin, > > Interesting post, > > On Jul 1, 2011, at 11:05 AM, Talin wrote: > > *Garbage collection is still way too difficult*. The biggest problem is > the inability to track SSA values - it requires the > > > *Light-weight coroutines* would be a "nice to have", as

On Tue, Jul 5, 2011 at 11:35 AM, Talin <viridia at gmail.com> wrote: > On Sun, Jul 3, 2011 at 9:07 AM, Chris Lattner <clattner at apple.com> wrote: > >> Hi Talin, >> >> Interesting post, >> >> On Jul 1, 2011, at 11:05 AM, Talin wrote: >> >> *Garbage collection is still way too difficult*. The biggest problem is >> the inability to