From mboxrd@z Thu Jan 1 00:00:00 1970 From: Duane Ellis To: insight@sourceware.cygnus.com Subject: Re: Buttons not disabled on startup. Date: Thu, 13 Jul 2000 11:00:00 -0000 Message-id: <200007131759.NAA07927@mercury.franklin.com> References: X-SW-Source: 2000-q3/msg00064.html Wait... mo> I just noticed that the step, next, finish, and continue buttons mo> are not disabled when you first start insight. I should not be mo> able to press these buttons until after I actually run the mo> program. If I go ahead and press one of the buttons, it talks to mo> gdb and notices that nothing is running. Only then do the buttons mo> become disabled. jingham> This is a recent breakage, then. Insight certainly used to grey out all > these buttons till the executable was running. I seem to remember this *NOT* being a 'breakage' but it is suppose to be that way. What you describe is *TRUE* only in a operating system based implimentation. It is *NEVER* true in a *ROM* or *SIMULATION* based situation. Manytimes you need to single step through the startup code to debug the startup code. -Duane Ellis (Wanna see a cool eBook: http://www.franklin.com ...)