Manual Page causes Memory Fault

[Dwight Pace]

HP-UX v11.0 does the following

HP-UX v11.0
$ man $PATH
Memory fault
$ ls
Mail junk.c
$ man judefgkgkgkgkgkgk
No manual entry for judefgkgkgkgkgkgk.
$ $PATH
ksh:
/usr/local/bin:/usr/bin:/usr/ucb:/usr/ccs/bin:/usr/contrib/bin:/usr/bin/X1d
$ man
/usr/local/bin:/usr/bin:/usr/ucb:/usr/ccs/bin:/usr/contrib/bin:/usr/bin/Xd
No manual entry for
/usr/local/bin:/usr/bin:/usr/ucb:/usr/ccs/bin:/usr/contrib/.

I noticed that Solaris is able to interpret this command correctly

type man $PATH on Solaris gives

No manual entry for
/usr/local/bin:/usr/bin:/usr/ucb:/usr/ccs/bin:/usr/contrib/.

which is the correct response.

The HP-UX has a some sort of a problem with this.

Anyone got any ideas about this.


Dwight

[Dan Hull]

I get the same error if my $PATH variable is set to its default, which is about
4 screen lines long. But if I set it to something shorter, like:

/usr/sbin:/sbin:/opt/socks/bin:/usr/bin:/opt/ansic/bin

and then do the command man $PATH, I get what you expect (the "No manual
entry..." error). It might be just because the man command is having trouble
parsing the very-long line. There may also be something in the path that it
can't handle.

I wonder why you would want to do a man on your $PATH variable! Is there
another command you're actually using that's also doing this?

[Chris Anoruo_1]

If there is a (.) dot on $PATH, you will definitely get a coredump and it is
also a security issue.

[Chris Anoruo_1]

If there is a (.) dot in your $PATH, you will definitely get a coredump and it
is also a security issue.