msweet at apple.com
Fri Feb 24 10:44:13 PST 2017
I think if you just run cupsd in gdb you will be able to get a backtrace when it crashes:
sudo gdb /usr/sbin/cupsd
run -f
... wait for crash ...
bt
and then send the output in a response.
> On Feb 24, 2017, at 1:40 PM, tjoen <tjoen at dds.nl> wrote:
>
> On Fri, 2017-02-24 at 10:10 -0500, Michael Sweet wrote:
>> You need to get a backtrace (from the core file, if one was
>> generated) to determine the cause. My guess is something in
>> libprelude, or another supporting library, as otherwise such things
>> would turn up when testing cupsd with valgrind and other security
>> tools.
>
> Thanks for responding.
> I have intalled valgrind because exempi issues a warning if there is
> no valgrind. But I have no experience with valgrind.
> First step is recompiling cups but without packaging into an rpm?
> Also libprelude and PAM?
> Do I need to read the whole valgrind documentation?
> Any suggestion welcome
> _______________________________________________
> cups-devel mailing list
> cups-devel at cups.org
> https://lists.cups.org/mailman/listinfo/cups-devel
_________________________________________________________
Michael Sweet, Senior Printing System Engineer