bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #61073] [groff]: SEGV with a single option as input


From: G. Branden Robinson
Subject: [bug #61073] [groff]: SEGV with a single option as input
Date: Fri, 27 Aug 2021 03:56:43 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #6, bug #61073 (project groff):


[comment #5 comment #5:]
>   The first sentence in my comment #4 is wrong.
> 
>   The segmentation fault should be provoked by lack of font
> directories, like those in "GROFF_FONT_PATH" and those defined in
> "build/defs.h", FONTPATH.
> 
>   I do neither have "GROFF_FONT_PATH" defined nor the directories in
>
FONTPATH="/usr/local/share/groff/site-font:/usr/local/share/groff/1.22.4/font:/usr/lib/font"

I couldn't reproduce this with the simple expedient of taking my built troff
executable and running it well outside the build directory (say, in /tmp),
which kept it from finding any of the source or build tree device directories
and the compiled-in system defaults (which on my Debian system use /usr as the
installation root, not the /usr/local a default build looks for, and moreover
/usr/lib/font does not exist on a Debian 10 system).

>   In "font.cpp" the string "path" gets a pointer "0x6" which can't be
> accessed.
> 
>   A fix is to give "path" in subroutine "font::load_desc()" in file
> "font.cpp" a value
> 
> char *path = NULL;
> 
>   That results in:
> 
> called subprograms:
> 
> ./groff: error: can't find 'DESC' file in path '(null)'
> ./groff: fatal error: invalid device 'ps'
> 
>   Maybe all declarations of characters need to be given an initial value
> that contains a NULL(?) (in C++ files(?)).

It looks to me like you're using a modified source tree.  That error message
about "in path '(null)'" reveals language that is not present in groff 1.22.4
nor in groff Git HEAD.

Can you reproduce this problem with a build made from a stock source tree?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61073>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]