Re: Qpid Proton messenger on 32 bit linux
I routinely run tests using Messenger in a 32-bit Linux environment and I've never had a problem with it. Are you building on a 64-bit machine or in a complete 32-bit environment? -Ted On 01/27/2014 03:43 PM, serega wrote: Does the messenger work on 32 bit linux? I build the 32 bit messenger by setting the variable export CFLAGS=-m32 The same code that works on 64 bit linux crates on 32. It always crashes in pn_encoder_writef8 Here is the crash stack trace from a core dump Core was generated by `./testconsumer 10.250.0.126 10.250.0.127 1000'. Program terminated with signal 11, Segmentation fault. #0 0x00d89877 in pn_encoder_writef8 () from /usr/local/lib/libqpid-proton.so.2 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6_3.7.i686 libuuid-2.17.2-12.7.el6_3.i686 (gdb) bt #0 0x00d89877 in pn_encoder_writef8 () from /usr/local/lib/libqpid-proton.so.2 #1 0x00d89d4c in pni_encoder_enter () from /usr/local/lib/libqpid-proton.so.2 #2 0x00d85d66 in pni_data_traverse () from /usr/local/lib/libqpid-proton.so.2 #3 0x00d8a6e5 in pn_encoder_encode () from /usr/local/lib/libqpid-proton.so.2 #4 0x00d863ec in pn_data_encode () from /usr/local/lib/libqpid-proton.so.2 #5 0x00d8af95 in pn_post_frame () from /usr/local/lib/libqpid-proton.so.2 #6 0x00d930f7 in pn_flush_disp () from /usr/local/lib/libqpid-proton.so.2 #7 0x00d93971 in pn_process_flush_disp () from /usr/local/lib/libqpid-proton.so.2 #8 0x00d93f94 in pn_phase () from /usr/local/lib/libqpid-proton.so.2 #9 0x00d940c0 in pn_process () from /usr/local/lib/libqpid-proton.so.2 #10 0x00d942e2 in pn_output_write_amqp () from /usr/local/lib/libqpid-proton.so.2 #11 0x00d94a28 in pn_io_layer_output_passthru () from /usr/local/lib/libqpid-proton.so.2 #12 0x00d94a28 in pn_io_layer_output_passthru () from /usr/local/lib/libqpid-proton.so.2 #13 0x00d944cd in transport_produce () from /usr/local/lib/libqpid-proton.so.2 #14 0x00d94de7 in pn_transport_pending () from /usr/local/lib/libqpid-proton.so.2 #15 0x00da0726 in pn_connector_process () from /usr/local/lib/libqpid-proton.so.2 #16 0x00d9b1bf in pn_messenger_tsync () from /usr/local/lib/libqpid-proton.so.2 #17 0x00d9b503 in pn_messenger_sync () from /usr/local/lib/libqpid-proton.so.2 #18 0x00d9d279 in pn_messenger_recv () from /usr/local/lib/libqpid-proton.so.2 #19 0x0065f10c in run_consumer (args=0x8dc7198) at messageconsumer.c:104 #20 0x0050fa49 in start_thread () from /lib/libpthread.so.0 #21 0x0035863e in clone () from /lib/libc.so.6 (gdb) -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Re: Qpid Proton messenger on 32 bit linux
I am building on 64 bit RedHat 6.3 that has required 32 bit libraries. It happens when initiated from both pn_messenger_recv() and pn_messenger_send(). -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445p7603475.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Re: Qpid Proton messenger on 32 bit linux
Do I need to pass any special arguments to cmake or change CMakeLists.txt that may affect Messanger? -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445p7603477.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
[jira] [Commented] (PROTON-498) Set VALGRIND environment variable to be compatible with the QPID build
[ https://issues.apache.org/jira/browse/PROTON-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884542#comment-13884542 ] ASF subversion and git services commented on PROTON-498: Commit 1562213 from [~kgiusti] in branch 'proton/trunk' [ https://svn.apache.org/r1562213 ] PROTON-498: set the VALGRIND env var to the path to the valgrind executable Set VALGRIND environment variable to be compatible with the QPID build -- Key: PROTON-498 URL: https://issues.apache.org/jira/browse/PROTON-498 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.6 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Trivial Fix For: 0.7 The proton build system detects if valgrind is installed, and exports the VALGRIND environment variable for use by the tests. However the proton build system sets this environment variable to 1. The QPID build system also sets the VALGRIND environment variable, but it sets it to the path to the valgrind executable (eg. /usr/bin/valgrind, or equivalent). The QPID test bed assumes $VALGRIND is the path to the executable. Modify the proton build system to use the same convention as the QPID build system. This prevents problems when switching from one build system to the other. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (PROTON-498) Set VALGRIND environment variable to be compatible with the QPID build
[ https://issues.apache.org/jira/browse/PROTON-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884583#comment-13884583 ] ASF subversion and git services commented on PROTON-498: Commit 1562224 from [~kgiusti] in branch 'proton/trunk' [ https://svn.apache.org/r1562224 ] PROTON-498: fix the CMake valgrind logic Set VALGRIND environment variable to be compatible with the QPID build -- Key: PROTON-498 URL: https://issues.apache.org/jira/browse/PROTON-498 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.6 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Trivial Fix For: 0.7 The proton build system detects if valgrind is installed, and exports the VALGRIND environment variable for use by the tests. However the proton build system sets this environment variable to 1. The QPID build system also sets the VALGRIND environment variable, but it sets it to the path to the valgrind executable (eg. /usr/bin/valgrind, or equivalent). The QPID test bed assumes $VALGRIND is the path to the executable. Modify the proton build system to use the same convention as the QPID build system. This prevents problems when switching from one build system to the other. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
