From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Ingham To: Tom Tromey Cc: James Ingham , Insight List Subject: Re: stack window Date: Mon, 10 Apr 2000 13:21:00 -0000 Message-id: <14578.14456.929356.500714@leda.cygnus.com> References: <87vh1pixbf.fsf@cygnus.com> <14578.12895.748586.185553@leda.cygnus.com> <200004102004.NAA11470@ferrule.cygnus.com> X-SW-Source: 2000-q2/msg00060.html Tom, Yeah, this is the same error as the one you reported before where you got a Tcl stack traceback. The reason is the same: not finding a source file causes the Source window's cache to get confused, and you are pretty much lost from there on out. This has to be fixed, but the real solution is to rip out the code and rewrite it, which is a couple two or three of weeks of work. I really don't want to try bandaging this particular bit of code any more, as it is pretty bad, and it implements a very important part of the UI. Jim > Jim> I need more details. In ordinary C code, the stack window works > Jim> fine... I bet you have hit some error that didn't get caught. Maybe > Jim> a source file not found error similar to the "pane5 doesn't exist" > Jim> error you saw earlier... > > I found out how to reproduce it: if I click on a frame, and gdb can't > find the file for that frame, then I get the bad behavior. > > Jim> But, as you may be coming to expect now, we didn't have the time > Jim> to complete the advanced design, so you are left with what is > Jim> there now. > > Thanks for the info. > > T >