Re: intermittent issue with encode (version 2.0.3)

2009-07-10 Thread Kenton Varda
2009 6:05 PM > > *To:* Rizzuto, Raymond > *Cc:* protobuf@googlegroups.com > *Subject:* Re: intermittent issue with encode (version 2.0.3) > > > > As the comment says, the first call will always occur at startup time when > there is only one thread anyway, so it's pe

RE: intermittent issue with encode (version 2.0.3)

2009-07-10 Thread Rizzuto, Raymond
o:ken...@google.com] Sent: Thursday, July 09, 2009 6:05 PM To: Rizzuto, Raymond Cc: protobuf@googlegroups.com Subject: Re: intermittent issue with encode (version 2.0.3) As the comment says, the first call will always occur at startup time when there is only one thread anyway, so it's perfectly

Re: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Kenton Varda
hat make that safe. I > don’t know if that is something that can be relied on in all compilers, > however. > > > > Ray > > > -- > > *From:* Kenton Varda [mailto:ken...@google.com] > *Sent:* Thursday, July 09, 2009 5:08 PM > > *To:* Rizzuto, Raymond > *Cc:* protobuf@g

RE: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Rizzuto, Raymond
__ From: Kenton Varda [mailto:ken...@google.com] Sent: Thursday, July 09, 2009 5:08 PM To: Rizzuto, Raymond Cc: protobuf@googlegroups.com Subject: Re: intermittent issue with encode (version 2.0.3) I suppose you could also temporarily edit the header file. On Thu, Jul 9, 2009 at

RE: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Rizzuto, Raymond
ilto:ken...@google.com<mailto:ken...@google.com>] Sent: Thursday, July 09, 2009 5:08 PM To: Rizzuto, Raymond Cc: protobuf@googlegroups.com<mailto:protobuf@googlegroups.com> Subject: Re: intermittent issue with encode (version 2.0.3) I suppose you could also temporarily edit the heade

Re: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Kenton Varda
} >> >> throw SPException(error.c_str()); >> >> } >> >> >> >> It might not be something I’d do in production, but it sure would help >> during development. >> >> >> -- >>

Re: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Kenton Varda
ng I’d do in production, but it sure would help > during development. > > > -- > > *From:* Kenton Varda [mailto:ken...@google.com] > *Sent:* Thursday, July 09, 2009 5:08 PM > > *To:* Rizzuto, Raymond > *Cc:* protobuf@googlegroups.com >

RE: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Rizzuto, Raymond
with the version of tools I have, don't work very well. From: Kenton Varda [mailto:ken...@google.com<mailto:ken...@google.com>] Sent: Thursday, July 09, 2009 5:02 PM To: Rizzuto, Raymond Cc: protobuf@googlegroups.com<mailto:protobuf@googlegroups

Re: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Kenton Varda
- > > *From:* Kenton Varda [mailto:ken...@google.com] > *Sent:* Thursday, July 09, 2009 5:02 PM > *To:* Rizzuto, Raymond > *Cc:* protobuf@googlegroups.com > *Subject:* Re: intermittent issue with encode (version 2.0.3) > > > > Run in a debugger and set a breakpoin

RE: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Rizzuto, Raymond
groups.com Subject: Re: intermittent issue with encode (version 2.0.3) Run in a debugger and set a breakpoint at wire_format_inl.h:289. On Thu, Jul 9, 2009 at 1:56 PM, Rizzuto, Raymond mailto:raymond.rizz...@sig.com>> wrote: I think I have an error in my code (C++) that only occurs when

Re: intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Kenton Varda
Run in a debugger and set a breakpoint at wire_format_inl.h:289. On Thu, Jul 9, 2009 at 1:56 PM, Rizzuto, Raymond wrote: > I think I have an error in my code (C++) that only occurs when I have > multiple threads, and a lot of message volume. Even then, I can run the > same test many times, but

intermittent issue with encode (version 2.0.3)

2009-07-09 Thread Rizzuto, Raymond
I think I have an error in my code (C++) that only occurs when I have multiple threads, and a lot of message volume. Even then, I can run the same test many times, but only get a failure on some runs. With 7 threads running on a 4 core machine, and generating 480384 google protocol buffer mes