On Tue, Mar 16, 2010 at 7:44 PM, Austin Ziegler halosta...@gmail.comwrote:
Except in the case where the user has both VS2005 and VS2008 installed
on the same system.
Oh, right. Sorry.
Urgh. I'll think about it. This is the first I've heard of this problem,
though. Is it really that
On Wed, Mar 17, 2010 at 1:07 PM, Kenton Varda ken...@google.com wrote:
On Tue, Mar 16, 2010 at 7:44 PM, Austin Ziegler halosta...@gmail.com
wrote:
Except in the case where the user has both VS2005 and VS2008 installed
on the same system.
Oh, right. Sorry.
Urgh. I'll think about it. This
OK, can you file an issue report, then? I suppose it would not be too
terrible to make this part of the release post-processing step.
On Wed, Mar 17, 2010 at 11:19 AM, Austin Ziegler halosta...@gmail.comwrote:
On Wed, Mar 17, 2010 at 1:07 PM, Kenton Varda ken...@google.com wrote:
On Tue, Mar
appearantly I didn't notice that when I clicked the .sln file, it opened
with VS2005...
I only started looking into it when compilation failed with the 2005
version.
Linking with the 2005 version failed, the linker error I got was something
to do with std::Base_container contstructor/destructor. I
I do test each release with both VS2005 and VS2008, and haven't seen that
problem before. Odd.
On Mon, Mar 15, 2010 at 10:54 PM, Roey Lehman roey...@gmail.com wrote:
appearantly I didn't notice that when I clicked the .sln file, it opened
with VS2005...
I only started looking into it when
On Tue, Mar 16, 2010 at 3:24 PM, Kenton Varda ken...@google.com wrote:
I do test each release with both VS2005 and VS2008, and haven't seen that
problem before. Odd.
Do you have 2005 and 2008 on a single system, or are they on
independent systems? If they're on the same system, VS does not
On Tue, Mar 16, 2010 at 6:11 PM, Austin Ziegler halosta...@gmail.comwrote:
On Tue, Mar 16, 2010 at 3:24 PM, Kenton Varda ken...@google.com wrote:
I do test each release with both VS2005 and VS2008, and haven't seen that
problem before. Odd.
Do you have 2005 and 2008 on a single system, or
On Tue, Mar 16, 2010 at 10:21 PM, Kenton Varda ken...@google.com wrote:
On Tue, Mar 16, 2010 at 6:11 PM, Austin Ziegler halosta...@gmail.com
wrote:
On Tue, Mar 16, 2010 at 3:24 PM, Kenton Varda ken...@google.com wrote:
I do test each release with both VS2005 and VS2008, and haven't seen
I actually maintain the project files using VS2008, but I run a hack script
that downgrades them to VS2005 (by simply replacing the version number)
before release so that VS2005 users can use the package.
I'm confused about how you managed to compile the project using VS2008
without it
The problem was that Protocol Buffers comes with a default VS2005
project, and my application is in VS2008.
Had to convert protobuf VS2005 to VS2008 and everything runs just
fine.
It seems that one of the STL Libraries had been changed between VS8
and VS9 and so was throwing all kinds of weird
I cannot find the ReadBytes function inside wire_format_lite_inl.h.
How come?
On Thu, Mar 11, 2010 at 10:21 PM, Kenton Varda ken...@google.com wrote:
Please keep the mailing list CC'd so that others can help.
The input_ field is normally null when parsing from a flat array, so that's
not
I'm really glad you found the cause of this; you had me worried I'd done
something horrible with the .NET encoding ;-p
Probably one for Kenton, but I wonder if it might be prudent to include
VS2008 (and presumably VS2010) project files for the core project?
Marc
On 14 March 2010 07:25, Roey
On Sun, Mar 14, 2010 at 3:15 PM, Marc Gravell marc.grav...@gmail.com wrote:
I'm really glad you found the cause of this; you had me worried I'd done
something horrible with the .NET encoding ;-p
Probably one for Kenton, but I wonder if it might be prudent to include
VS2008 (and presumably
Just to clarify , the access violation occurs inside the
ParseFromArray function, right when it tries to parse the second field
of the struct (data),
this is the code that crashes inside the cc file :
// optional bytes Data = 2;
case 2: {
if
The crash occurs in my auto-generated cc file for the google proto
structs , on this line :
// optional bytes Data = 2;
case 2: {
if
(::google::protobuf::internal::WireFormatLite::GetTagWireType(tag) ==
OK, so, which pointer is null?
We can't do this for you. You are the only one who can run your code in the
debugger.
If you want us to debug it, you need to provide a small, self-contained
example program demonstrating the problem. Just C++ code and input data is
needed -- the C# part is not
Please keep the mailing list CC'd so that others can help.
The input_ field is normally null when parsing from a flat array, so that's
not the problem.
ReadBytes() is an inline function found in
google/protobuf/wire_format_lite_inl.h. Your debugger should be able to
descend into it. You may
17 matches
Mail list logo
