Newer Perl interpreters are becoming more and more picky about UTF-8 sanity (valid multibyte sequences). Sometimes, LXR needs to examine file contents prior to deciding whether it will display it or not. If this file does not contain text (graphics or otherwise binary), there is a high probability that runs of bytes does not form a valid UTF-8 sequence. In this case, Perl issues a fatal error.
Debian seems to not set properly the working directory before launching a CGI script. As a consequence, relative file designations which rely on the working directory to be the LXR root directory will fail and a "file not found" error is displayed.
A configuration file is dependent upon mod_version Apache module
but Ubuntu Apache (reported at least for Ubuntu 12.04 LTS)
does not load the module by default.
When LXR scripts are launched, the current working directory is not set to the LXR root directory. OS-relative file paths in lxr.conf cannot be correctly resolved.
To fix the problem, edit custom.d/lxr.conf, "HTML subsection" and add the OS-absolute path of the LXR root directory in front of all HTML template designations. When done, copy the modified file to its final destination as usual.
'alternate_stylesheet'which are not file paths but HTML references.
A misconception of
TRUNCATE TABLE in MySQL causes
a very slow global database purge (with option
which becomes noticeable on big trees like a Linux kernel.
As of MySQL 5.5.5, default storage engine changed from MyISAM to InnoDB. Despite an improvement in transaction reliability, performance has drastically degraded: indexing by genxref is now twice as long.
PostgreSQL offers several methods to connect to a database.
The default one uses Unix-domain sockets.
Under some circumstances,
the Perl DB library may fail to access the LXR database.
The work-around is to request explicitly the TCP access method in the
'dbname' configuration parameter by adding:
Many language descriptions are faulty or, at best, incomplete. Only C, C++ and Perl can be considered reliable.
This is not really an LXR bug. ctags uses elementary parsers for secondary languages (read: not C nor C++). These parsers do not implement complete language grammar.
'range'function in lxr.conf loses release tags.
If your Java code contains
import static statements,
the parser fails on
and enters an endless loop
which freezes the screen on the previous line.
When trying to hyperlink
the generic-based HTML parser may fail and not recover,
leading to an endless loop.
It is also not protected against "external" URI
where the double slash is taken for an empty file path.
Two lines (419 and 485) in ident use relaxed Perl syntax instead of "bullet-proof" code. Comment for bug #233 contains a patch.
Prior to release 2.0.0, error messages are only sent to the browser error log. This usually requires administrator privileges to retrieve the information.
Starting with release 0.11, this directory is set to "read-only" mode to discourage people from making changes. It thus becomes a reliable reference for stored files. Any LXR customisation must be done in the custom.d/ directory (lxrconf.d/ prior to release 1.0).
Free-text search is unavailable due to the specific format of the VCS database (read: they do not use plain files).
CVS does not manage version for directories.
If you change version for something other than
you get the infamous "file does not exist" error message.
Approximately 0.5 second per line (on a 3.4 GHz processor!); but do not blame Mercurial, something is wrong in LXR code interfacing with the system.
They are not compiler-grade (and very far from that). They are limited to lexically extracting runs of characters looking like identifiers (independently of their semantics).
Ignores an eventual sigil when assembling identifiers. This results in confusion of symbols with different roles into a single highlighting.
$while functions have no prefix.
Ignores identifier classification since it does not manage semantics. This results too in confusion of symbols with different roles into a single highlighting.
URI references are hyperlinked only if they point to another document in the source tree.
The parser gets easily confused if the content part (outside HTML tags) contains quotes or double quotes. It causes an out-of-sync situation.
Due to ctags limitation,
subs and no variables are indexed.
Variables are accidentally highlighted
if their name, without sigil, is the same as a function.
Occurrences of characters such as
" in patterns are likely to cause out-of-sync situations.
require will hyperlink to the target
file only if the name is a string relative to source-tree root.
Also, the name cannot contain quotes (
or double quotes (
Multiple includes from a single
instruction are not handled.
You can compare two files differing in only one variable.
You can compare two files differing in any number of variables provided you set all required variables before clicking on the "Change" button.
The new differences will be computed between the most recently selected version and the newly requested, not between the base version (the one active when you clicked on the "diff markup" link) and the newly requested version.