All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Compile failure with rt_sigaction on amd64
Date: Fri, 10 Jul 2009 16:16:20 +0530	[thread overview]
Message-ID: <1247222780.6630.24.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <f5a7b3810907100201p514cb9a2p44faaaa42bc59a32@mail.gmail.com>

On Fri, 2009-07-10 at 14:31 +0530, naresh kamboju wrote: 
> Garrett,
> 
> On Fri, Jul 10, 2009 at 10:22 AM, Masatake YAMATO<yamato@redhat.com> wrote:
> > I've found an interesting code in glibc about "rt_sigaction".
> >
> > sysdeps/unix/sysv/linux/x86_64/sigaction.c:
> > int
> > __libc_sigaction (int sig, const struct sigaction *act, struct sigaction *oact)
> >
> >
> >
> > How do you think follow the way to glibc?
> > In addition man page is needed to update.
> >
> > Masatake YAMATO
> >
> 
> Garrett Cooper <yanegomi@gmail.com> wrote:
> >>gcooper@orangebox /scratch/ltp-vanilla/ltp $ /lib/libc.so.6
> >>GNU C Library stable release version 2.9, by Roland McGrath >>et al.
> 
> >>I'm confused -- how will that help us?
> 
> To conform glibc version you are using is 2.9
> 
> >>gcooper@orangebox /scratch/ltp-vanilla/ltp $ gdb
> >>This GDB was configured as "x86_64-pc-linux-gnu"...
> >>(gdb) r
> >>Starting program:
> >>/scratch/ltp-vanilla/ltp/testcases/kernel/syscalls/rt_sigaction>>/rt_sigaction01
> >>rt_sigaction01    0  INFO  :  signal: 34
> >>rt_sigaction01    1  PASS  :  rt_sigaction call succeeded: >>result = 0
> >>rt_sigaction01    0  INFO  :  sa.sa_flags = >>SA_RESETHAND|SA_SIGINFO
> 
> >>Program received signal SIG34, Real-time event 34.
> >>0x00007f770ba0b4f7 in kill () from /lib/libc.so.6
> >>(gdb) where
> >>#0  0x00007f770ba0b4f7 in kill () from /lib/libc.so.6
> >>#1  0x0000000000401c3e in main ()
> >>(gdb)
> 
> 
> As you said in the pervious mail when you try to debug using gdb you
> got a segmentation falut from /lib/libc.so.6.
> 
> So that segmentation fault is generated by glibc.
> 
> 
> As per Masatake YAMATO comments,
> glibc code implementation for libc/sysdeps/unix/sysv/linux/x86_64/sigaction.c
> 
> X86_64:
> 
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/x86_64/sigaction.c?annotate=1.8.2.4&cvsroot=glibc
> 
> X86:
> 
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/sigaction.c?annotate=1.24.2.2&cvsroot=glibc
> 
> Thanks Masatake YAMATO for your information.
> 
> However, before concluding problem/issue need some more Investigation
> Please remove
> -kill(getpid(),signal);
> from rt_sigaction01.c
> And complie and execute and share the results.

I will wait for any of your patches till you investigate all issues.

Regards--
Subrata

> 
> Best regards,
> Naresh Kamboju


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-07-10 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 12:46 [LTP] Compile failure with rt_sigaction on amd64 naresh kamboju
2009-07-07 16:06 ` Garrett Cooper
2009-07-09 14:50   ` naresh kamboju
2009-07-09 17:40     ` Garrett Cooper
2009-07-10  4:52       ` Masatake YAMATO
2009-07-10  9:01         ` naresh kamboju
2009-07-10 10:46           ` Subrata Modak [this message]
2009-07-10 16:49           ` Garrett Cooper
  -- strict thread matches above, loose matches on Subject: below --
2009-07-07 10:12 Garrett Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1247222780.6630.24.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=naresh.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.