Browse code

show infomsg for bytecode number -> bytecode name mapping in test mode.

This allows you to find out which bytecode is causing the errors.

Török Edvin authored on 2010/10/18 16:44:38
Showing 1 changed files
... ...
@@ -1468,6 +1468,8 @@ static int cli_loadcbc(FILE *fs, struct cl_engine *engine, unsigned int *signo,
1468 1468
 	return CL_SUCCESS;
1469 1469
     }
1470 1470
     bc->id = bcs->count;/* must set after _load, since load zeroes */
1471
+    if (engine->bytecode_mode == CL_BYTECODE_MODE_TEST)
1472
+	cli_infomsg(NULL, "bytecode %u -> %s\n", bc->id, dbname);
1471 1473
     sigs++;
1472 1474
     if (bc->kind == BC_LOGICAL || bc->lsig) {
1473 1475
         unsigned oldsigs = sigs;