On my embedded m68k target, where debugging appears problematic, sometimes 
frames called in frame.c:get_prev_frame() have their frame level set to 
-1. If you have a backtrace limit set (with "set backtrace limit") then 
this would mean the following test is done:


   if (this_frame->level > backtrace_limit)
     {
       error ("Backtrace limit of %d exceeded", backtrace_limit);
     }

This looks like it would be right even if the level is -1. However 
backtrace_limit is unsigned and this results in this_frame->level being 
promoted to an unsigned 0xffffffff value.

Therefore I'm attaching a patch to correct this, simply by making 
backtrace_limit now be signed. Anyone who needs more than 2 billion stack 
levels has bigger problems :-).

I do have write access so can check this in if someone approves.

Jifl

2005-05-23  Jonathan Larmour  <jifl@eCosCentric.com>

	* command.h: Declare new add_setshow_integer_cmd function.
	* cli/cli-decode.c (add_setshow_integer_cmd): New function. Cloned
	from add_setshow_uinteger_cmd.
	* frame.c: backtrace_limit should be signed to prevent matching against
	negative frame levels.
	(_initialize_frame): Call add_setshow_integer_cmd for backtrace limit
	now.



-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine