The stack trace you provided looks like it is from v2.0.3.  The
initialization code changed drastically in 2.1.0 -- the method
DescriptorPool::InternalBuildGeneratedFile no longer exists, for example.
 Can you provide a stack trace using 2.1.0?

On Fri, Jun 26, 2009 at 8:07 AM, rodrigob <rodrigo.benen...@gmail.com>wrote:

>
> Hello there,
> I'm usually a linux developer, but I occasionally have to develop some
> Windows applications.
>
> I have a Gtk + Cairo + ProtocolBuffers that was ported to windows some
> months ago without any problem.
>
> Now I have a new one, with similar setup but a few more dependencies
> (CGAL, RSVG and others).
>
> After configuring the visual studio project and getting the code to
> compile and link correctly the executable crashes miserably on a
> ProtocolBuffers exception.
>
> The crash details can be inspected at
> http://files.getdropbox.com/u/185965/parking_planning/protobuf_crash.jpg
>
> the weird thing is that the application crashes before ever entering
> in the main, during some static elements initialization defined by
> Protocol Buffer.
>
> I used first protobuf 2.1.0 and then 2.0.3, both crash in the same
> way.
>
> Any idea of what is going on ? I know that Protobuf can work unders
> VisualStudio, but this time it is not working for me... what could
> cause this kind of crashes ?
>
> The problem seems similar to
>
> http://groups.google.com/group/protobuf/browse_thread/thread/f0f8108fdc0de614?pli=1#
>
> but the crash source is no the same.
>
> I'm using Windows Xp and Visual Studio 2005.
>
> Any help would be appreciated.
>
> Regards,
> rodrigob.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to