history_comment errors found in -orig PATH may be reported against source code path

[Gary Dixon]

The following command should display history comments 1, 2, and 3 in pnotice_paths_.pl1. It displays that data after printing error messages about these three comments against both the source file and the -orig PATH file. However, messages against the -orig PATH file include the wrong pathname in the error message.

hcom ds bound_pnotice_.s::pnotice_paths_.pl1 1:3 -orig >ldd>t>s>==::==

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1
   Comment 1 has null approve and audit values a null install value is required.

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1
   Comment 2 has null approve and audit values a null install value is required.

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1
   Comment 3 has null approve and audit values a null install value is required.

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1
   Comment 1 has null approve and audit values a null install value is required.

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1
   Comment 2 has null approve and audit values a null install value is required.

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1
   Comment 3 has null approve and audit values a null install value is required.

>user_dir_dir>Multics>GDixon>lib>s>bound_pnotice_.s::pnotice_paths_.pl1:
  1) change(1981-05-01,Stansbury), approve(), audit(), install(1986-11-12,MR12.0-1213):
  2) change(1981-12-01,Stansbury), approve(), audit(), install(1986-11-12,MR12.0-1213):
  3) change(1982-10-01,Stansbury), approve(), audit(), install(1986-11-12,MR12.0-1213):
r 13:08 1.668 32 level 2

This is caused by an error in hcom_process_seg_.pl1, whose process_tokens internal procedure references the wrong variable declared in its outer procedure. It references d.seg instead of the particular seg substructure passed to comment_parse.

[Gary Dixon]

Duplicate of bug #190.