Re: [SOLVED] Segfault in OpenSSL even though ports GnuTLS demanded (irssi and loudmouth)

[Julian Elischer]

On 2/08/2016 5:16 AM, Bertram Scharpf wrote:
> On Thursday, 28. Jul 2016, 17:56:46 -0400, Jung-uk Kim wrote:
>> On 07/28/16 05:37 PM, Bertram Scharpf wrote:
>>>>> On Thursday, 28. Jul 2016, 15:37:00 -0400, Jung-uk Kim wrote:
>>>>>> On 07/28/16 02:02 PM, Bertram Scharpf wrote:
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> [Switching to Thread 29403080 (LWP 101275/mcabber)]
>>>>>>> 0x285c1245 in OPENSSL_ia32_cpuid () from /usr/local/lib/libcrypto.so.8
>>>>>> Try "ldd /usr/local/lib/libloudmouth-1.so.0.1.0". It looks like a
>>>>>> Kerberos issue.
>>> So, how could I resolve this?
>> You may ask its maintainer (gn...@FreeBSD.org) to add USES+=gssapi and
>> add an option to select GSS-API from ports.
> I looked at the other 4(!) projects that set something like
> USES+=gssapi and copied that to loudmouth, and I even had to
> copy it to irssi. Now the segfault has gone away.
>
> The patch is below.
>
> I will not write a problem report as long as my running
> problem reports aren't deemed worthy of an answer.what Are your current reports?

hmmm do I sense frustration? :-/

Please DO at least drop it into a bug report..
what are your other bug reports? I find the best way to get bug
reports handled is to look in the history of the module concerned,
e.g. https://svnweb.freebsd.org/ports/head/irc/irssi/
or
https://svnweb.freebsd.org/ports/head/net-im/loudmouth/Makefile?view=log

and see who has been working on it recently and email them directly
with a pointer to the bug

The bad part of how the project works is that there is no "manager"
correlating bugs with people directly, so it's really easy to miss bug
reports that you should be aware of.

In this case I've cc'd the people who may best be able to evaluate
your patch, and since it is simple and you've done he work one hopes
that one of them will be able to comment and maybe even commit.

Julian

>
> Bertram
>
>
> ________________________________________________________________________
>
> diff --git a/irc/irssi/Makefile b/irc/irssi/Makefile
> index d9a89fe..f7f9e45 100644
> --- a/irc/irssi/Makefile
> +++ b/irc/irssi/Makefile
> @@ -43,6 +43,7 @@ TRUECOLOR_CONFIGURE_ENABLE= true-color
> CONFIGURE_ARGS+= --disable-ssl
> .else
> USE_OPENSSL= yes
> +USES+=gssapi:base,flags
> .endif
>
> post-patch:
> diff --git a/net-im/loudmouth/Makefile b/net-im/loudmouth/Makefile
> index ead1d4e..0a86d13 100644
> --- a/net-im/loudmouth/Makefile
> +++ b/net-im/loudmouth/Makefile
> @@ -29,6 +29,8 @@ OPTIONS_DEFAULT=GNUTLS
> OPTIONS_RADIO= SSL
> OPTIONS_RADIO_SSL= GNUTLS OPENSSL
>
> +USES+=gssapi:base,flags
> +
> .include <bsd.port.options.mk>
>
> .if ${PORT_OPTIONS:MGNUTLS}
>
>

_______________________________________________
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"

[Bertram Scharpf]

On Tuesday, 02. Aug 2016, 09:50:26 +0800, Julian Elischer wrote:
> On 2/08/2016 5:16 AM, Bertram Scharpf wrote:
> >
> > I will not write a problem report as long as my running
> > problem reports aren't deemed worthy of an answer.
>

> hmmm do I sense frustration? :-/
>
> Please DO at least drop it into a bug report..

I will keep the solution in mind (and in the VCS) until at
least one of my other bug reports receives an answer.

Bertram


--
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de