Yes, I do agree.. as I said, December 1st, if nothing major appears, we
release 0.95... if we can't fix the bug by december 1st, we'll use the
orkaround and that's it...
Harry, maybe you didn't get the latest change because the anonymous CVS
wasn't up to date... JUST IN CASE, I would suggest you get the latest cvs
again and do a `make clean all`... if the bug still happens, i would
really appreciate it if you did like you did at first : give us the
backtrace of the segfault ...
without the backtrace from gdb, we can't find where the new bug happens...
Thanks,
KaKaRoTo
On Fri, 25 Nov 2005 15:06:19 -0500, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
Don't forget we just have to re-enable the check for the PWC driver
at the start of aMSN. That way, the config buttons will just be
disabled so nobody will get a seg fault, that's not a "serious bug"
for a release because we can prevent the bug from happening (yes it's
better to fix the bug but at least we can prevent it)
Le 05-11-25 à 14:09, Harry Vennik a écrit :
That is to say, we thought it would be fixed now, but it is not.
At this moment I don't think anyone understands why the change by
Phil didn't
fix it. I tried to find it out this morning, but no success. I will
try again
tomorrow, if I don't get it again, and neither does anyone else,
then I think
we should not have this prevent us from releasing 0.95, even though
I regard
it as quite a serious bug.
--
KaKaRoTo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
