> Couple of thoughts from a quick skim of the code/git history: > 1. I presume giop_complete_request_list is for matching request/reply. > Grepping its use will probably give you some clues as to where to look.
Thanks for the pointer. Rummaging in packet-giop.c it looks like requests and replies are stored in a hash table giop_complete_reply_hash and the key used for this is packet_info->fd->num Does that look right, am I on the right track? If so, then I guess I need to look at where this number comes from and if it is used for anything else. Any help anyone? > 2. I'd recommend using the latest dev branch (master or at least master-2.0). > Any fixes you find would need to be applied there (master) first and then >backported to 1.12 (and 2.0) I had a quick look at 2.0. So far I've fallen over at the first hurdle. I tried following the build instructions and the first nmake -f Makefile.nmake verify_tools fails with a file win32.mak not found error. So I guess I'm looking at the wrong instructions. Can someone point me at how to build 2.0 for Windows. Thanks Andy Ling --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ---------------------------------------------------------------------------------------
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
