Here what i got : (gdb) thread apply all bt Thread 1 (process 522, thread 1): #0 0x28985f7c in __sys_poll () from /usr/lib/libc_r.so.4 #1 0x28985461 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 #2 0x28984e16 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 #3 0x0 in ?? ()
i mentionned earlier that i am not used to gdb :( To give you more details, when it hangs, it's just before transforming the "outbox" to "bold" and adding "(1)" next to it. When i click send and the outbox stays unbold, i know the email won't be sent, and when i click on "cancel" it gives me my email, then when i click close and discard, it hangs completely. Thanks On Wed, 2005-06-15 at 16:37 +0800, Not Zed wrote: > Uh, since you're using bsd i figured you'd know how to use gdb. > > hit ctrl-c when it hangs, then try 'thread apply all bt', it'll show > where the various threads are at that instant, and should pinpoint the > hang. > > On Wed, 2005-06-15 at 07:26 +0200, FireWire BSD wrote: > > It didn't hang a lot like usual under gdb, i am getting lots of these > > three lines : > > update flow align > > (no debugging symbols found)...(no debugging symbols found)... > > (evolution:4569): camel-WARNING **: camel_exception_get_id called with > > NULL parameter. > > > > But when it hangs, i have nothing in the gdb, it just freezes with no > > more console lines at all. > > > > > > On Sun, 2005-06-12 at 22:58 +0800, Not Zed wrote: > > > Ideally - yes, but you *may* be able to get something useful-enough > > > without it. Unfortunately it probably takes a bit of experience to tell > > > if you have something useful or not. But given all the time-zone delays > > > you probably have time to try the re-build-with-symbols route anyway, if > > > it is really stopping you getting anywhere. > > > > > > > > > On Sun, 2005-06-12 at 16:47 +0200, FireWire BSD wrote: > > > > Ok, i will try, i am not used to gdb, do i have to recompile my > > > > evolution with debug symbols or something? > > > > > > > > On Fri, 2005-06-10 at 14:39 +0800, Not Zed wrote: > > > > > Well to continue with the suggestion - run it in gdb, get a backtrace, > > > > > file a bug report. Haven't seen this issue, so without some details > > > > > other than 'it doesn't work for me', we can't do a lot! > > > > > > > > > > _______________________________________________ > > evolution maillist - [email protected] > > http://lists.ximian.com/mailman/listinfo/evolution > _______________________________________________ evolution maillist - [email protected] http://lists.ximian.com/mailman/listinfo/evolution
