RE: 2.6.9 chrdev_open: serial_core: uart_open

[Matthias Urlichs]

Hi, Alan Cox wrote:

> 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.

Note also that gcc does sibling optimization, i.e. it will happily
reduce the code at the end of
	int bar(a,b) { [...] return baz(x,y); }
into something like
	overwrite 'a' with 'x', and 'b' with 'y'
	pop local stack frame, if present
	jump to baz

which saves some stack space and is faster, but makes you wonder
how in hell the
	baz
	foo
stack dump you're seeing in your crash dump came about.

(2.6.13 will turn that off when debugging.)

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@xxxxxxxxxxxxxx
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
There is a vast difference between putting your nose in other people's
business and putting your heart in other people's problems.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/