List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:February 16 2005 1:55am
Subject:Re: mysql++1.7.28 thread safety
View as plain text  
Alex Vishnev wrote:
> 
> After I placed the method in question into another
> nested try/catch, the problem resolved itself inside my simple application.

Thanks for the report, but _yuck_.  What a weak implementation.

I guess the solution is to rework the resetdb sample so that it doesn't 
require nested exceptions.  Selectively turning off exceptions in the 
inner block probably isn't the right way, though.

>  I still would be curious to see why this happens.

I think the inner block is throwing an exception, which would tell you 
why the problem is happening.
Thread
mysql++1.7.28 core dumps on solarisAlex Vishnev12 Feb
  • Re: mysql++1.7.28 core dumps on solarisChris Frey12 Feb
    • RE: mysql++1.7.28 core dumps on solarisAlex Vishnev12 Feb
      • Re: mysql++1.7.28 core dumps on solarisChris Frey13 Feb
        • RE: mysql++1.7.28 core dumps on solarisAlex Vishnev14 Feb
          • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
    • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
  • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
    • RE: mysql++1.7.28 core dumps on solarisAlex Vishnev14 Feb
      • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
        • mysql++1.7.28 thread safetyAlex Vishnev14 Feb
          • Re: mysql++1.7.28 thread safetyEarl Miles14 Feb
            • Re: mysql++1.7.28 thread safetyWarren Young14 Feb
              • Re: mysql++1.7.28 thread safetyEarl Miles14 Feb
              • RE: mysql++1.7.28 thread safetyAlex Vishnev15 Feb
                • Re: mysql++1.7.28 thread safetyWarren Young16 Feb