Hello community,

here is the log from the commit of package psmisc for openSUSE:Factory
checked in at Tue Oct 4 17:01:02 CEST 2011.



--------
--- openSUSE:Factory/psmisc/psmisc.changes      2011-09-28 15:31:10.000000000 
+0200
+++ /mounts/work_src_done/STABLE/psmisc/psmisc.changes  2011-10-03 
12:57:29.000000000 +0200
@@ -1,0 +2,5 @@
+Mon Oct  3 10:56:19 UTC 2011 - [email protected]
+
+- Fix segfault in pstree, patch by Tetsuo Handa (bnc#718915).
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


New:
----
  pstree-segfault.patch

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ psmisc.spec ++++++
--- /var/tmp/diff_new_pack.8uhi3i/_old  2011-10-04 17:00:58.000000000 +0200
+++ /var/tmp/diff_new_pack.8uhi3i/_new  2011-10-04 17:00:58.000000000 +0200
@@ -33,6 +33,7 @@
 Patch0:         %name-22.14.dif
 Patch1:         %name-22.12-tigetstr.patch
 Patch2:         %name-22.12-pstree.patch
+Patch3:         pstree-segfault.patch
 Patch42:        %name-22.14-22.15.patch
 Patch43:        %name-22.15-timeout.patch
 
@@ -54,6 +55,7 @@
 %patch1 -p0 -b .tigetstr
 %patch2 -p0 -b .pstree
 %patch0 -p0 -b .0
+%patch3 -p1
 
 %build
 autoreconf -fi

++++++ pstree-segfault.patch ++++++
From: Tetsuo Handa <[email protected]>

See bnc#718915#c1

---
 src/pstree.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- psmisc-22.14.orig/src/pstree.c
+++ psmisc-22.14/src/pstree.c
@@ -70,7 +70,7 @@ extern const char *__progname;
 #define        VT_HD        "w"
 
 typedef struct _proc {
-    char comm[COMM_LEN + 1];
+    char comm[COMM_LEN + 2 + 1];     /* add another 2 for thread brackets */
     char **argv;                /* only used : argv[0] is 1st arg; undef if 
argc < 1 */
     int argc;                        /* with -a   : number of arguments, -1 if 
swapped    */
     pid_t pid;
continue with "q"...



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to