> 21.04.2016 13:35, Thomas Steinmaurer wrote:
> ...
>>> As you already found that fbtracemgr is OK, i guess something is not
>>> fully
>>> correct (or stepped on some another issue) at FB Trace Manager. Could you
>>> show
>>> how do you work with trace service ?
>>
>> The usage of the trace s
Build the Linux code with --enable-binreloc and create an option in the
installer to install in different locations than /opt/firebird
--
Key: CORE-
> 21.04.2016 13:35, Thomas Steinmaurer wrote:
> ...
>>> As you already found that fbtracemgr is OK, i guess something is not
>>> fully
>>> correct (or stepped on some another issue) at FB Trace Manager. Could you
>>> show
>>> how do you work with trace service ?
>>
>> The usage of the trace s
21.04.2016 13:35, Thomas Steinmaurer wrote:
...
>>As you already found that fbtracemgr is OK, i guess something is not fully
>> correct (or stepped on some another issue) at FB Trace Manager. Could you
>> show
>> how do you work with trace service ?
>
> The usage of the trace services in FBTM
Single CPU core fully utilized with Trace session
-
Key: CORE-5203
URL: http://tracker.firebirdsql.org/browse/CORE-5203
Project: Firebird Core
Issue Type: Bug
Components: Engine
A
Building libreoffice master git with Clang trunk on Mac OS X
https://www.mail-archive.com/search?l=libreoff...@lists.freedesktop.org&q=subject:%22Building+with+Clang+trunk+on+Mac+OS+X%22&o=newest
it might be related to this issue
http://paulbeachsblog.blogspot.ro/2016/03/dyldlibrarypath-and-el-
> On 04/21/2016 12:47 PM, Thomas Steinmaurer wrote:
>> Hi Alex,
>>
> Hello Vlad,
>
>>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>>> ...
What else could I provide so that you can investigate the offending
thread?
>>> Full memory dump, please.
> Have y
On 04/21/2016 12:47 PM, Thomas Steinmaurer wrote:
> Hi Alex,
>
Hello Vlad,
>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>> ...
>>> What else could I provide so that you can investigate the offending
>>> thread?
>> Full memory dump, please.
Have you had time
Hello Vlad,
>>> Have you had time to look at it?
>
> Looking now, but seems you already on the way ;)
>
>>> Unfortunately this now also has happened in a production environment at
>>> a customer site.
>>>
>>> We did quite some testing in the trace area at Firebird 3 Alpha stage
>>> and I can't
Hi Alex,
>>> Hello Vlad,
>>>
> 20.04.2016 0:47, Thomas Steinmaurer wrote:
> ...
>> What else could I provide so that you can investigate the offending
>> thread?
> Full memory dump, please.
>>> Have you had time to look at it?
>>>
>>> Unfortunately this now also has happene
21.04.2016 12:00, Thomas Steinmaurer wrote:
>> Have you had time to look at it?
Looking now, but seems you already on the way ;)
>> Unfortunately this now also has happened in a production environment at
>> a customer site.
>>
>> We did quite some testing in the trace area at Firebird 3 Alpha
On 04/21/2016 12:00 PM, Thomas Steinmaurer wrote:
> Hi again,
>
>> Hello Vlad,
>>
20.04.2016 0:47, Thomas Steinmaurer wrote:
...
> What else could I provide so that you can investigate the offending
> thread?
Full memory dump, please.
>> Have you had time to look at it?
>
Hi again,
> Hello Vlad,
>
>>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>>> ...
What else could I provide so that you can investigate the offending
thread?
>>>
>>>Full memory dump, please.
>
> Have you had time to look at it?
>
> Unfortunately this now also has happened in a prod
Hello Vlad,
>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>> ...
>>> What else could I provide so that you can investigate the offending
>>> thread?
>>
>>Full memory dump, please.
Have you had time to look at it?
Unfortunately this now also has happened in a production environment at
a cust
14 matches
Mail list logo
