|
From: Ka-Hing C. <kh...@ja...> - 2003-04-02 18:02:35
|
On Wed, 2003-04-02 at 09:40, Richard Hoskins wrote: > Ethan Blanton <ebl...@cs...> writes: > Perhaps the discussion of the new buddy list was warranted, then. It > did some good. Just because some acted like they wanted the world, > doesn't mean that there wasn't room for discussion. You don't want > feedback from the users? Are you going to treat all questions as > complaints, and all concerns as whining? > We want feedback from users, but not in the form of "This is bad and I don't like it." Not saying this happened on this list, but it sure happens a lot on #gaim. > Gaim dumped core on me, or at least that is what STDERR said, along > with a request for a backtrace. I couldn't find the core file to get > said backtrace, so I posted to this list. I was told "There's a reason > this is CVS. The bugs will be fixed when we find fixes." In this case your system probably set a size limit on core file to 0. Try 'ulimit -c unlimited' then run gaim from the same terminal. After you get a core see http://gaim.sf.net/gdb.php for how to get a bt. Other than the bt, it is often useful to tell us what you were doing at the time of segfault. Other information such as distro, gtk versions are less helpful, but they don't hurt. For example, recently we have a segfault-on-start problem with Gentoo users only. May I also add that it's not very useful to report bugs that you cannot reproduce? Also, a quick search on the sf tracker, this emailing list, and the sf forum would help prevent multiple bug reports. If we get the same bug report over and over again, it's easy to get annoyed by it. -- Ka-Hing "A complex system that works is invariably found to have evolved from a simple system that worked." -- John Gall, _Systemantics_ |