Ilya Konstantinov wrote:
>Do you guys have any objections?
>
>
Are there any other active developers on the mailing list than you?
People who understand all the consequences that these changes have for
users, plugin developers and future contributors? If you're the only one
who understands a
Hi list!
Now it's proven.
Here is a part of the kdelibs3.spec of the suse src rpm's:
./configure \
$configkde \
%ifarch i386
--enable-fast-malloc=yes \
^
%endif
--with-distribution=SuSE \
--with-install-root=$RPM_BUILD_ROOT \
--with-sgml-cat=/var/lib/sgml/
make
Regards,
Daniel
Okay, dear list, I think, I got it.
It seems, that SuSE biuld it's kde3 packages with --enable-fast-malloc
This can produce some weird crashes on some programs (like licq).
Because SuSE didn't use --enable-fast-malloc=full it is possible to turn fast
malloc on or off with the environment varia
Okay, my success wit --enable-debug was a one-timer. Can't reproduce it.
But hey, Will, your hint is wonderful! It works! Thank you very much! How do
you get to this trick?
Greets,
Daniel
Am Freitag, 31. Mai 2002 17:49 schrieb Will Stephenson:
> On Friday 31 May 2002 14:10, Daniel Eckl wrote:
Hi List! Hi Rob!
I tried to look at some debugging messages on my own and compiled the kde-gui
plugin again with --enable-debug
And what do you say? Now it works...
If you want to look over licq's shoulder, it is frightened and takes care not
to crash
What AI do you use?
little bit
Hi,
I'm proposing to make licq's backend guarantee returning UTF-8-encoded
string values to the plugins in the 1.1.0 series. For that, I'll make
licq link with libiconv and make the decoding and encoding right in the
backend (e.g. SMSs are always transfered in UTF-8 over the net, contact
messages
It seems to be a problem with licq_kde-gui.so and the kde libs >3.0.0
With KDE 3.0.0 it worked seemlessly. With KDE 3.0.1 it crashes immediately
after start. with KDE 3.0.1 but without "--with-kde" configure option (-p
qt-gui), it works very smooth, too.
So there is an incompatibility with eit
On Tue, 28 May 2002, Jonas Jensen wrote:
> licq had been stable for a week (which is rare for me), but it crashed
> yesterday when I closed a message window:
Happens to me quite often.. this is the latest backtrace:
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handle_sigsegv+0x83)
