Re: Debug into glibc with source code display in gdb on Debian

2025-02-02 Thread Zhaoming Luo
On Sun, Feb 02, 2025 at 12:13:17PM +0100, Samuel Thibault wrote: > Zhaoming Luo, le dim. 02 févr. 2025 19:09:45 +0800, a ecrit: > > On Sun, Feb 02, 2025 at 12:00:17PM +0100, Samuel Thibault wrote: > > > Zhaoming Luo, le dim. 02 févr. 2025 18:55:49 +0800, a ecrit: > > > > ``` > > > > Thread 2 hit Br

Re: Debug into glibc with source code display in gdb on Debian

2025-02-02 Thread Samuel Thibault
Zhaoming Luo, le dim. 02 févr. 2025 19:09:45 +0800, a ecrit: > On Sun, Feb 02, 2025 at 12:00:17PM +0100, Samuel Thibault wrote: > > Zhaoming Luo, le dim. 02 févr. 2025 18:55:49 +0800, a ecrit: > > > ``` > > > Thread 2 hit Breakpoint 1, _hurd_select (nfds=7, pollfds=0x0, > > > readfds=0x103cc20, wr

Re: Debug into glibc with source code display in gdb on Debian

2025-02-02 Thread Zhaoming Luo
On Sun, Feb 02, 2025 at 12:00:17PM +0100, Samuel Thibault wrote: > Zhaoming Luo, le dim. 02 févr. 2025 18:55:49 +0800, a ecrit: > > ``` > > Thread 2 hit Breakpoint 1, _hurd_select (nfds=7, pollfds=0x0, > > readfds=0x103cc20, writefds=0x103cc40, exceptfds=0x103cc60, > > timeout=0x103cba4, sigma

Re: Debug into glibc with source code display in gdb on Debian

2025-02-02 Thread Samuel Thibault
Zhaoming Luo, le dim. 02 févr. 2025 18:55:49 +0800, a ecrit: > ``` > Thread 2 hit Breakpoint 1, _hurd_select (nfds=7, pollfds=0x0, > readfds=0x103cc20, writefds=0x103cc40, exceptfds=0x103cc60, > timeout=0x103cba4, sigmask=0x0) at ./hurd/hurdselect.c:51 > 51 ./hurd/hurdselect.c: No such fi

Debug into glibc with source code display in gdb on Debian

2025-02-02 Thread Zhaoming Luo
Hi, I'm trying to track the curl failed tests by debugging select() function (or system call?) defined in glibc using gdb. When I executed `b _hurd_select` to set a break point and run the program. The gdb stopped at the breakpoint but it gives me the following info: ``` Thread 2 hit Breakpoint 1