[Openswan dev] Re: [Openswan Users] Wildcards in ID_DER_ASN1_DN (rightid)

[Kevan Benson]

On Thursday 15 December 2005 13:03, Paul Wouters wrote:
> On Thu, 15 Dec 2005, Kevan Benson wrote:
> > Sure thing.
> > Backtrace of dumpfile follows (wordwrap turned off on my
> > MUA to facilitate readability):
>
> wow that corrupted this email pretty badly. Had to extract it :P
>
> > [root at test200 ~]# gdb /usr/sbin/ipsec /tmp/core.3785
> >
> > Reading symbols from shared object read from target memory...(no
> > debugging symbols found)...done.
> >
> > I take it you want debugging symbols though, and I'm not sure how to
> > enable that through the openswan.spec build.
>
> On FC4, there is a openswan-debug package with symbols that you can
> install. Another way is to just use rpmbuild -bp and then goto
>  /usr/src/redhat/BUILD/openswan-2.x.y/ and make programs install. Then you
> can point gdb to
> /usr/src/redhat/BUILD/openswan-2.x.y/modobj/programs/pluto/pluto

I was pointing it at ipsec, not pluto.  Here's a better backtrace:

Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xffffe000
Core was generated by `/usr/libexec/ipsec/pluto --nofork 
--secretsfile /etc/ipsec.secrets --ipsecdir /'.
Program terminated with signal 6, Aborted.

warning: svr4_current_sos: Can't read pathname for load map: Input/output 
error

Reading symbols from /usr/lib/libgmp.so.3...done.
Loaded symbols for /usr/lib/libgmp.so.3
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0  0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ea77d5 in raise () from /lib/tls/libc.so.6
#2  0xb7ea9149 in abort () from /lib/tls/libc.so.6
#3  0x080566f5 in passert_fail (pred_str=0x0, file_str=0x0, line_no=0) at 
log.c:612
#4  0x0806d4ff in install_inbound_ipsec_sa (st=0x80f4128) at kernel.c:2237
#5  0x08069152 in quick_inI1_outR1_cryptocontinue (pcrc=0x80f3b40, 
r=0xbfffee10, ugh=0x0) at ikev1_quick.c:1942
#6  0x0807c2d2 in pluto_crypto_helper_ready (readfds=0xbffff9c0) at 
pluto_crypt.c:565
#7  0x0805c2cb in call_server () at server.c:1192
#8  0x0805930b in main (argc=8, argv=0xbffffbe4) at plutomain.c:783


> > Dec 15 12:15:06 test200 pluto[3785]: "test100" #2: ASSERTION FAILED at
> > kernel.c:2237: c->kind == CK_PERMANENT || c->kind == CK_INSTANCE
>
> This one might be already fixed in cvs, so hopefully 2.4.5 should not crash
> for you anymore.

Hope not, or at least hope my backtace helped work towards a resolution.

-- 
Kevan Benson
A-1 Networks