Messages in this thread | | | Subject | RE: 2.6.9 chrdev_open: serial_core: uart_open | From | Alan Cox <> | Date | Sat, 16 Jul 2005 01:12:48 +0100 |
| |
On Gwe, 2005-07-15 at 13:11 -0700, karl malbrain wrote: > N.b. I don't pretend to understand how uart_change_pm, uart_startup, and > uart_block_til_ready could ALL be on the call stack. Uart_open calls them > sequentially. Perhaps you might explain how this works? Thanks, karl m
gcc does smart things including deferring stack cleanup so that it can turn
push, push, call, adjust stack, push, push call .. etc
into a sequence with less stack pointer adjustment for performance reasons. That sometimes fools the traceback code. A good rule of thumb is to trace the sequence of calls and assume that the last sane sequence is the one that occurred before the failure.
Alan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |