You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by samuel sun <su...@hotmail.com> on 2008/06/13 08:34:53 UTC
Re: [Axis2] Axis2/C support for AIX?
Hi guys,
I'm also working on this issue, my env is AXIS2/C 1.3, AIX 5.2 and xlc 6.0,
and I also encounter the shared library suffix issue, after resolve it
temporarily the error when running sample echo is "Illegal instruction (core
dumped)" at "addr_in_handler.c" line 105. The call stack print by dbx is the
following:
.() at 0x0
axis2_addr_in_handler_create(0x11000c7f0, 0x110036a10), line 105 in
"addr_in_handler.c"
unnamed block $b746, line 1318 in "dep_engine.c"
axis2_dep_engine_add_module_flow_handlers(0x11000cf90, 0x11000c7f0,
0x1100365b0, 0x110037ab0), line 1318 in "dep_engine.c"
axis2_dep_engine_add_new_module(0x11000cf90, 0x11000c7f0, 0x11002bfd0), line
1389 in "dep_engine.c"
unnamed block $b758, line 1515 in "dep_engine.c"
unnamed block $b757, line 1515 in "dep_engine.c"
axis2_dep_engine_do_deploy(0x11000cf90, 0x11000c7f0), line 1515 in
"dep_engine.c"
axis2_ws_info_list_update(0x11002be10, 0x11000c7f0), line 425 in
"ws_info_list.c"
axis2_repos_listener_update(0x11002b5b0, 0x11000c7f0), line 297 in
"repos_listener.c"
axis2_repos_listener_init(0x11002b5b0, 0x11000c7f0), line 324 in
"repos_listener.c"
axis2_repos_listener_create_with_folder_name_and_dep_engine(0x11000c7f0,
0x11000d8b0, 0x11000cf90), line 141 in "repos_listener.c"
axis2_dep_engine_load_client(0x11000cf90, 0x11000c7f0, 0xffffffffffff8a6),
line 938 in "dep_engine.c"
axis2_build_client_conf_ctx(0x11000c7f0, 0xffffffffffff8a6), line 226 in
"conf_init.c"
axis2_svc_client_init_transports_from_conf_ctx(0x11000c7f0, 0x11000cb10,
0x0, 0xffffffffffff8a6), line 1168 in "svc_client.c"
axis2_svc_client_create_with_conf_ctx_and_svc(0x11000c7f0,
0xffffffffffff8a6, 0x0, 0x0), line 283 in "svc_client.c"
axis2_svc_client_create(0x11000c7f0, 0xffffffffffff8a6), line 106 in
"svc_client.c"
main(argc = 1, argv = 0x0ffffffffffff410), line 86 in "echo.c"
I can't get any idea totally how to track this kind of issue, can anyone
help?
Hal Roseman wrote:
>
> Hi Brent,
>
> We are also working on this problem. Have you gotten any closer? We
> should collaborate.
>
> - Hal
>
>
--
View this message in context: http://www.nabble.com/-Axis2--Axis2-C-support-for-AIX--tp17136222p17816047.html
Sent from the Axis - C++ - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: [Axis2] Axis2/C support for AIX?
Posted by Samisa Abeysinghe <sa...@wso2.com>.
On a related question, do we have to do anything special to get function
pointers to work on AIX? Again, I am asking this because it seems to
crash where a function pointer assignment is taking place.
Samisa...
Samisa Abeysinghe wrote:
> Looking at the trace, my gut feel is that it fails doe to the call
> axis2_handler_set_invoke(handler, env, axis2_addr_in_handler_invoke);
> on line 102 of addr_in_handler.c
>
> What really happens here is a function pointer assignment. Could you
> please step into this call and see how it goes. Also, is there a tool
> on AIX to track memory corruptions, something similar to valgrind?
>
> Samisa...
>
> samuel sun wrote:
>> Hi guys,
>>
>> I'm also working on this issue, my env is AXIS2/C 1.3, AIX 5.2 and
>> xlc 6.0,
>> and I also encounter the shared library suffix issue, after resolve it
>> temporarily the error when running sample echo is "Illegal
>> instruction (core
>> dumped)" at "addr_in_handler.c" line 105. The call stack print by dbx
>> is the
>> following:
>>
>> .() at 0x0
>> axis2_addr_in_handler_create(0x11000c7f0, 0x110036a10), line 105 in
>> "addr_in_handler.c"
>> unnamed block $b746, line 1318 in "dep_engine.c"
>> axis2_dep_engine_add_module_flow_handlers(0x11000cf90, 0x11000c7f0,
>> 0x1100365b0, 0x110037ab0), line 1318 in "dep_engine.c"
>> axis2_dep_engine_add_new_module(0x11000cf90, 0x11000c7f0,
>> 0x11002bfd0), line
>> 1389 in "dep_engine.c"
>> unnamed block $b758, line 1515 in "dep_engine.c"
>> unnamed block $b757, line 1515 in "dep_engine.c"
>> axis2_dep_engine_do_deploy(0x11000cf90, 0x11000c7f0), line 1515 in
>> "dep_engine.c"
>> axis2_ws_info_list_update(0x11002be10, 0x11000c7f0), line 425 in
>> "ws_info_list.c"
>> axis2_repos_listener_update(0x11002b5b0, 0x11000c7f0), line 297 in
>> "repos_listener.c"
>> axis2_repos_listener_init(0x11002b5b0, 0x11000c7f0), line 324 in
>> "repos_listener.c"
>> axis2_repos_listener_create_with_folder_name_and_dep_engine(0x11000c7f0,
>> 0x11000d8b0, 0x11000cf90), line 141 in "repos_listener.c"
>> axis2_dep_engine_load_client(0x11000cf90, 0x11000c7f0,
>> 0xffffffffffff8a6),
>> line 938 in "dep_engine.c"
>> axis2_build_client_conf_ctx(0x11000c7f0, 0xffffffffffff8a6), line 226 in
>> "conf_init.c"
>> axis2_svc_client_init_transports_from_conf_ctx(0x11000c7f0, 0x11000cb10,
>> 0x0, 0xffffffffffff8a6), line 1168 in "svc_client.c"
>> axis2_svc_client_create_with_conf_ctx_and_svc(0x11000c7f0,
>> 0xffffffffffff8a6, 0x0, 0x0), line 283 in "svc_client.c"
>> axis2_svc_client_create(0x11000c7f0, 0xffffffffffff8a6), line 106 in
>> "svc_client.c"
>> main(argc = 1, argv = 0x0ffffffffffff410), line 86 in "echo.c"
>>
>> I can't get any idea totally how to track this kind of issue, can anyone
>> help?
>>
>>
>> Hal Roseman wrote:
>>
>>> Hi Brent,
>>>
>>> We are also working on this problem. Have you gotten any closer? We
>>> should collaborate.
>>>
>>> - Hal
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG. Version: 8.0.100 / Virus Database: 270.3.0/1499 -
>> Release Date: 6/12/2008 7:13 AM
>>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.100 / Virus Database: 270.3.0/1503 - Release Date: 6/14/2008 6:02 PM
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: [Axis2] Axis2/C support for AIX?
Posted by Samisa Abeysinghe <sa...@wso2.com>.
samuel sun wrote:
> Thanks for your reply, Samisa. But my program seems not going that far, it
> crashes at addr_in_handler.c, line 105:
> handler = axis2_handler_create(env);
> In my source code(1.3.0), axis2_handler_set_invoke is line 113. Using step
> in dbx at this line also crashes with Illegal instruction, I guess the
> program crashes before this function is called correctly.
>
> Since axis2_handler_create resides in libaxis2_engine.so, which is linked at
> link time, while addr_in_handler.o resides in libaxis2_mod_addr.so which is
> dynamiclly loaded, I guess this may be some relocation problem. I tried to
> copy axis2_handler_create definition from handler.c to addr_in_handler.c and
> rename it(avoid symbol conflict), it works. But then it crashes at line 113,
> because axis2_handler_set_invoke's definition is also in libaxis2_engine.so.
> I don't know what's wrong here, I link the echo with -brtl in order to link
> .so library, could that be a problem?
>
Not sure, can you try without that?
Thanks,
Samisa...
>
> Samisa Abeysinghe-4 wrote:
>
>> Looking at the trace, my gut feel is that it fails doe to the call
>> axis2_handler_set_invoke(handler, env, axis2_addr_in_handler_invoke); on
>> line 102 of addr_in_handler.c
>>
>> What really happens here is a function pointer assignment. Could you
>> please step into this call and see how it goes. Also, is there a tool on
>> AIX to track memory corruptions, something similar to valgrind?
>>
>> Samisa...
>>
>> samuel sun wrote:
>>
>>> Hi guys,
>>>
>>> I'm also working on this issue, my env is AXIS2/C 1.3, AIX 5.2 and xlc
>>> 6.0,
>>> and I also encounter the shared library suffix issue, after resolve it
>>> temporarily the error when running sample echo is "Illegal instruction
>>> (core
>>> dumped)" at "addr_in_handler.c" line 105. The call stack print by dbx is
>>> the
>>> following:
>>>
>>> .() at 0x0
>>> axis2_addr_in_handler_create(0x11000c7f0, 0x110036a10), line 105 in
>>> "addr_in_handler.c"
>>> unnamed block $b746, line 1318 in "dep_engine.c"
>>> axis2_dep_engine_add_module_flow_handlers(0x11000cf90, 0x11000c7f0,
>>> 0x1100365b0, 0x110037ab0), line 1318 in "dep_engine.c"
>>> axis2_dep_engine_add_new_module(0x11000cf90, 0x11000c7f0, 0x11002bfd0),
>>> line
>>> 1389 in "dep_engine.c"
>>> unnamed block $b758, line 1515 in "dep_engine.c"
>>> unnamed block $b757, line 1515 in "dep_engine.c"
>>> axis2_dep_engine_do_deploy(0x11000cf90, 0x11000c7f0), line 1515 in
>>> "dep_engine.c"
>>> axis2_ws_info_list_update(0x11002be10, 0x11000c7f0), line 425 in
>>> "ws_info_list.c"
>>> axis2_repos_listener_update(0x11002b5b0, 0x11000c7f0), line 297 in
>>> "repos_listener.c"
>>> axis2_repos_listener_init(0x11002b5b0, 0x11000c7f0), line 324 in
>>> "repos_listener.c"
>>> axis2_repos_listener_create_with_folder_name_and_dep_engine(0x11000c7f0,
>>> 0x11000d8b0, 0x11000cf90), line 141 in "repos_listener.c"
>>> axis2_dep_engine_load_client(0x11000cf90, 0x11000c7f0,
>>> 0xffffffffffff8a6),
>>> line 938 in "dep_engine.c"
>>> axis2_build_client_conf_ctx(0x11000c7f0, 0xffffffffffff8a6), line 226 in
>>> "conf_init.c"
>>> axis2_svc_client_init_transports_from_conf_ctx(0x11000c7f0, 0x11000cb10,
>>> 0x0, 0xffffffffffff8a6), line 1168 in "svc_client.c"
>>> axis2_svc_client_create_with_conf_ctx_and_svc(0x11000c7f0,
>>> 0xffffffffffff8a6, 0x0, 0x0), line 283 in "svc_client.c"
>>> axis2_svc_client_create(0x11000c7f0, 0xffffffffffff8a6), line 106 in
>>> "svc_client.c"
>>> main(argc = 1, argv = 0x0ffffffffffff410), line 86 in "echo.c"
>>>
>>> I can't get any idea totally how to track this kind of issue, can anyone
>>> help?
>>>
>>>
>>> Hal Roseman wrote:
>>>
>>>
>>>> Hi Brent,
>>>>
>>>> We are also working on this problem. Have you gotten any closer? We
>>>> should collaborate.
>>>>
>>>> - Hal
>>>>
>>>>
>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG.
>>> Version: 8.0.100 / Virus Database: 270.3.0/1499 - Release Date: 6/12/2008
>>> 7:13 AM
>>>
>>>
>> --
>> Samisa Abeysinghe
>> Director, Engineering; WSO2 Inc.
>>
>> http://www.wso2.com/ - "The Open Source SOA Company"
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>>
>>
>>
>>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.100 / Virus Database: 270.3.0/1505 - Release Date: 6/16/2008 7:20 AM
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: [Axis2] Axis2/C support for AIX?
Posted by samuel sun <su...@hotmail.com>.
Thanks for your reply, Samisa. But my program seems not going that far, it
crashes at addr_in_handler.c, line 105:
handler = axis2_handler_create(env);
In my source code(1.3.0), axis2_handler_set_invoke is line 113. Using step
in dbx at this line also crashes with Illegal instruction, I guess the
program crashes before this function is called correctly.
Since axis2_handler_create resides in libaxis2_engine.so, which is linked at
link time, while addr_in_handler.o resides in libaxis2_mod_addr.so which is
dynamiclly loaded, I guess this may be some relocation problem. I tried to
copy axis2_handler_create definition from handler.c to addr_in_handler.c and
rename it(avoid symbol conflict), it works. But then it crashes at line 113,
because axis2_handler_set_invoke's definition is also in libaxis2_engine.so.
I don't know what's wrong here, I link the echo with -brtl in order to link
.so library, could that be a problem?
Samisa Abeysinghe-4 wrote:
>
> Looking at the trace, my gut feel is that it fails doe to the call
> axis2_handler_set_invoke(handler, env, axis2_addr_in_handler_invoke); on
> line 102 of addr_in_handler.c
>
> What really happens here is a function pointer assignment. Could you
> please step into this call and see how it goes. Also, is there a tool on
> AIX to track memory corruptions, something similar to valgrind?
>
> Samisa...
>
> samuel sun wrote:
>> Hi guys,
>>
>> I'm also working on this issue, my env is AXIS2/C 1.3, AIX 5.2 and xlc
>> 6.0,
>> and I also encounter the shared library suffix issue, after resolve it
>> temporarily the error when running sample echo is "Illegal instruction
>> (core
>> dumped)" at "addr_in_handler.c" line 105. The call stack print by dbx is
>> the
>> following:
>>
>> .() at 0x0
>> axis2_addr_in_handler_create(0x11000c7f0, 0x110036a10), line 105 in
>> "addr_in_handler.c"
>> unnamed block $b746, line 1318 in "dep_engine.c"
>> axis2_dep_engine_add_module_flow_handlers(0x11000cf90, 0x11000c7f0,
>> 0x1100365b0, 0x110037ab0), line 1318 in "dep_engine.c"
>> axis2_dep_engine_add_new_module(0x11000cf90, 0x11000c7f0, 0x11002bfd0),
>> line
>> 1389 in "dep_engine.c"
>> unnamed block $b758, line 1515 in "dep_engine.c"
>> unnamed block $b757, line 1515 in "dep_engine.c"
>> axis2_dep_engine_do_deploy(0x11000cf90, 0x11000c7f0), line 1515 in
>> "dep_engine.c"
>> axis2_ws_info_list_update(0x11002be10, 0x11000c7f0), line 425 in
>> "ws_info_list.c"
>> axis2_repos_listener_update(0x11002b5b0, 0x11000c7f0), line 297 in
>> "repos_listener.c"
>> axis2_repos_listener_init(0x11002b5b0, 0x11000c7f0), line 324 in
>> "repos_listener.c"
>> axis2_repos_listener_create_with_folder_name_and_dep_engine(0x11000c7f0,
>> 0x11000d8b0, 0x11000cf90), line 141 in "repos_listener.c"
>> axis2_dep_engine_load_client(0x11000cf90, 0x11000c7f0,
>> 0xffffffffffff8a6),
>> line 938 in "dep_engine.c"
>> axis2_build_client_conf_ctx(0x11000c7f0, 0xffffffffffff8a6), line 226 in
>> "conf_init.c"
>> axis2_svc_client_init_transports_from_conf_ctx(0x11000c7f0, 0x11000cb10,
>> 0x0, 0xffffffffffff8a6), line 1168 in "svc_client.c"
>> axis2_svc_client_create_with_conf_ctx_and_svc(0x11000c7f0,
>> 0xffffffffffff8a6, 0x0, 0x0), line 283 in "svc_client.c"
>> axis2_svc_client_create(0x11000c7f0, 0xffffffffffff8a6), line 106 in
>> "svc_client.c"
>> main(argc = 1, argv = 0x0ffffffffffff410), line 86 in "echo.c"
>>
>> I can't get any idea totally how to track this kind of issue, can anyone
>> help?
>>
>>
>> Hal Roseman wrote:
>>
>>> Hi Brent,
>>>
>>> We are also working on this problem. Have you gotten any closer? We
>>> should collaborate.
>>>
>>> - Hal
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG.
>> Version: 8.0.100 / Virus Database: 270.3.0/1499 - Release Date: 6/12/2008
>> 7:13 AM
>>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering; WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/-Axis2--Axis2-C-support-for-AIX--tp17136222p17861881.html
Sent from the Axis - C++ - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: [Axis2] Axis2/C support for AIX?
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Looking at the trace, my gut feel is that it fails doe to the call
axis2_handler_set_invoke(handler, env, axis2_addr_in_handler_invoke); on
line 102 of addr_in_handler.c
What really happens here is a function pointer assignment. Could you
please step into this call and see how it goes. Also, is there a tool on
AIX to track memory corruptions, something similar to valgrind?
Samisa...
samuel sun wrote:
> Hi guys,
>
> I'm also working on this issue, my env is AXIS2/C 1.3, AIX 5.2 and xlc 6.0,
> and I also encounter the shared library suffix issue, after resolve it
> temporarily the error when running sample echo is "Illegal instruction (core
> dumped)" at "addr_in_handler.c" line 105. The call stack print by dbx is the
> following:
>
> .() at 0x0
> axis2_addr_in_handler_create(0x11000c7f0, 0x110036a10), line 105 in
> "addr_in_handler.c"
> unnamed block $b746, line 1318 in "dep_engine.c"
> axis2_dep_engine_add_module_flow_handlers(0x11000cf90, 0x11000c7f0,
> 0x1100365b0, 0x110037ab0), line 1318 in "dep_engine.c"
> axis2_dep_engine_add_new_module(0x11000cf90, 0x11000c7f0, 0x11002bfd0), line
> 1389 in "dep_engine.c"
> unnamed block $b758, line 1515 in "dep_engine.c"
> unnamed block $b757, line 1515 in "dep_engine.c"
> axis2_dep_engine_do_deploy(0x11000cf90, 0x11000c7f0), line 1515 in
> "dep_engine.c"
> axis2_ws_info_list_update(0x11002be10, 0x11000c7f0), line 425 in
> "ws_info_list.c"
> axis2_repos_listener_update(0x11002b5b0, 0x11000c7f0), line 297 in
> "repos_listener.c"
> axis2_repos_listener_init(0x11002b5b0, 0x11000c7f0), line 324 in
> "repos_listener.c"
> axis2_repos_listener_create_with_folder_name_and_dep_engine(0x11000c7f0,
> 0x11000d8b0, 0x11000cf90), line 141 in "repos_listener.c"
> axis2_dep_engine_load_client(0x11000cf90, 0x11000c7f0, 0xffffffffffff8a6),
> line 938 in "dep_engine.c"
> axis2_build_client_conf_ctx(0x11000c7f0, 0xffffffffffff8a6), line 226 in
> "conf_init.c"
> axis2_svc_client_init_transports_from_conf_ctx(0x11000c7f0, 0x11000cb10,
> 0x0, 0xffffffffffff8a6), line 1168 in "svc_client.c"
> axis2_svc_client_create_with_conf_ctx_and_svc(0x11000c7f0,
> 0xffffffffffff8a6, 0x0, 0x0), line 283 in "svc_client.c"
> axis2_svc_client_create(0x11000c7f0, 0xffffffffffff8a6), line 106 in
> "svc_client.c"
> main(argc = 1, argv = 0x0ffffffffffff410), line 86 in "echo.c"
>
> I can't get any idea totally how to track this kind of issue, can anyone
> help?
>
>
> Hal Roseman wrote:
>
>> Hi Brent,
>>
>> We are also working on this problem. Have you gotten any closer? We
>> should collaborate.
>>
>> - Hal
>>
>>
>>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.100 / Virus Database: 270.3.0/1499 - Release Date: 6/12/2008 7:13 AM
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org