List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:May 15 2009 1:28pm
Subject:Re: Segfault using thread_start
View as plain text  
Okay, here's the new plan:

       - Add DBDriver::library_begin() and library_end(), wrapping
         similarly named functions in the C API.

       - Create Process class, which you create at the top of main()
         on the stack, purely to call these automatically.

       - Update userman to recommend creating Process object in
         ConnectionPool derivatives, instead.

       - Create Thread class to call existing DBDriver::thread_start()
         and thread_end(), similar to Process, created on the stack
         of the thread entry function.

       - Move memory leak FAQ into userman, rewriting it to cover
         all this.
Thread
Segfault using thread_startMichael15 May
  • Re: Segfault using thread_startWarren Young15 May
    • Re: Segfault using thread_startMichael15 May
      • Re: Segfault using thread_startWarren Young15 May
        • Re: Segfault using thread_startMichael15 May
        • Re: Segfault using thread_startWarren Young15 May
          • Re: Segfault using thread_startMichael15 May
            • Re: Segfault using thread_startWarren Young15 May
              • Re: Segfault using thread_startMichael15 May