No, I was just checking it out. I'm looking for possible places where I can start to debug this, considering strace is doing the equivalent of shrugging and walking away. :\
Patrick On Tue, Oct 30, 2012 at 5:45 PM, Émeric Maschino <emeric.masch...@gmail.com>wrote: > Patrick, > > Do you mean that your compiled kernel 3.7.0-rc3 fails to pass > test_accept4 [1]? Simply replace the __accept4 function call in the > do_test function with the accept4 syscall. > > Émeric > > > [1] http://marc.info/?l=linux-ia64&m=132110749405138&w=2 > > > 2012/10/30 Patrick Baggett <baggett.patr...@gmail.com>: > > Also, in arch/ia64/kernel/entry.S, I see > > > > data8 sys_setns // 1330 > > data8 sys_sendmmsg > > data8 sys_process_vm_readv > > data8 sys_process_vm_writev > > data8 sys_accept4 > > > > So it appears that the accept4() system call is definitely present in > > upstream -- but it still doesn't work. :( > > > > Patrick > > > > On Tue, Oct 30, 2012 at 9:21 AM, Patrick Baggett < > baggett.patr...@gmail.com> > > wrote: > >> > >> Stephan / Émeric, > >> > >> I compiled Linux 3.7.0-rc3 and installed GDB 7.4.1-3 (sid) -- doing "gdb > >> man" hits a breakpoint at 0x0000000000000000 just like he described. > I'm not > >> sure if it is a kernel thing -- I just compiled mine from Linus's git > >> repository last night. I don't mind doing a little spelunking into the > >> kernel code though -- you think it might have to do with the accept4() > >> syscall? Any other hints? (For a second, I was about to write, "let's > just > >> run GDB in GDB and then we can..." -- doh). > >> > >> Patrick > >> > >> > >> On Mon, Oct 29, 2012 at 3:11 PM, Émeric Maschino > >> <emeric.masch...@gmail.com> wrote: > >>> > >>> Hi Stephan, > >>> > >>> This vaguely reminds me something... Yes, back in February, while I > >>> was still chasing what in the end was missing accept4 syscall, I > >>> experienced a similar issue > >>> (http://lists.debian.org/debian-ia64/2012/01/msg00016.html). From this > >>> post, this was with linux-image-3.1.0-1-mckinley_3.1.8-2_ia64.deb > >>> Debian kernel. I don't remember the GDB version though (probably the > >>> one in Testing repository at this time) and I no more have the GDB > >>> core dump I'm talking about in this post :-( > >>> > >>> Kernel image and GDB currently in Testing repository > >>> (linux-image-mckinley-3.2+45 and gdb-7.4.1-3) work fine as I've just > >>> updated bug #642750 > >>> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642750) using such a > >>> configuration. Looking at my aptitude logs, gdb-7.4.1-1.1 was working > >>> fine too. > >>> > >>> Hope this helps, > >>> > >>> Émeric > >>> > >>> > >>> 2012/10/27 Stephan Schreiber <i...@fs-driver.org>: > >>> > Hello to all, > >>> > > >>> > I just issued the Debian bugreport 691576 > >>> > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691576). > >>> > > >>> > Did you also experience the problem? Do you know more about that, for > >>> > example, working or failing combinations of GDB versions/Debian > Kernels > >>> > on > >>> > ia64? > >>> > > >>> > Thanks in advance. > >>> > > >>> > Stephan Schreiber > >>> > > >>> > > >>> > > >>> > -- > >>> > To UNSUBSCRIBE, email to debian-ia64-requ...@lists.debian.org > >>> > with a subject of "unsubscribe". Trouble? Contact > >>> > listmas...@lists.debian.org > >>> > Archive: > >>> > > >>> > > http://lists.debian.org/20121027131939.horde.yxy-asl8999qi8nlg4tx...@webmail.df.eu > >>> > > >>> > >>> > >>> -- > >>> To UNSUBSCRIBE, email to debian-ia64-requ...@lists.debian.org > >>> with a subject of "unsubscribe". Trouble? Contact > >>> listmas...@lists.debian.org > >>> Archive: > >>> > http://lists.debian.org/caa9xbm6l6fu114t6tkmzgfcivuxum8bion9v2aktvdmciud...@mail.gmail.com > >>> > >> > > >
