[
https://issues.apache.org/jira/browse/THRIFT-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921492#action_12921492
]
Roger Meier commented on THRIFT-582:
------------------------------------
Yes, I'm ready to do this Bryan.
Anatol, I agree with you on these points:
* The best thing as for me is to add "if WITH_CPP" to Makefile for this
particular test.
* rename gen-c folder to gen-c_glib for consistency
just did a test with your version from git repo, still have the same issue on
my Debian Lenny...see
{code}
[New Thread 0xb74406b0 (LWP 20985)]
[Switching to Thread 0xb74406b0 (LWP 20985)]
Breakpoint 1, test_tricky2 () at testoptionalrequired.c:106
106 TTestTricky1 *t1 = NULL;
(gdb) b testoptionalrequired.c:113
Breakpoint 2 at 0x804e700: file testoptionalrequired.c, line 113.
(gdb) c
Continuing.
Breakpoint 2, test_tricky2 () at testoptionalrequired.c:113
113 write_to_read (THRIFT_STRUCT (t3), THRIFT_STRUCT (t1), NULL, NULL);
(gdb) b src/protocol/thrift_binary_protocol.c:148
Breakpoint 3 at 0xb75ee01d: file src/protocol/thrift_binary_protocol.c, line
148.
(gdb) c
Continuing.
Breakpoint 3, thrift_binary_protocol_get_type () at
src/protocol/thrift_binary_protocol.c:148
148 if (type == 0)
(gdb)
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0xb76bc3dc in ?? () from /usr/lib/libgobject-2.0.so.0
(gdb)
{code}
seems, that I have to become familiar with GType and GObject;-)
> C implementation of Thrift
> --------------------------
>
> Key: THRIFT-582
> URL: https://issues.apache.org/jira/browse/THRIFT-582
> Project: Thrift
> Issue Type: New Feature
> Reporter: David Reiss
> Assignee: Roger Meier
> Priority: Minor
> Attachments: c_glib_bindings.patch, t_c_generator.cc,
> thrift_582_c_glib_bindings.patch, thrift_582_c_glib_bindings_20100927.patch,
> thrift_582_c_glib_bindings_20101012.patch
>
>
> Create a usable implementation of Thrift that uses only C at runtime, no C++.
> The code is at
> http://svn.apache.org/repos/asf/incubator/thrift/branches/c-bindings/.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
