Hi,
is it safe to use a STL container of messages ?
I'm doing it and I seeing rare segmentation faults when executed on our
target platform which is a NXP IMX6ull.
The message queue:
std::queue reqs_;
a coredump backtrace:
(gdb) bt full
#0 __libc_do_syscall () at libc-do-syscall.S:49
No l
It's fine to put protobuf messages in STL containers, so if you're seeing
segfaults then those must be caused by some other issue.
On Mon, Jul 12, 2021 at 5:02 AM jobroe wrote:
>
> Hi,
>
> is it safe to use a STL container of messages ?
>
> I'm doing it and I seeing rare segmentation faults when
Hi,
I want to use ProtobufStreamObjectSource in a project.
I am a little confused about the type.pb.h and type_info.h files.
Is this an example class (ProtobufStreamObjectSource) that uses type.pb.h
and type_info.h as example case and I should implement my own extension of
the ObjectSource cl
I actually found this in the comments:
"This implementation uses a google.protobuf.Type for tag and name lookup."
Which implies I can write my own extension similar to this for my own
message type it seems.
On Monday, July 12, 2021 at 3:14:21 PM UTC-7 Sanjana Gupta wrote:
> Hi,
>
> I want to
But actually, the unit tests make me think otherwise. They use a variety of
different messages in the tests.
On Monday, July 12, 2021 at 3:24:17 PM UTC-7 Sanjana Gupta wrote:
> I actually found this in the comments:
> "This implementation uses a google.protobuf.Type for tag and name lookup."
>
>
