[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: zxid segmentation fault
John Mitchell wrote:
> I have compiled 0.47 and 0.48 of zxid and I am getting a segmentation
> [jpmitchell@dauntless zxid-0.48]$ ./zxid
> Content-Type: text/html
> <title>ZXID SP SSO</title><body bgcolor="#330033" text="#ffaaff"
> link="#ffddff" vlink="#aa44aa" alink="#ffffff"><font
> face=sans><h1>ZXID SP Federated SSO (user NOT logged in, no
> </pre><form method=post action="zxid?o=P"><h3>Login Using New IdP</h3>
> <i>A new IdP is one whose metadata we do not have yet. We need to know
> the Entity ID in order to fetch the metadata using the well known
> location method. You will need to ask the adminstrator of the IdP to
> tell you what the EntityID is.</i>
> <p>IdP EntityID URL <input name=e size=100><input type=submit name=l1
> value=" Login (SAML20:Artifact) ">
> <input type=submit name=l2 value=" Login (SAML20:POST) "><br>
> Segmentation fault (core dumped)
> I ran gdb to see what was up:
> Core was generated by `./zxid'.
> Program terminated with signal 11, Segmentation fault.
> [New process 23890]
> #0 0x08064adf in zxid_get_ent_by_sha1_name (cf=0x8f8b520,
> sha1_name=0x8f9d47f "s36Te-rgbzReSjVc8vDDGy89tT8") at zxidmeta.c:302
> 302 for (ent = cf->cot; ent; ent = ent->n) /* Check in-memory cache. */
In gdb, please print cf->cot. I bet it is null.
Now, why would that be? Most likely you have empty /var/zxid/cot
directory. This situation should obviously be checked by the
code as empty CoT is a normal situation in new install.
You may be able to work around the situation by using zxcot tool
to add at least one partner metadata.
I'll add the check to next release. Let me know if the workaround
P.S. zxid.c is not exactly the recommended API so you may want to
look at zxidhlo.c instead.
> Seems like an odd place for it to die. This is running on RHEL 5.4
> with kernel 2.6.18-164.9.1.el5. The libraries and what not where
> compiled with gcc version 4.1.2 20080704 (Red Hat 4.1.2-46). Is there
> any known compatibility problems out there or bugs that I should be
> aware of?
> John P. Mitchell <jpmitchell@xxxxxxxxxx>