gdb: adding a patch to handle well the edit cmd + SIGWINCH.
It's reported to upstream since two years ago, through their patches mailing list.
This commit is contained in:
parent
d4bf329dde
commit
ae3a1519e4
@ -30,6 +30,8 @@ stdenv.mkDerivation rec {
|
|||||||
sha256 = "08vcb97j1b7vxwq6088wb6s3g3bm8iwikd922y0xsgbbxv3d2104";
|
sha256 = "08vcb97j1b7vxwq6088wb6s3g3bm8iwikd922y0xsgbbxv3d2104";
|
||||||
};
|
};
|
||||||
|
|
||||||
|
patches = [ ./edit-signals.patch ];
|
||||||
|
|
||||||
# I think python is not a native input, but I leave it
|
# I think python is not a native input, but I leave it
|
||||||
# here while I will not need it cross building
|
# here while I will not need it cross building
|
||||||
nativeBuildInputs = [ texinfo python ]
|
nativeBuildInputs = [ texinfo python ]
|
||||||
|
25
pkgs/development/tools/misc/gdb/edit-signals.patch
Normal file
25
pkgs/development/tools/misc/gdb/edit-signals.patch
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
Patch adapted from
|
||||||
|
https://www.sourceware.org/ml/gdb-patches/2012-08/msg00439.html
|
||||||
|
|
||||||
|
Without it, spawning a terminal 'vim' from gdb 'edit' cmd, makes
|
||||||
|
all gdb grazy.
|
||||||
|
|
||||||
|
diff --git a/gdb/tui/tui-win.c b/gdb/tui/tui-win.c
|
||||||
|
index 7ea0fec..be5455c 100644
|
||||||
|
--- a/gdb/tui/tui-win.c
|
||||||
|
+++ b/gdb/tui/tui-win.c
|
||||||
|
@@ -831,11 +831,12 @@ void
|
||||||
|
tui_initialize_win (void)
|
||||||
|
{
|
||||||
|
#ifdef SIGWINCH
|
||||||
|
-#ifdef HAVE_SIGACTION
|
||||||
|
+#if defined (HAVE_SIGACTION) && defined (SA_RESTART)
|
||||||
|
struct sigaction old_winch;
|
||||||
|
|
||||||
|
- memset (&old_winch, 0, sizeof (old_winch));
|
||||||
|
+ sigemptyset (&old_winch.sa_mask);
|
||||||
|
old_winch.sa_handler = &tui_sigwinch_handler;
|
||||||
|
+ old_winch.sa_flags = SA_RESTART;
|
||||||
|
sigaction (SIGWINCH, &old_winch, NULL);
|
||||||
|
#else
|
||||||
|
signal (SIGWINCH, &tui_sigwinch_handler);
|
Loading…
Reference in New Issue
Block a user