Re: [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis

From: Soeren Sonnenburg <evolution nn7 de>
To: evolution ximian com
Subject: Re: [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
Date: 06 Jan 2003 09:03:40 +0100

On Mon, 2003-01-06 at 01:23, Not Zed wrote:
[...]

Well, e_thread_destroy() empties the server_port message queue without
acquiring EThread.lock. Conceivably there could be a race there. I
sincerily hope it's not "just" random memory corruption. ;-)


Memory bugs are sometimes hard to find ... :-/


not if one uses valgrind ?!

Follow-Ups:
- Re: [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
  - From: Mika Liljeberg

References:
- [Evolution] SIGSEGV on setting label - gdb output and analysis
  - From: Mika Liljeberg
- [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
  - From: Jeffrey Stedfast
- [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
  - From: Mika Liljeberg
- [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
  - From: Jeffrey Stedfast
- [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
  - From: Mika Liljeberg
- Re: [Evolution] Re: [Evolution-hackers] SIGSEGV on setting label - gdb output and analysis
  - From: Not Zed

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]