When running the tx509 test (with no args), it ends up generating a SIGILL. GDB says the instruction is 'ud2a' which I believe is the guaranteed illegal opcode on ia32. Not sure why it's being generated though. This occurs on both FreeBSD 7 x86 and x64. FreeBSD 5 and 6 do not exhibit this behavior. All are being run within VMWare Server v1.0.x, but that's never been an issue before.
Just for testing purposes, I also tried using the 'no-asm', 'no-sse2', and '386' flags, and edited Configure to use '-O0 -g' instead of '-O3' and it also generates the same thing. Here's what GDB says: Starting program: /usr/home/build/openssl-fips-1.2/apps/openssl x509 -in fff.p -inform p -outform d [New LWP 100100] [New Thread 0x28401100 (LWP 100100)] Program received signal SIGILL, Illegal instruction. [Switching to Thread 0x28401100 (LWP 100100)] 0x0815b5e0 in PEM_read_bio_X509_AUX (bp=0x284051c0, x=0x0, cb=0x80c2a60 <password_callback>, u=0x0) (gdb) bt #0 0x0815b5e0 in PEM_read_bio_X509_AUX (bp=0x284051c0, x=0x0, cb=0x80c2a60 <password_callback>, u=0x0) #1 0x080c3843 in load_cert (err=0x28405040, file=0xbfbfedc3 "fff.p", format=3, pass=0x0, e=0x0, cert_descrip=0x81d3290 "Certificate") at apps.c:821 #2 0x080af73e in x509_main (argc=0, argv=0xbfbfecc0) at x509.c:632 #3 0x0809082b in do_cmd (prog=0x28406200, argc=7, argv=0xbfbfeca4) at openssl.c:396 #4 0x080904b8 in main (Argc=7, Argv=0xbfbfeca4) at openssl.c:315 (gdb) disas Dump of assembler code for function PEM_read_bio_X509_AUX: 0x0815b5e0 <PEM_read_bio_X509_AUX+0>: ud2a End of assembler dump. $ gcc --version gcc (GCC) 4.2.1 20070719 [FreeBSD] Any ideas? GCC issue perhaps? Thanks. -Brad ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
