Re: kallsyms __print_symbol prints first weak symbol encountered

2007-10-30 Thread Mathieu Desnoyers
* Paulo Marques ([EMAIL PROTECTED]) wrote: > Mathieu Desnoyers wrote: > >Hi, > > Hi, > > >[...] > >kallsyms returns the first symbol encountered, even though it is weak, > >when it should in fact return sys_ni_syscall. > > > >Is it a concern for anyone else out there ? Would it make sense to fix

Re: kallsyms __print_symbol prints first weak symbol encountered

2007-10-30 Thread Rusty Russell
On Wednesday 31 October 2007 04:49:02 Mathieu Desnoyers wrote: > kallsyms returns the first symbol encountered, even though it is weak, > when it should in fact return sys_ni_syscall. Yes, it's an arbitrary choice, but preferring non-weak symbols would definitely be a win. Thanks! Rusty. - To un

Re: kallsyms __print_symbol prints first weak symbol encountered

2007-10-30 Thread Paulo Marques
Mathieu Desnoyers wrote: Hi, Hi, [...] kallsyms returns the first symbol encountered, even though it is weak, when it should in fact return sys_ni_syscall. Is it a concern for anyone else out there ? Would it make sense to fix it ? I don't know if it is a concern, but if we're going to fix

kallsyms __print_symbol prints first weak symbol encountered

2007-10-30 Thread Mathieu Desnoyers
Hi, I am try to see how I can use kallsyms to get the mapping syscall id -> syscall name by listing all the symbols corresponding to the function pointers present in the sys_call_table. However, I just ran into what I consider an unusual behavior of kallsyms: when I list the sys_ni() (not impleme