_CORE_mutex_Seize

[Wendell Thompson]

My application using code from the ppp example calls 
rtems_bsdnet_semaphore_obtain, which then calls _Core_mutex_Seize, which 
then goes directly into _CORE_mutex_Seize_interrupt_blocking. It then 
swaps tasks and never returns to that task.

Shouldn't _CORE_mutex_Seize go into _CORE_mutex_Seize_interrupt_trylock? 
It appears that rtems_glue.c was built with __RTEMS_APPLICATION__ defined.

This is 4.6.0pre1, built for an M68k custom bsp.