On 12/14/20 2:14 PM, Bernhard Übelacker wrote:
Hello Mack Stanley,
I am not involved in packaging a2ps, but I guess there are some more
information needed to even start investigating.
I tried several files in a VM to send to a2ps and I could
not observe a crash.
Therefore could you supply to this bug which command line is used
to trigger the crash?
If possible a link to or if small enough attaching the input you
give to a2ps?
A crash should at least have a trace in dmesg output,
could you add this?
And possibly you could install the package "systemd-cordump".
That way some more information should be written
to the journal - e.g. visible in 'journalctl -e'.
Kind regards,
Bernhard
Dear Bernhard,
Thanks so much for your interest and your message. I very recently
realized that my bug report is in error and hoped that I would be able
to correct or withdraw it before troubling anyone.
Here is how to reproduce the segfault I observed (in wither 32 or 64 bit
debian a2ps):
Near the top of /etc/a2ps-site.cfg comment out one or both of the lines
_____
Options: --encoding=latin1
Options: --medium=libpaper
_____
Then just execute
a2ps
The result will be a crash with simply
Segmentation Fault
-------
I am very sorry to have filed a false bug report. I had tried two 32
bit installations and one 64 bit. Evidently I made the same mistake in
both 32 bit installations: I must have installed with an old Fedora
a2ps-site.cfg already in /etc/ , which the Debian installation politely
refused to overwrite. The default Fedora a2ps-site.cfg has those two
lines as
#Options: --encoding=latin1
Options: --medium=_glibc
After removing "#" from the first line, the debian build a2ps complains
helpfully about the second line. But with the "#" it just segfaults.
I am sorry it took me so long to find this mistake. It wasn't till I
built 32 bit a2ps from the GNU source that I saw the problem
(http://ftp.gnu.org/gnu/a2ps/a2ps-4.14.tar.gz./configure --prefix=/usr
--with-gnu-gettext --with-medium=letter ).
It would be nice if a2ps itself had been more forthcoming about my
mistake rather than segfaulting. But it was just that---my mistake.
Again, my apologies for wasting your time and my thanks for your interest.
Best regards, Mack
