OK, just for the records: Now I can be really sure. I've deleted everything that remotely resembles a release build and changed my build system so it won't create any and work without. And still the bug occurs. So I don't think it is related to Microsoft runtime issues.
Cheers, Stephan On 16 Jul., 08:33, Mr Moose <stephan.men...@gmail.com> wrote: > Kenton, > > well, I checked this over and over again and I really think I did make > sure. I also checked the linker settings for all other libs I link > against and they are all set to Debug. Also, this is the same build > environment I used with 2.0.3. where it did work. On the other hand, > it's Microsoft so you can never be really sure what's going on. > Anyway, is there any other possible explanation for said crashes? > > Cheers, > > Stephan > > On 15 Jul., 20:25, Kenton Varda <ken...@google.com> wrote: > > > Did you make sure to compile your debug build against a debug build of > > libprotobuf? MSVC fails miserably when trying to mix and match debug vs. > > release, apparently because the STL classes have different representations > > between the two. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
