Global debugging help req

[Bakken, Luke]

Hello all,

I have been using global for a while to index my company's source code with 
great success. However, I've run into a problem that I don't know how to debug 
and was wondering if someone here could start me off in the right direction.

Currently I'm using the Borland compiler to build global for Win32. The three 
source trees that I index each contain about 1100 files. Each tree is only 
slightly different from the others in content. This may not seem like important 
info, but you'll see why it is as I describe the issue.

The index files build fine for the first two trees, however on the third tree I 
get a memory access violation about halfway through on one particular file, 
whose contents are identical to those in the other trees (other files in this 
tree processed prior to this are not identical, however). If I run gctags on 
this file it finds object definitions OK. If I cut this file in half, the tag 
building process continues OK until another file down the line, which then dies 
with another error.

I have built a debug version of global in hopes to find the problem and I can 
use the Borland debugger to set breakpoints, etc etc. However when I get to the 
spot where the memory error occurs, I can only see the assembly language 
version of the code that causes the problem, which doesn't help me one bit.

If anyone on this list can give me some pointers on where to begin debugging 
this problem, I would really appreciate it. I'm also going to build global 
under cygwin and see if the problem still occurs.

Thanks,
Luke