On 2012-05-21 04:54, David Xu wrote:
...
As I said, it depends on ordering the global objects are destructed, if
the object which deleting
the current_thread_data_key is destructed lastly, the problem wont
happen, but now
it is destructed too early. I believe there is no specification said
On Mon, May 21, 2012 at 10:54:54AM +0800, David Xu wrote:
On 2012/5/21 1:24, Konstantin Belousov wrote:
On Sun, May 20, 2012 at 06:42:35PM +0200, Alberto Villa wrote:
On Sun, May 20, 2012 at 8:03 AM, David Xulistlog2...@gmail.com wrote:
qdbus segfaults on my machine too, I tracked it down,
Now let me dig into qthread_unix.cpp, see how QThreadData::current()
works:
QThreadData *QThreadData::current()
{
QThreadData *data = get_thread_data();
if (!data) {
void *a;
if
(QInternal::activateCallbacks(QInternal::AdoptCurrentThread, a)) {
QThread
On 2012/4/30 22:13, Gustau Pérez i Querol wrote:
Hi,
the kde team is seeing some strange problems with the new version
(4.8.1) of devel/dbus-qt4 with current. It does work with stable. I
also suspect that the problem described below is affecting the
experimental cinnamon port (an
On Sun, May 20, 2012 at 8:03 AM, David Xu listlog2...@gmail.com wrote:
qdbus segfaults on my machine too, I tracked it down, and found the problem
is in QT,
it deleted current_thread_data_key, but it still uses it in some cxa hooks,
I applied the
following patch, and it works fine.
On Sun, May 20, 2012 at 06:42:35PM +0200, Alberto Villa wrote:
On Sun, May 20, 2012 at 8:03 AM, David Xu listlog2...@gmail.com wrote:
qdbus segfaults on my machine too, I tracked it down, and found the problem
is in QT,
it deleted current_thread_data_key, but it still uses it in some cxa
On 2012/5/21 1:24, Konstantin Belousov wrote:
On Sun, May 20, 2012 at 06:42:35PM +0200, Alberto Villa wrote:
On Sun, May 20, 2012 at 8:03 AM, David Xulistlog2...@gmail.com wrote:
qdbus segfaults on my machine too, I tracked it down, and found the problem
is in QT,
it deleted
On 2012/5/21 10:54, David Xu wrote:
On 2012/5/21 1:24, Konstantin Belousov wrote:
On Sun, May 20, 2012 at 06:42:35PM +0200, Alberto Villa wrote:
On Sun, May 20, 2012 at 8:03 AM, David Xulistlog2...@gmail.com
wrote:
qdbus segfaults on my machine too, I tracked it down, and found the
problem
On Tue, May 1, 2012 at 8:18 PM, Gustau Pérez i Querol
gpe...@entel.upc.edu wrote:
So the problem seems to be not related to jemalloc or malloc. As the
experimental 4.8.1 devel/dbus-qt4 port works fine in stable, the problem has
do to with some differences between head and stable. When we get
On Fri, May 18, 2012 at 07:01:25PM +0200, Alberto Villa wrote:
On Tue, May 1, 2012 at 8:18 PM, Gustau P?rez i Querol
gpe...@entel.upc.edu wrote:
So the problem seems to be not related to jemalloc or malloc. As the
experimental 4.8.1 devel/dbus-qt4 port works fine in stable, the problem has
on 18/05/2012 20:01 Alberto Villa said the following:
On Tue, May 1, 2012 at 8:18 PM, Gustau Pérez i Querol
gpe...@entel.upc.edu wrote:
So the problem seems to be not related to jemalloc or malloc. As the
experimental 4.8.1 devel/dbus-qt4 port works fine in stable, the problem has
do to with
On Fri, May 18, 2012 at 11:28 PM, Andriy Gapon a...@freebsd.org wrote:
you have add new people to the discussion, but unfortunately too little of the
original context is present here... That is, this email doesn't even include
a
description of an actual problem.
Could you please provide the
On Sat, May 19, 2012 at 12:16:59AM +0200, Alberto Villa wrote:
On Fri, May 18, 2012 at 11:28 PM, Andriy Gapon a...@freebsd.org wrote:
you have add new people to the discussion, but unfortunately too little of
the
original context is present here... That is, this email doesn't even
On Sat, May 19, 2012 at 12:37 AM, Konstantin Belousov
kostik...@gmail.com wrote:
Well, there is still not much to read. And, http://pastebin.com/ryBXtqGF.
shows 'Unknown Paste ID!'.
Eh, sorry, Gus will provide updated data.
That said, why do you think that the problem is in system and not in
On Sat, May 19, 2012 at 12:49:02AM +0200, Alberto Villa wrote:
On Sat, May 19, 2012 at 12:37 AM, Konstantin Belousov
kostik...@gmail.com wrote:
Well, there is still not much to read. And, http://pastebin.com/ryBXtqGF.
shows 'Unknown Paste ID!'.
Eh, sorry, Gus will provide updated data.
On Sat, May 19, 2012 at 12:52 AM, Konstantin Belousov
kostik...@gmail.com wrote:
How to reproduce the issue locally ? (I do not want to install all KDE
to my test box).
Just build devel/dbus-qt4 on 10-CURRENT and run qdbus. It should crash
(should you have D-Bus running, which you probably
Al 30/04/2012 21:34, En/na Jason Evans ha escrit:
On Apr 30, 2012, at 7:13 AM, Gustau Pérez i Querol wrote:
the kde team is seeing some strange problems with the new version (4.8.1) of
devel/dbus-qt4 with current. It does work with stable. I also suspect that the
problem described below is
Hi,
the kde team is seeing some strange problems with the new version
(4.8.1) of devel/dbus-qt4 with current. It does work with stable. I also
suspect that the problem described below is affecting the experimental
cinnamon port (an alternative to gnome3, possible replacement of gnome2).
Hi,
Please install valgrind and run the program inside valgrind. See what
kind of errors it generates.
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
On Apr 30, 2012, at 7:13 AM, Gustau Pérez i Querol wrote:
the kde team is seeing some strange problems with the new version (4.8.1) of
devel/dbus-qt4 with current. It does work with stable. I also suspect that
the problem described below is affecting the experimental cinnamon port (an
20 matches
Mail list logo
