Re: Unexpected gdbus behaviour during PAM authentication

On 15/01/17 12:36, David Llewellyn-Jones wrote:
> On 15/01/17 12:04, Bastien Nocera wrote:
>> On Sun, 2017-01-15 at 01:27 +0000, David Llewellyn-Jones wrote:
>>> On 13/01/17 15:47, Bastien Nocera wrote:
>>>>
>> <snip>
>>> and here's the segfault entry from syslog:
>>>
>>> Jan 14 23:12:17 Owen kernel: [ 4683.886530] compiz[11249]: segfault
>>> at
>>> 7f34cd0ac8a0 ip 00007f34f8692908 sp 00007ffe6e955970 error 4 in
>>> libglib-2.0.so.0.4800.1[7f34f8649000+10f000]
>>>
>>> Am I doing something wrong? In case it's important, the segfault
>>> doesn't
>>> occur the first time the module is run, but consistently when it's
>>> called for a second time.
>>
>> Again, look at the LDFLAGS used in pam_fprintd. You can't unload and
>> reload libgobject.so.
> 
> Thanks; I'll take a look at this and figure out what I'm missing.

In case it's useful for others viewing this thread, I added the
following flags to the gcc linker step:

-Wl,-z,nodelete

as shown here:
https://github.com/llewelld/dbus-pam-test/commit/2dbf4c5e8ca52f112eb08718e20289b09a7f19c9

and this seems to have fixed the issue (although there were some other
libtool flags from Bastien's build that I couldn't see how to convert to
gcc, so caveat emptor).

Thanks again Bastien.

David
-- 
Website: http://www.flypig.co.uk
_______________________________________________
dbus mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dbus