Hello, Maybe you could try removing the catch(...) and see if the debugger comes in at the point where the exception is thrown. That might show the reason of what is wrong.
Richard Peters Guy Smith wrote: > I also agree that Pat is making a reasonable point. The problem is > that this code is part of a fairly complicated program and the pieces > are scattered in many locations. Distilling this program down into a > meaningful test case would be difficult, and if I did so I would > solve the problem in the process anyway. I was hoping that somebody > would see something obvious in my example; if that's not going to > happen I'd rather not get you involved in it. At any rate, I think > you've answered my question; apparently there's nothing egregious > about my use of Crypto++. Thank you both for being so considerate > and so willing to help. > > --Guy > > ----- Original Message ----- > From: "Michael Barnett" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, July 10, 2003 4:58 PM > Subject: RE: CBC_Mode<AES> giving me grief > > >> The devil is in the details. I think Pat is making a reasonable > point...without a minimum-compilable segment of code it is impossible > to say what MIGHT be causing a problem. Looking at a snippet I might > ASSUME you are setting parameters that you have missed, simply > because "of course" you have to set the key val. what one programmer > assumes "everyone knows" may be the one peice of information another > programmer most needs. >> -Mike
