Andrew Cagney wrote:
> Michal Ludvig wrote:
>>
>> Hi Andrew,
>> I'm getting lots of internal errors due to the fact that this function 
>> is called while running x86-64 testsuite on mainline.
>>
>> +static void
>> +sentinel_frame_pop (struct frame_info *frame,
>> +            void **cache,
>> +            struct regcache *regcache)
>> +{
>> +  internal_error (__FILE__, __LINE__, "Function sentinal_frame_pop 
>> called");
>> +}
>>
>> How can I avoid these errors?
> 
> Can you please post a stack backtrace and a transcript illustrating the 
> problem?  The above assertion is correct - for some reason GDB is trying 
> to pop the wrong frame :-(

Hi again,
I got back to the mainline/"sentinel" problem and have found that it 
happens when a program's function is called from a gdb prompt.

To reproduce create a very simple program:
int func(int arg) { return 2*arg; }
int main(int argc) { return func(argc); }

Then run mainline GDB on x86-64:
(gdb) break main
(gdb) run
(gdb) print func(1)
../../gdb-head/gdb/sentinel-frame.c:102: internal-error: Function 
sentinal_frame_pop called
A problem internal to GDB has been detected.  Further
debugging may prove unreliable.
Quit this debugging session? (y or n)

Attached is a backtrace of this failing GDB.
Any ideas?

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz