When dissecting an indirect call reply, if either there's an old-style

or new-style dissector for the reply, we can dissect the reply; there
doesn't have to be a new-style dissector.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@3009 f5534014-38df-0310-8fa8-9805f1628bb7

diff --git a/packet-rpc.c b/packet-rpc.c
index 4d6ab2a68fdfe620fa837f8a5c20468f018869df..b1a033389aed23cbb3ad1d93a8485f041930cde1 100644 (file)
--- a/packet-rpc.c
+++ b/packet-rpc.c
@@ -2,7 +2,7 @@
  * Routines for rpc dissection
  * Copyright 1999, Uwe Girlich <Uwe.Girlich@philosys.de>
  * 
- * $Id: packet-rpc.c,v 1.54 2001/02/09 07:59:00 guy Exp $
+ * $Id: packet-rpc.c,v 1.55 2001/02/09 08:38:13 guy Exp $
  * 
  * Ethereal - Network traffic analyzer
  * By Gerald Combs <gerald@zing.org>
@@ -1307,7 +1307,7 @@ dissect_rpc_indir_reply(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree,
                        procname, rpc_call->proc);
        }
 
-       if (dissect_function == NULL) {
+       if (old_dissect_function == NULL && dissect_function == NULL) {
                /* We don't know how to dissect the reply procedure.
                   Just show the reply stuff as opaque data. */
                offset = dissect_rpc_data_tvb(tvb, pinfo, tree, result_id,