From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gdb/snapshot
Date: Thu, 24 Aug 2006 12:46:55 -0700 (PDT) [thread overview]
Message-ID: <20060824194655.B2FA048A54@busybox.net> (raw)
Author: aldot
Date: 2006-08-24 12:46:55 -0700 (Thu, 24 Aug 2006)
New Revision: 15981
Log:
- remove patch that was already applied upstream
Removed:
trunk/buildroot/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch
Changeset:
Deleted: trunk/buildroot/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch
===================================================================
--- trunk/buildroot/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch 2006-08-24 19:45:47 UTC (rev 15980)
+++ trunk/buildroot/toolchain/gdb/snapshot/770-debian_vfork-done-spelling.patch 2006-08-24 19:46:55 UTC (rev 15981)
@@ -1,12 +0,0 @@
-diff -ur gdb-6.3.50.20050915/gdb/linux-nat.c gdb-6.3.50.20050915-patched/gdb/linux-nat.c
---- gdb-6.3.50.20050915/gdb/linux-nat.c 2005-09-10 13:11:02.000000000 -0500
-+++ gdb-6.3.50.20050915-patched/gdb/linux-nat.c 2005-09-15 19:57:23.000000000 -0500
-@@ -458,7 +458,7 @@
- generally not encounter vfork (vfork is defined to fork
- in libpthread.so).
-
-- The holding part is very easy if we have VFORKDONE events;
-+ The holding part is very easy if we have VFORK_DONE events;
- but keeping track of both processes is beyond GDB at the
- moment. So we don't expose the parent to the rest of GDB.
- Instead we quietly hold onto it until such time as we can
next reply other threads:[~2006-08-24 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 19:46 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-24 19:45 [Buildroot] svn commit: trunk/buildroot/toolchain/gdb/snapshot aldot at uclibc.org
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=20060824194655.B2FA048A54@busybox.net \
--to=aldot@uclibc.org \
--cc=buildroot@busybox.net \
/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