jack@cca.CCA.COM (Jack Orenstein) (03/22/88)
In article <179@laic.UUCP> darin@laic.UUCP (Darin Johnson) writes: > If I go into a program (completely recompiled under 3.6a) with > sdb, and give a "g" command, it stops in a function at a > BltBitMap function call. If I type "g", "g @", etc. I can't get > past this call. There are no breakpoints set when I display the > breakpoint table. > > Has anyone seen this problem? Yes, I got stuck in a similar way on a call to one of my own functions. I also got a lot of gurus. I was able to reproduce the problem in a series of smaller programs, finally getting down to about 30 lines of very innocent looking code. The problem was always on a reference to a certain field in a struct. I finally tried compiling WITHOUT the +L flag (which had been on the whole time), and that seemed to fix it. I have no explanation as to why +L should cause the problem it did. Has anyone else noticed problems with +L? Jack Orenstein This is not a disclaimer.