[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [issues] arm gdb backtrace for read syscall
- To: "Matthieu CASTET" <matthieu.castet@xxxxxxxxxx>
- Subject: Re: [issues] arm gdb backtrace for read syscall
- From: "Carlos O'Donell" <carlos@xxxxxxxxxxxxxxxx>
- Date: Fri, 17 Oct 2008 16:15:50 -0400
On Fri, Oct 17, 2008 at 12:28 PM, Matthieu CASTET
> 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?
Could you describe the behaviour you would like?
e.g. I would like frame #2 to show the correct frame.