public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: kevinb@sourceware.org To: src-cvs@sources.redhat.com Subject: src/rda/unix ChangeLog ptrace-target.c thread-db.c Date: Fri, 02 Dec 2005 20:52:00 -0000 [thread overview] Message-ID: <20051202205204.17763.qmail@sourceware.org> (raw) CVSROOT: /cvs/src Module name: src Changes by: kevinb@sourceware.org 2005-12-02 20:52:04 Modified files: rda/unix : ChangeLog ptrace-target.c thread-db.c Log message: * ptrace-target.c (ptrace_break_program): Use SIGSTOP instead of SIGINT to interrupt inferior process. * thread-db.c (thread_db_break_program): Likewise. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/ChangeLog.diff?cvsroot=src&r1=1.57&r2=1.58 http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/ptrace-target.c.diff?cvsroot=src&r1=1.10&r2=1.11 http://sourceware.org/cgi-bin/cvsweb.cgi/src/rda/unix/thread-db.c.diff?cvsroot=src&r1=1.17&r2=1.18
reply other threads:[~2005-12-02 20:52 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051202205204.17763.qmail@sourceware.org \ --to=kevinb@sourceware.org \ --cc=src-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).