[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [issues] arm gdb backtrace for read syscall
- To: Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx>
- Subject: Re: [issues] arm gdb backtrace for read syscall
- From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
- Date: Mon, 20 Oct 2008 10:23:34 +0200
Carlos O'Donell a écrit :
> On Fri, Oct 17, 2008 at 12:28 PM, Matthieu CASTET
> <matthieu.castet@xxxxxxxxxx> wrote:
>> I am using eglibc-2.7, and the gdb backtrace doesn't work when a thread
>> is block on a read syscall. 
>> Can't we manage to make the read entry code more gdb friendly ?
>> #0 0x4003383c in read ()
>> from /opt/arm-eglibc/arm-none-linux-gnueabi/libc/lib/libpthread.so.0
>> #1 0x400330ac in __pthread_enable_asynccancel () at cancellation.c:42
>> #2 0x00000000 in ?? ()
> What you mean by more gdb friendly?
I mean it avoid to distrub gdb backtrace algorithm.
I don't what arm gdb use for backtrace (frame pointer, stack scan, ...).
> Could you describe the behaviour you would like?
I would like that when a process is block on the read system call, I can
get the complete backtrace ie getting caller of the read syscall.
This is the case for example for sigwaitinfo syscall.