warning: Illegal offset error?

I was attempting to edit a page on a site running Drupal 6.16 and I got the following error message:

* warning: Illegal offset type in /home/msvehicl/public_html/includes/path.inc on line 75.
* warning: Illegal offset type in isset or empty in /home/msvehicl/public_html/includes/path.inc on line 78.
* warning: mysqli_real_escape_string() expects parameter 2 to be string, array given in /home/msvehicl/public_html/includes/database.mysqli.inc on line 323.
* warning: Illegal offset type in /home/msvehicl/public_html/includes/path.inc on line 87.

It looks like there is a problem with PathAuto but I am not sure. I tried updating to the dev release of PathAuto but that has not helped. The rest of the modules are up to date. Has any one seen this error message before? I have been googling for the last couple of hours and I figured I ought to just ask if anyone in the Florida group has run across this problem.

Here are lines 83 through 88 from the path.inc file mentioned in the error:

// Check $no_src for this $path in case we've already determined that there
// isn't a path that has this alias
elseif ($action == 'source' && !isset($no_src[$path_language][$path])) {
// Look for the value $path within the cached $map
$src = '';
if (!isset($map[$path_language]) || !($src = array_search($path, $map[$path_language]))) {
// Get the most fitting result falling back with alias without language
if ($src = db_result(db_query("SELECT src FROM {url_alias} WHERE dst = '%s' AND language IN('%s', '') ORDER BY language DESC, pid DESC", $path, $path_language))) {
$map[$path_language][$src] = $path;
}
else {
// We can't record anything into $map because we do not have a valid
// index and there is no need because we have not learned anything
// about any Drupal path. Thus cache to $no_src.
$no_src[$path_language][$path] = TRUE;
}

For the record, I am only using two taxonomy vocabularies and they only have five or six terms listed in each. The taxonomy was added after the content and then I went back and added the appropriate terms to the node. Not sure if that has anything to do with the problem but I figured I would mention it.

If there is any other bit of information that might help resolve the issue, let me know.