Displaying 20 results from an estimated 31489 matches for "optimizer".
Did you mean:
optimized
2018 Dec 04
2
[2.3.4] Segmentation faults
Hi
How to solve this ?
So many similar segfaults
Thank you
On 2018-11-30 06:11, Joan Moreau wrote:
> ANother (very very long) example :
>
> # gdb /usr/libexec/dovecot/indexer-worker core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.1543533424000000
> GNU gdb (GDB) 8.2
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or
2018 Dec 04
3
[2.3.4] Segmentation faults
Thanks for mySql
For Squat vs Solr, Solr does not reach Squat by very far in terms of
results : If I setup Solr, and search (via the search in Roundbube or
Evolution) for a keyword or part of the keyword, the results are
complete non sense. The diference between "search in full body" and
"search in fields" does not even work.
Solr with Dovecot seems very early beta
2018 Dec 04
2
[2.3.4] Segmentation faults
> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>
> We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
FWIW, Squat has been deprecated since 2.0, so none of this should come as a surprise.
https://wiki.dovecot.org/Plugins/FTS
> Aki
>
> > On 04 December
2018 Dec 04
0
[2.3.4] Segmentation faults
> On 04 December 2018 at 16:46 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
>
> Hi
>
> How to solve this ?
>
> So many similar segfaults
>
> Thank you
>
> On 2018-11-30 06:11, Joan Moreau wrote:
>
> > ANother (very very long) example :
> >
> > # gdb /usr/libexec/dovecot/indexer-worker
2018 Dec 04
0
[2.3.4] Segmentation faults
We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
Aki
> On 04 December 2018 at 17:16 Joan Moreau <jom at grosjo.net> wrote:
>
>
> Thanks for mySql
>
> For Squat vs Solr, Solr does not reach Squat by very far in terms of
> results : If I setup Solr, and search (via the search in Roundbube
2018 Dec 04
0
Squat
Yes, but the bottom line is that Squat does the job needed for end
users, Solr does not
On 2018-12-04 16:53, Michael Slusarz wrote:
>> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>>
>> We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
>
> FWIW, Squat
2017 Jun 27
0
Seg Fault memory violation
Greetings all,
Recently ran into a seg fault the keeps reoccurring whenever R-java is used (I believe). Not sure if this is an R issue or an openjdk issue so I'm trying to cover all bases with this report. I tried downgrading R version from 3.4.0 to 3.3.3 with the same results. Also tried downgrading java version from 1.8 to 1.7 with no luck. Running on a fully updated CentOS 7 x86_64,
2017 Dec 06
0
[Gluster-devel] Crash in glusterd!!!
Hi Atin,
Please find the backtrace and logs files attached here.
Also, below are the BT from core.
(gdb) bt
#0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at
../sysdeps/unix/sysv/linux/raise.c:55
#1 0x00003fff88350fd0 in __GI_abort () at abort.c:89
[**ALERT: The abort() might not be exactly invoked from the following
function line.
If the trail function
2017 Dec 06
1
[Gluster-devel] Crash in glusterd!!!
I hope these logs were sufficient... please let me know if you require more
logs.
On Wed, Dec 6, 2017 at 3:26 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com>
wrote:
> Hi Atin,
>
> Please find the backtrace and logs files attached here.
>
> Also, below are the BT from core.
>
> (gdb) bt
>
> #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at
>
2018 Nov 29
3
[2.3.4] Segmentation faults
finally managed to locate the dump
here the output:
# gdb /usr/libexec/dovecot/auth
/var/lib/systemd/coredump/core.auth.0.3a33f56105e043de802a7dfcee265a07.28130.1543516118000000
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
2016 Oct 06
2
[imap-login] SSL related crashes using the latest 2.2.25
I'm running Dovecot as proxy in front of some IMAP/POP3 Dovecot &
Courier-IMAP servers and in the last couple of days I've been seeing a
lot of imap-login crashes (signal 11) on both 2.2.18 and 2.2.25, all SSL
related. The following backtraces are taken running 2.2.25, built from
source on a test system similar to the live proxy servers.
OS: CentOS 6.8 64bit
Packages:
2020 Sep 13
2
libva-utils test siuite is crashing in nouveau sriver
Hi,
I'm hitting that issue since Mesa 20.0.6 and it is present still in latest
version 20.1.7
```
[tkloczko at barrel SPECS]$ coredumpctl gdb 3926866
PID: 3926866 (test_va_api)
UID: 1000 (tkloczko)
GID: 1000 (tkloczko)
Signal: 11 (SEGV)
Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago)
Command Line: ./test_va_api
Executable:
2008 Jun 05
4
[Bug 16241] New: assertion failed: (movie->cache_state <= SWFDEC_MOVIE_INVALID_CHILDREN)
http://bugs.freedesktop.org/show_bug.cgi?id=16241
Summary: assertion failed: (movie->cache_state <=
SWFDEC_MOVIE_INVALID_CHILDREN)
Product: swfdec
Version: git
Platform: x86-64 (AMD64)
URL: http://www.cnn.com/ELECTION/2008/primaries/results/score
card/#R
OS/Version: Linux (All)
2017 Dec 06
2
[Gluster-devel] Crash in glusterd!!!
Without the glusterd log file and the core file or the backtrace I can't
comment anything.
On Wed, Dec 6, 2017 at 3:09 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com>
wrote:
> Any suggestion....
>
> On Dec 6, 2017 11:51, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote:
>
>> Hi Team,
>>
>> We are getting the crash in glusterd after
2018 Jun 25
2
Samba 4.7.1 Generating Core Dumps
Hi,
We are having issues with our samba server running on CentOS 7. It's generating core dumps and dumping them in the / (root filesystem) directory in the form of core.##### where the # is a series of numbers.
Snippets of log files and some troubleshooting commands are below. Hope someone can have a look and see if I should file this as a bug, as there were similar posts in the samba
2018 Nov 30
0
[2.3.4] Segmentation faults
ANother (very very long) example :
# gdb /usr/libexec/dovecot/indexer-worker
core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.1543533424000000
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to
2014 Feb 23
1
2.2.12: Panic: file mail-index.c: line 380 (mail_index_keywords_unref): assertion failed: (keywords->refcount > 0)
I upgraded 2.1 -> 2.2 something like a week ago because I needed
INDEXPVT. Not sure if this crash started immediately or not, noticed it
today looking at journalctl.
Backtrace http://bpaste.net/raw/181944/ and pasted below.
This seems to crash on every IMAP connection made, so any ideas for a
possible client-level workaround are quite welcome until dovecot code
improves here.
root at
2012 Mar 21
1
enableJIT() and internal R completions (was: [ESS-bugs] ess-mode 12.03; ess hangs emacs)
Hello,
JIT compiler interferes with internal R completions:
compiler::enableJIT(2)
utils:::functionArgs("density", '')
gives:
utils:::functionArgs("density", '')
Note: no visible global function definition for 'bw.nrd0'
Note: no visible global function definition for 'bw.nrd'
Note: no visible global function definition for 'bw.ucv'
2013 Jun 07
1
v2.2.2 (e5bd0a7c6a1e) Core Dump
(gdb) bt full
#0 mailbox_list_default_get_vname (list=0x21ceec0, storage_name=0x0) at mailbox-list.c:655
__s2_len = <optimized out>
i = <optimized out>
prefix_len = <optimized out>
name_len = <optimized out>
vname = 0x0
list_sep = <optimized out>
ns_sep = <optimized out>
ret = <optimized
2013 Apr 24
3
[LLVMdev] [PROPOSAL] per-function optimization level control
...t this.
The idea is to allow the optimization level to be overridden
for specific functions.
The rest of this proposal is organized as follows:
- Section 1. describes this new feature and explains why and when
per-function optimization options are useful;
- Sections 2. and 3. describe how the optimizer could be adapted/changed
to allow the definition of per-function optimizations;
- Section 4. tries to outline a possible workflow for implementing this
new feature.
I am looking for any feedback or suggestions etc.
Thanks!
Andrea Di Biagio
SN Systems Ltd.
http://www.snsys.com
1. Descript...