Segmentation Fault
Posted in 2008
Topics: General Discussion
Hi, I have an application written in JAM(GUI) interfacing with the informix IDS. From the application a segmentation fault occurs. The informix entry point in the debug stack below is from sqli_db_open() Any idea what could be the reason? thanks Dorai Program terminated with signal 11, Segmentation fault. #0 0x0063e8e1 in __nss_database_lookup () from /lib/libc.so.6 (gdb) bt #0 0x0063e8e1 in __nss_database_lookup () from /lib/libc.so.6 #1 0x0063faa1 in __nss_passwd_lookup () from /lib/libc.so.6 #2 0x005eca2e in getpwnam_r@@GLIBC_2.1.2 () from /lib/libc.so.6 #3 0x005ec3d8 in getpwnam () from /lib/libc.so.6 #4 0x08174edd in ifx_getpwnam () #5 0x0816fb82 in ggethomepath () #6 0x0816d92d in greadenv () #7 0x0816de93 in init_getenv () #8 0x0816ec0d in idx_ggetenv () #9 0x08175f28 in _sqdbgsetup () #10 0x081723e4 in ostcb_alloc () #11 0x0817240b in CheckOsInit () #12 0x08172448 in getoserr () #13 0x080d0da6 in chkAPIerr () #14 0x080d0c34 in CheckGlobInit () #15 0x080cdd7a in sqli_db_open () #16 0x08082ef7 in dm_inf_logon () #17 0x08074b83 in dm_infsup () #18 0x08072d5b in dm_call_fnc () #19 0x0806a287 in dm_logon () #20 0x0806a709 in declare_connection () #21 0x08069cb4 in dm_do_dbms () #22 0x0806e270 in jpl_sup () #23 0x0804e5c5 in sup_fnc_rw () #24 0x08099bfb in do_dbi () #25 0x08099bbc in do_dbms () #26 0x08098d38 in sm_jplexec () #27 0x080979ef in exec_jpl () #28 0x08097437 in exec_attch () #29 0x080965cc in sm_jpcall_fnc () #30 0x0808b7f8 in sm_call_fnc () #31 0x0808f7d2 in exec_func () #32 0x0808f9c1 in sm_fe_1proc () #33 0x08095848 in field_entry () #34 0x08093f24 in sm_input () #35 0x08084a0e in jm_top_open () #36 0x0808486f in sm_jtop () #37 0x0804ec37 in main (argc=2, argv=0xbfdfd534) at jmain.c:492
Hi,
it is during authentication (or username/password
lookup for other purpose).
This stack - is it from an oninit process of the IDS
server? Or is it from a process of your application?
Are you using PAM for authentication?
If the stack is from oninit process of server and you
are using PAM, then try to set onconfig parameter
PAM_STACKSIZE to e.g. 256. You may even try
value 512 for that parameter.
(I'm not sure whether this parameter would have
any effect on the client side.)
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Herbert Kircher
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 02.07.2008 12:22:54:
> Hi,
>
> I have an application written in JAM(GUI) interfacing with the informix
IDS.
> >From the application a segmentation fault occurs. The informix
> entry point in
> the debug stack below is from sqli_db_open()
>
> Any idea what could be the reason?
>
> thanks
> Dorai
>
> Program terminated with signal 11, Segmentation fault.
> #0 0x0063e8e1 in __nss_database_lookup () from /lib/libc.so.6
> (gdb) bt
> #0 0x0063e8e1 in __nss_database_lookup () from /lib/libc.so.6
> #1 0x0063faa1 in __nss_passwd_lookup () from /lib/libc.so.6
> #2 0x005eca2e in getpwnam_r@@GLIBC_2.1.2 () from /lib/libc.so.6
> #3 0x005ec3d8 in getpwnam () from /lib/libc.so.6
> #4 0x08174edd in ifx_getpwnam ()
> #5 0x0816fb82 in ggethomepath ()
> #6 0x0816d92d in greadenv ()
> #7 0x0816de93 in init_getenv ()
> #8 0x0816ec0d in idx_ggetenv ()
> #9 0x08175f28 in _sqdbgsetup ()
> #10 0x081723e4 in ostcb_alloc ()
> #11 0x0817240b in CheckOsInit ()
> #12 0x08172448 in getoserr ()
> #13 0x080d0da6 in chkAPIerr ()
> #14 0x080d0c34 in CheckGlobInit ()
> #15 0x080cdd7a in sqli_db_open ()
> #16 0x08082ef7 in dm_inf_logon ()
> #17 0x08074b83 in dm_infsup ()
> #18 0x08072d5b in dm_call_fnc ()
> #19 0x0806a287 in dm_logon ()
> #20 0x0806a709 in declare_connection ()
> #21 0x08069cb4 in dm_do_dbms ()
> #22 0x0806e270 in jpl_sup ()
> #23 0x0804e5c5 in sup_fnc_rw ()
> #24 0x08099bfb in do_dbi ()
> #25 0x08099bbc in do_dbms ()
> #26 0x08098d38 in sm_jplexec ()
> #27 0x080979ef in exec_jpl ()
> #28 0x08097437 in exec_attch ()
> #29 0x080965cc in sm_jpcall_fnc ()
> #30 0x0808b7f8 in sm_call_fnc ()
> #31 0x0808f7d2 in exec_func ()
> #32 0x0808f9c1 in sm_fe_1proc ()
> #33 0x08095848 in field_entry ()
> #34 0x08093f24 in sm_input ()
> #35 0x08084a0e in jm_top_open ()
> #36 0x0808486f in sm_jtop ()
> #37 0x0804ec37 in main (argc=2, argv=0xbfdfd534) at jmain.c:492
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Hi,
The stack is from the client application process and not from oninit.
I am not sure about the flow of control in the stack from sqli_db_open() to
getpwnam_r() which is leading to the error.
regards
Dorai
Bug in __nss_database_lookup? I'd check out - http://www.linuxforums.org/