Re: static functions are your friends (Was GPIO revisited)

[christos%astron.com@localhost (Christos Zoulas)]

In article <118171B1-B7E9-4B0E-AA9A-99F505C86C39%msys.ch@localhost>,
Marc Balmer  <marc%msys.ch@localhost> wrote:
>
>Am 09.08.2009 um 20:34 schrieb Manuel Bouyer:
>
>> On Sun, Aug 09, 2009 at 08:25:04PM +0200, Marc Balmer wrote:
>>> [...]
>>> See, that is why I do not declare functions static.  Gcc likely
>>> inlines them and ddb trace output becomes useless.
>>
>> that's not really true. You can use ddb's output with gdb, and gdb
>> will tell you exactly where the issue happened, better than ddb
>> (ddb gives you a function name, gdb gives you a line number).
>> Codes I'm working on includes static functions, which sometimes gets
>> inlined and I've always been able to make sense of ddb's output,
>> even when the crash did happen on someone else's box.
>
>ddb's trace command should produce the function name.  no voodoo  
>should be required.

It can't. It is lost if the function is inlined.

christos