From: Matt K. <ra...@ch...> - 2004-03-29 22:21:27
|
> > Can we work around it by setting the global variables to something? A > well commented line could be left in jazz.cpp for when the problem > goes away. > > Patrick > I thought about that, but I'd worry about what version of wxGTK any given user is using. There is no guarantee that their version will have the same set of global wxString variables. If the user were compiling JAZZ, that's one thing (although if it didn't work, they would have a hard time figuring out the mismatch), but if the user installs JAZZ from RPM's, there's no way to fix a mismatch. A possibly safer approach would be to instantiate an instance of each wxGTK class that uses global wxStrings. This might be a little safer, but still no guarantees against mismatches. Not sure how to crack this nut. We may either have to do something like this, or just tell the users that it's gonna segfault on exit and explain that it's not our fault. Matt |