Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rich Coe <Richard.Coe@med.ge.com>
To: gdb@sources.redhat.com
Subject: gdb x86_64 ERESTARTNOHAND
Date: Tue, 14 Jun 2005 13:56:00 -0000	[thread overview]
Message-ID: <20050614085425.6717c34b@godzilla> (raw)

Run the program below in gdb on x86_64, compiled either -m32 or 64 bit,
    stop the execution with control-C
    call a function, in this case doNothing(), but sleep(1) works as well
    continue
gdb passes errno 514 to the program.  514=ERESTARTNOHAND

I see that strace prints out information about ERESTARTNOHAND, so it knows
about it.  I was wondering if gdb should know about this, is this an 
x86_64 kernel error, or what?

Even though strace knows about ERESTARTNOHAND on i386, and prints it,
gdb does not print or cause the program to receive this errno on a 32bit kernel.

-- 
Rich Coe		richard.coe@med.ge.com
General Electric Healthcare Technologies
Global Software Platforms, Computer Technology Team

#include <stdio.h>
#include <sys/select.h>
#include <errno.h>
#include <signal.h>

int myselect(int fd, void* ptr)
{
    printf("myselect\n");
    fd_set in;

AGAIN:
    FD_ZERO(&in);
    FD_SET(fd, &in);

    if(select(32, &in, 0, 0, 0) == -1)
    {
        printf("select error=%d: %s\n", errno, strerror(errno));
    }

    goto AGAIN;

   return 0;
}

int func_two(int fd, void* ptr)
{
    printf("func_two\n");
    return myselect(fd, ptr);
}

int func_one(int fd, void*ptr)
{
    printf("func_one\n");
    return func_two(fd, ptr);
}

void catch(int sig)
{
    char buf[218];
    sprintf(buf, "caught %d\n", sig);
    write(fileno(stdout), buf, strlen(buf));
}

void docatch()
{
    struct sigaction act = { 0 } ;

    act.sa_handler = catch;
    //act.sa_mask = 0;
    act.sa_flags = 0;
    /* auto restart interrupted system calls */
    act.sa_flags = SA_RESTART;

    if(sigaction(SIGINT, &act, NULL) < 0) {
        perror(__FILE__ ": sigaction");
        exit(1);
    }
    if(sigaction(SIGHUP, &act, NULL) < 0) {
        perror(__FILE__ ": sigaction");
        exit(1);
    }
    if(sigaction(SIGTERM, &act, NULL) < 0) {
        perror(__FILE__ ": sigaction");
        exit(1);
    }
}

int a = 0;

void
doNothing()
{
    a += 5;
}

int main(int argc, char*argv[])
{
    doNothing();
    docatch();
    printf("main\n");
    return func_one(fileno(stdin), myselect);
}



             reply	other threads:[~2005-06-14 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 13:56 Rich Coe [this message]
2005-06-14 14:33 ` Daniel Jacobowitz
2005-06-14 20:21   ` Rich Coe
2005-06-14 20:25     ` Daniel Jacobowitz

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=20050614085425.6717c34b@godzilla \
    --to=richard.coe@med.ge.com \
    --cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox