from:"Marcin Juszkiewicz via KDE Bugzilla"

[valgrind] [Bug 371439] Get coredump working on arm64

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371439

--- Comment #1 from Marcin Juszkiewicz  ---
Created attachment 101686
  --> https://bugs.kde.org/attachment.cgi?id=101686=edit
patch

 regs->pstate should probably do something with guest_CC_{OP/DEP1/DEP2/NDEP}
but no idea how

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371439] New: Get coredump working on arm64

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371439

Bug ID: 371439
   Summary: Get coredump working on arm64
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

VEX lacks code to dump registers so coredumps do not work. Or sth like that.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371411

Marcin Juszkiewicz  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371411

Marcin Juszkiewicz  changed:

   What|Removed |Added

 Attachment #101681|0   |1
is obsolete||

--- Comment #4 from Marcin Juszkiewicz  ---
Created attachment 101683
  --> https://bugs.kde.org/attachment.cgi?id=101683=edit
Handle (int flags) argument of fstatat64 on arm and ppc32

x86 and mips32 have wrappers which support all 4 arguments. So let arm and
ppc32 join them.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371411

Marcin Juszkiewicz  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Marcin Juszkiewicz  ---
should check first with build. stat structure differ per arch ;(

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371412] Rename wrap_sys_shmat to sys_shmat like other wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371412

--- Comment #1 from Marcin Juszkiewicz  ---
Created attachment 101682
  --> https://bugs.kde.org/attachment.cgi?id=101682=edit
patch

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371412] New: Rename wrap_sys_shmat to sys_shmat like other wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371412

Bug ID: 371412
   Summary: Rename wrap_sys_shmat to sys_shmat like other wrappers
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

All syscall wrappers are name sys_SYSCALLNAME except wrap_sys_shmat (and few
highly arch specific sys_syscall284 like ones).

I have a script to generate syscall table also for valgrind and this wrapper
name adds special case for no reason.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371411

Marcin Juszkiewicz  changed:

   What|Removed |Added

 Attachment #101680|0   |1
is obsolete||

--- Comment #2 from Marcin Juszkiewicz  ---
Created attachment 101681
  --> https://bugs.kde.org/attachment.cgi?id=101681=edit
move all *stat*64 to generic

this patch adds stat64 and lstat64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371411] Unify fstat64/fstatat64 wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371411

--- Comment #1 from Marcin Juszkiewicz  ---
Created attachment 101680
  --> https://bugs.kde.org/attachment.cgi?id=101680=edit
patch

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371411] New: Unify fstat64/fstatat64 wrappers

2016-10-21 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371411

Bug ID: 371411
   Summary: Unify fstat64/fstatat64 wrappers
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

arm/mips32/ppc32/x86 have similar wrappers for those two syscalls.

arm/mips32 ones do not handled 4th arguments (int flags) of syscall.

Not tested.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371227] Clean AArch64 syscall table

2016-10-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371227

--- Comment #2 from Marcin Juszkiewicz  ---
Created attachment 101646
  --> https://bugs.kde.org/attachment.cgi?id=101646=edit
patch which reformats table

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371227] Clean AArch64 syscall table

2016-10-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371227

--- Comment #1 from Marcin Juszkiewicz  ---
Created attachment 101645
  --> https://bugs.kde.org/attachment.cgi?id=101645=edit
patch which adds all entries

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371227] New: Clean AArch64 syscall table

2016-10-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371227

Bug ID: 371227
   Summary: Clean AArch64 syscall table
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

AArch64 (arm64) syscall table has some entries omitted and there is a commented
list of some not handled ones.

This patchset drops commented part, adds all missing entries into table as
commented out entries. LIN/PLA/GEN values are taken from other architectures
and can be wrong as this was not tested.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371225] Fix order of timer_{gettime,getoverrun,settime} syscalls on arm64

2016-10-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371225

--- Comment #1 from Marcin Juszkiewicz  ---
Created attachment 101644
  --> https://bugs.kde.org/attachment.cgi?id=101644=edit
patch

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 371225] New: Fix order of timer_{gettime,getoverrun,settime} syscalls on arm64

2016-10-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=371225

Bug ID: 371225
   Summary: Fix order of timer_{gettime,getoverrun,settime}
syscalls on arm64
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

Syscall table for arm64 has three entries put in wrong order. As they use
__NR_* defines values are proper. But comments have syscall numbers and those
are wrong.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369032] New: WARNING: unhandled amd64-linux syscall: 205 (set_thread_area)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369032

Bug ID: 369032
   Summary: WARNING: unhandled amd64-linux syscall: 205
(set_thread_area)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=set_thread_area01_valgrind_memory_leak_check stime=1474195515
cmdline=" valgrind -q --leak-check=full --trace-children=yes set_thread_area01"
contacts=""
analysis=exit
<<>>
--24891-- WARNING: unhandled amd64-linux syscall: 205
--24891-- You may be able to write your own handler.
--24891-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24891-- Nevertheless we consider this a bug.  Please report
--24891-- it at http://valgrind.org/support/bug_reports.html.
set_thread_area_011  TCONF  :  set_thread_area01.c:77: syscall(205)
tests[i].syscall not supported on your arch
set_thread_area_012  TCONF  :  set_thread_area01.c:77: Remaining cases not
appropriate for configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=63 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369029] New: WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369029

Bug ID: 369029
   Summary: WARNING: unhandled amd64-linux syscall: 315
(sched_getattr)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_getattr02_valgrind_memory_leak_check stime=1474195095
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_getattr02"
contacts=""
analysis=exit
<<>>
--24040-- WARNING: unhandled amd64-linux syscall: 315
--24040-- You may be able to write your own handler.
--24040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24040-- Nevertheless we consider this a bug.  Please report
--24040-- it at http://valgrind.org/support/bug_reports.html.
--24040-- WARNING: unhandled amd64-linux syscall: 315
--24040-- You may be able to write your own handler.
--24040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24040-- Nevertheless we consider this a bug.  Please report
--24040-- it at http://valgrind.org/support/bug_reports.html.
--24040-- WARNING: unhandled amd64-linux syscall: 315
--24040-- You may be able to write your own handler.
--24040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24040-- Nevertheless we consider this a bug.  Please report
--24040-- it at http://valgrind.org/support/bug_reports.html.
--24040-- WARNING: unhandled amd64-linux syscall: 315
--24040-- You may be able to write your own handler.
--24040-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24040-- Nevertheless we consider this a bug.  Please report
--24040-- it at http://valgrind.org/support/bug_reports.html.
sched_getattr021  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr022  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr023  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr024  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=68 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368925] WARNING: unhandled arm64-linux syscall: 130 (tkill)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368925

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 130|arm64-linux syscall: 130
   ||(tkill)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368913] WARNING: unhandled arm64-linux syscall: 117 (ptrace)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368913

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 117|arm64-linux syscall: 117
   ||(ptrace)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368914] WARNING: unhandled arm64-linux syscall: 142 (reboot)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368914

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 142|arm64-linux syscall: 142
   ||(reboot)

--- Comment #1 from Marcin Juszkiewicz  ---
https://bugs.kde.org/show_bug.cgi?id=369026 - same for amd64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368863] WARNING: unhandled arm64-linux syscall: 100 (get_robust_list)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368863

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 100|arm64-linux syscall: 100
   ||(get_robust_list)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368922] WARNING: unhandled arm64-linux syscall: 161 (sethostname)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368922

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 161|arm64-linux syscall: 161
   ||(sethostname)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368921] WARNING: unhandled arm64-linux syscall: 162 (setdomainname)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368921

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 162|arm64-linux syscall: 162
   ||(setdomainname)

--- Comment #1 from Marcin Juszkiewicz  ---
https://bugs.kde.org/show_bug.cgi?id=369030 - same for amd64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368917] WARNING: unhandled arm64-linux syscall: 218 (request_key)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368917

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 218|arm64-linux syscall: 218
   ||(request_key)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368864] WARNING: unhandled arm64-linux syscall: 262 (fanotify_init)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368864

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 262|arm64-linux syscall: 262
   ||(fanotify_init)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368866] WARNING: unhandled arm64-linux syscall: 238 (migrate_pages)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368866

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 238|arm64-linux syscall: 238
   ||(migrate_pages)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368916] WARNING: unhandled arm64-linux syscall: 234 (remap_file_pages)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368916

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 234|arm64-linux syscall: 234
   ||(remap_file_pages)

--- Comment #1 from Marcin Juszkiewicz  ---
https://bugs.kde.org/show_bug.cgi?id=369027 - same for amd64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368923] WARNING: unhandled arm64-linux syscall: 268 (setns)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368923

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 268|arm64-linux syscall: 268
   ||(setns)

--- Comment #1 from Marcin Juszkiewicz  ---
https://bugs.kde.org/show_bug.cgi?id=369031 - same for amd64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368865] WARNING: unhandled arm64-linux syscall: 272 (kcmp)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368865

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 272|arm64-linux syscall: 272
   ||(kcmp)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368919] WARNING: unhandled arm64-linux syscall: 274 (sched_setattr)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368919

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 274|arm64-linux syscall: 274
   ||(sched_setattr)

--- Comment #1 from Marcin Juszkiewicz  ---
https://bugs.kde.org/show_bug.cgi?id=369028 - same for amd64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368920] WARNING: unhandled arm64-linux syscall: 275 (sched_getattr)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368920

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 275|arm64-linux syscall: 275
   ||(sched_getattr)

--- Comment #1 from Marcin Juszkiewicz  ---
https://bugs.kde.org/show_bug.cgi?id=369029 is same for amd64

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368924] WARNING: unhandled arm64-linux syscall: 84 (sync_file_range)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368924

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 84 |arm64-linux syscall: 84
   ||(sync_file_range)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368926] WARNING: unhandled arm64-linux syscall: 97 (unshare)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368926

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |arm64-linux syscall: 97 |arm64-linux syscall: 97
   ||(unshare)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369026] WARNING: unhandled amd64-linux syscall: 169 (reboot)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369026

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |amd64-linux syscall: 169|amd64-linux syscall: 169
   ||(reboot)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368960] WARNING: unhandled amd64-linux syscall: 163 (acct)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368960

Marcin Juszkiewicz  changed:

   What|Removed |Added

Summary|WARNING: unhandled  |WARNING: unhandled
   |amd64-linux syscall: 163|amd64-linux syscall: 163
   ||(acct)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369034] New: WARNING: unhandled amd64-linux syscall: 136 (ustat)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369034

Bug ID: 369034
   Summary: WARNING: unhandled amd64-linux syscall: 136 (ustat)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=ustat01_valgrind_memory_leak_check stime=1474227085
cmdline=" valgrind -q --leak-check=full --trace-children=yes ustat01"
contacts=""
analysis=exit
<<>>
--28865-- WARNING: unhandled amd64-linux syscall: 136
--28865-- You may be able to write your own handler.
--28865-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--28865-- Nevertheless we consider this a bug.  Please report
--28865-- it at http://valgrind.org/support/bug_reports.html.
ustat01 1  TCONF  :  ustat01.c:54: ustat not supported
ustat01 2  TCONF  :  ustat01.c:54: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=60 cstime=1
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369033] New: WARNING: unhandled amd64-linux syscall: 139 (sysfs)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369033

Bug ID: 369033
   Summary: WARNING: unhandled amd64-linux syscall: 139 (sysfs)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sysfs01_valgrind_memory_leak_check stime=1474225812
cmdline=" valgrind -q --leak-check=full --trace-children=yes sysfs01"
contacts=""
analysis=exit
<<>>
--26537-- WARNING: unhandled amd64-linux syscall: 139
--26537-- You may be able to write your own handler.
--26537-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26537-- Nevertheless we consider this a bug.  Please report
--26537-- it at http://valgrind.org/support/bug_reports.html.
sysfs01 1  TCONF  :  sysfs01.c:94: syscall(139) __NR_sysfs not supported on
your arch
sysfs01 2  TCONF  :  sysfs01.c:94: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=61 cstime=1
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369031] New: WARNING: unhandled amd64-linux syscall: 308 (setns)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369031

Bug ID: 369031
   Summary: WARNING: unhandled amd64-linux syscall: 308 (setns)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=setns01_valgrind_memory_leak_check stime=1474195406
cmdline=" valgrind -q --leak-check=full --trace-children=yes setns01"
contacts=""
analysis=exit
<<>>
--24584-- WARNING: unhandled amd64-linux syscall: 308
--24584-- You may be able to write your own handler.
--24584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24584-- Nevertheless we consider this a bug.  Please report
--24584-- it at http://valgrind.org/support/bug_reports.html.
setns01 1  TCONF  :  setns01.c:209: syscall(308) __NR_setns not supported
on your arch
setns01 2  TCONF  :  setns01.c:209: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=60 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369030] New: WARNING: unhandled amd64-linux syscall: 171 (setdomainname)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369030

Bug ID: 369030
   Summary: WARNING: unhandled amd64-linux syscall: 171
(setdomainname)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=setdomainname01_valgrind_memory_leak_check stime=1474195205
cmdline=" valgrind -q --leak-check=full --trace-children=yes setdomainname01"
contacts=""
analysis=exit
<<>>
--24445-- WARNING: unhandled amd64-linux syscall: 171
--24445-- You may be able to write your own handler.
--24445-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24445-- Nevertheless we consider this a bug.  Please report
--24445-- it at http://valgrind.org/support/bug_reports.html.
--24445-- WARNING: unhandled amd64-linux syscall: 171
--24445-- You may be able to write your own handler.
--24445-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24445-- Nevertheless we consider this a bug.  Please report
--24445-- it at http://valgrind.org/support/bug_reports.html.
setdomainname011  TFAIL  :  setdomainname01.c:104: setdomainname() Failed,
errno = 38 : Function not implemented
setdomainname010  TWARN  :  setdomainname01.c:146: setdomainname() failed
while restoring domainname to "(none)"
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=5 corefile=no
cutime=60 cstime=1
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369028] New: WARNING: unhandled amd64-linux syscall: 314 (sched_setattr)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369028

Bug ID: 369028
   Summary: WARNING: unhandled amd64-linux syscall: 314
(sched_setattr)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_setattr01_valgrind_memory_leak_check stime=1474195092
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_setattr01"
contacts=""
analysis=exit
<<>>
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
sched_setattr011  TFAIL  :  sched_setattr01.c:96: sched_setattr(0,attr,0)
returned: -1 expected: 0: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr012  TFAIL  :  sched_setattr01.c:109:
sched_setattr(32768,attr,0): expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38):
Function not implemented
sched_setattr013  TFAIL  :  sched_setattr01.c:109: sched_setattr(0,attr,0):
expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr014  TFAIL  :  sched_setattr01.c:109:
sched_setattr(0,attr,1000): expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38):
Function not implemented
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=74 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 369027] New: WARNING: unhandled amd64-linux syscall: 216 (remap_file_pages)

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369027

Bug ID: 369027
   Summary: WARNING: unhandled amd64-linux syscall: 216
(remap_file_pages)
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=remap_file_pages01_valgrind_memory_leak_check stime=1474194855
cmdline=" valgrind -q --leak-check=full --trace-children=yes
remap_file_pages01"
contacts=""
analysis=exit
<<>>
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
--23752-- WARNING: unhandled amd64-linux syscall: 216
--23752-- You may be able to write your own handler.
--23752-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23752-- Nevertheless we consider this a bug.  Please report
--23752-- it at http://valgrind.org/support/bug_reports.html.
==23752== Invalid read of size 1
==23752==at 0x402BC5: test_nonlinear (remap_file_pages01.c:194)
==23752==by 0x4027B7: main (remap_file_pages01.c:133)
==23752==  Address 0x4800 is not stack'd, malloc'd or (recently) free'd
==23752== 
remap_file_pages011  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4800, page_sz=8192, window_pages=14: errno=ENOSYS(38):
Function not implemented
remap_file_pages012  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x48002000, page_sz=8192, window_pages=12: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed:
unlink(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed; errno=2: No such file or
directory
remap_file_pages013  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x48004000, page_sz=8192, window_pages=10: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed:
unlink(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed; errno=2: No such file or
directory
remap_file_pages014  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x48006000, page_sz=8192, window_pages=8: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed:
unlink(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed; errno=2: No such file or
directory
remap_file_pages015  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x48008000, page_sz=8192, window_pages=6: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed:
unlink(/tmp/ltp-QOz7BwMisJ/remV18dD9) failed; errno=2: No such file or
directory
remap_file_pages016  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4800a000, page_sz=8192, window_pages=4:

[valgrind] [Bug 369026] New: WARNING: unhandled amd64-linux syscall: 169

2016-09-19 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=369026

Bug ID: 369026
   Summary: WARNING: unhandled amd64-linux syscall: 169
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=reboot01_valgrind_memory_leak_check stime=1474194666
cmdline=" valgrind -q --leak-check=full --trace-children=yes reboot01"
contacts=""
analysis=exit
<<>>
--23663-- WARNING: unhandled amd64-linux syscall: 169
--23663-- You may be able to write your own handler.
--23663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23663-- Nevertheless we consider this a bug.  Please report
--23663-- it at http://valgrind.org/support/bug_reports.html.
--23663-- WARNING: unhandled amd64-linux syscall: 169
--23663-- You may be able to write your own handler.
--23663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23663-- Nevertheless we consider this a bug.  Please report
--23663-- it at http://valgrind.org/support/bug_reports.html.
reboot011  TFAIL  :  reboot01.c:109: reboot(2) Failed for option
LINUX_REBOOT_CMD_CAD_ON
reboot012  TFAIL  :  reboot01.c:109: reboot(2) Failed for option
LINUX_REBOOT_CMD_CAD_OFF
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=60 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368960] New: WARNING: unhandled amd64-linux syscall: 163

2016-09-17 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368960

Bug ID: 368960
   Summary: WARNING: unhandled amd64-linux syscall: 163
   Product: valgrind
   Version: 3.11.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=acct01_valgrind_memory_leak_check stime=1474126660
cmdline=" valgrind -q --leak-check=full --trace-children=yes acct01"
contacts=""
analysis=exit
<<>>
--10205-- WARNING: unhandled amd64-linux syscall: 163
--10205-- You may be able to write your own handler.
--10205-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--10205-- Nevertheless we consider this a bug.  Please report
--10205-- it at http://valgrind.org/support/bug_reports.html.
acct01  1  TCONF  :  acct01.c:112: BSD process accounting is not configured
in this kernel
acct01  2  TCONF  :  acct01.c:112: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=24 cstime=0
<<>>

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368925] New: WARNING: unhandled arm64-linux syscall: 130

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368925

Bug ID: 368925
   Summary: WARNING: unhandled arm64-linux syscall: 130
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=tkill01_valgrind_memory_leak_check stime=1473976160
cmdline=" valgrind -q --leak-check=full --trace-children=yes tkill01"
contacts=""
analysis=exit
<<>>
--30021-- WARNING: unhandled arm64-linux syscall: 130
--30021-- You may be able to write your own handler.
--30021-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--30021-- Nevertheless we consider this a bug.  Please report
--30021-- it at http://valgrind.org/support/bug_reports.html.
tkill01 1  TCONF  :  tkill01.c:96: syscall(130) __NR_tkill not supported on
your arch
tkill01 2  TCONF  :  tkill01.c:96: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=46 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368926] New: WARNING: unhandled arm64-linux syscall: 97

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368926

Bug ID: 368926
   Summary: WARNING: unhandled arm64-linux syscall: 97
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=unshare01_valgrind_memory_leak_check stime=1473976179
cmdline=" valgrind -q --leak-check=full --trace-children=yes unshare01"
contacts=""
analysis=exit
<<>>
--30118-- WARNING: unhandled arm64-linux syscall: 97
--30118-- You may be able to write your own handler.
--30118-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--30118-- Nevertheless we consider this a bug.  Please report
--30118-- it at http://valgrind.org/support/bug_reports.html.
unshare011  TCONF  :  unshare01.c:198: unshare not supported in kernel
unshare012  TCONF  :  unshare01.c:198: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=51 cstime=3
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368924] New: WARNING: unhandled arm64-linux syscall: 84

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368924

Bug ID: 368924
   Summary: WARNING: unhandled arm64-linux syscall: 84
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sync_file_range01_valgrind_memory_leak_check stime=1473975067
cmdline=" valgrind -q --leak-check=full --trace-children=yes sync_file_range01"
contacts=""
analysis=exit
<<>>
--27072-- WARNING: unhandled arm64-linux syscall: 84
--27072-- You may be able to write your own handler.
--27072-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--27072-- Nevertheless we consider this a bug.  Please report
--27072-- it at http://valgrind.org/support/bug_reports.html.
sync_file_range011  TCONF  :  sync_file_range01.c:221: syscall(84)
__NR_sync_file_range not supported on your arch
sync_file_range012  TCONF  :  sync_file_range01.c:221: Remaining cases not
appropriate for configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=46 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368923] New: WARNING: unhandled arm64-linux syscall: 268

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368923

Bug ID: 368923
   Summary: WARNING: unhandled arm64-linux syscall: 268
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=setns01_valgrind_memory_leak_check stime=1473974802
cmdline=" valgrind -q --leak-check=full --trace-children=yes setns01"
contacts=""
analysis=exit
<<>>
--26151-- WARNING: unhandled arm64-linux syscall: 268
--26151-- You may be able to write your own handler.
--26151-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26151-- Nevertheless we consider this a bug.  Please report
--26151-- it at http://valgrind.org/support/bug_reports.html.
setns01 1  TCONF  :  setns01.c:209: syscall(268) __NR_setns not supported
on your arch
setns01 2  TCONF  :  setns01.c:209: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=61 cstime=2
<<>>
<<>>
tag=setns01_valgrind_thread_concurrency_check stime=1473974803
cmdline=" valgrind -q --tool=helgrind --trace-children=yes setns01"
contacts=""
analysis=exit
<<>>
--26158-- WARNING: unhandled arm64-linux syscall: 268
--26158-- You may be able to write your own handler.
--26158-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26158-- Nevertheless we consider this a bug.  Please report
--26158-- it at http://valgrind.org/support/bug_reports.html.
setns01 1  TCONF  :  setns01.c:209: syscall(268) __NR_setns not supported
on your arch
setns01 2  TCONF  :  setns01.c:209: Remaining cases not appropriate for
configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=35 cstime=3
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368922] New: WARNING: unhandled arm64-linux syscall: 161

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368922

Bug ID: 368922
   Summary: WARNING: unhandled arm64-linux syscall: 161
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sethostname01_valgrind_memory_leak_check stime=1473974797
cmdline=" valgrind -q --leak-check=full --trace-children=yes sethostname01"
contacts=""
analysis=exit
<<>>
--26133-- WARNING: unhandled arm64-linux syscall: 161
--26133-- You may be able to write your own handler.
--26133-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26133-- Nevertheless we consider this a bug.  Please report
--26133-- it at http://valgrind.org/support/bug_reports.html.
--26133-- WARNING: unhandled arm64-linux syscall: 161
--26133-- You may be able to write your own handler.
--26133-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26133-- Nevertheless we consider this a bug.  Please report
--26133-- it at http://valgrind.org/support/bug_reports.html.
sethostname011  TFAIL  :  sethostname01.c:105: sethostname() failed ,
errno=38 : Function not implemented
sethostname010  TWARN  :  sethostname01.c:152: sethostname() failed while
restoring hostname to "pinkiepie.local": Function not implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=5 corefile=no
cutime=45 cstime=1
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368916] New: WARNING: unhandled arm64-linux syscall: 234

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368916

Bug ID: 368916
   Summary: WARNING: unhandled arm64-linux syscall: 234
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=remap_file_pages01_valgrind_memory_leak_check stime=1473974430
cmdline=" valgrind -q --leak-check=full --trace-children=yes
remap_file_pages01"
contacts=""
analysis=exit
<<>>
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
--25011-- WARNING: unhandled arm64-linux syscall: 234
--25011-- You may be able to write your own handler.
--25011-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25011-- Nevertheless we consider this a bug.  Please report
--25011-- it at http://valgrind.org/support/bug_reports.html.
==25011== Invalid read of size 1
==25011==at 0x403020: test_nonlinear (remap_file_pages01.c:203)
==25011==by 0x402B77: main (remap_file_pages01.c:133)
==25011==  Address 0x4800 is not stack'd, malloc'd or (recently) free'd
==25011== 
remap_file_pages011  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4800, page_sz=131072, window_pages=14: errno=ENOSYS(38):
Function not implemented
remap_file_pages012  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4802, page_sz=131072, window_pages=12: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages013  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4804, page_sz=131072, window_pages=10: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages014  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4806, page_sz=131072, window_pages=8: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages015  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x4808, page_sz=131072, window_pages=6: errno=ENOSYS(38):
Function not implemented
remap_file_pages010  TWARN  :  tst_tmpdir.c:213: tst_rmdir:
rmobj(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed:
unlink(/tmp/ltp-PmGOOBcgbn/rem3reF42) failed; errno=2: No such file or
directory
remap_file_pages016  TFAIL  :  remap_file_pages01.c:184: remap_file_pages
error for page=0x480a, page_sz=131072, window_pages=4: errno=ENOSYS(38):
Function

[valgrind] [Bug 368921] New: WARNING: unhandled arm64-linux syscall: 162

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368921

Bug ID: 368921
   Summary: WARNING: unhandled arm64-linux syscall: 162
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=setdomainname01_valgrind_memory_leak_check stime=1473974763
cmdline=" valgrind -q --leak-check=full --trace-children=yes setdomainname01"
contacts=""
analysis=exit
<<>>
--26022-- WARNING: unhandled arm64-linux syscall: 162
--26022-- You may be able to write your own handler.
--26022-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26022-- Nevertheless we consider this a bug.  Please report
--26022-- it at http://valgrind.org/support/bug_reports.html.
--26022-- WARNING: unhandled arm64-linux syscall: 162
--26022-- You may be able to write your own handler.
--26022-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26022-- Nevertheless we consider this a bug.  Please report
--26022-- it at http://valgrind.org/support/bug_reports.html.
setdomainname011  TFAIL  :  setdomainname01.c:104: setdomainname() Failed,
errno = 38 : Function not implemented
setdomainname010  TWARN  :  setdomainname01.c:146: setdomainname() failed
while restoring domainname to "(none)"
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=5 corefile=no
cutime=54 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368920] New: WARNING: unhandled arm64-linux syscall: 275

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368920

Bug ID: 368920
   Summary: WARNING: unhandled arm64-linux syscall: 275
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_getattr02_valgrind_memory_leak_check stime=1473974664
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_getattr02"
contacts=""
analysis=exit
<<>>
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
--25462-- WARNING: unhandled arm64-linux syscall: 275
--25462-- You may be able to write your own handler.
--25462-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25462-- Nevertheless we consider this a bug.  Please report
--25462-- it at http://valgrind.org/support/bug_reports.html.
sched_getattr021  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr022  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr023  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
sched_getattr024  TFAIL  :  sched_getattr02.c:83: sched_getattr() failed
unexpectedly : expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not
implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=52 cstime=1
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368919] New: WARNING: unhandled arm64-linux syscall: 274

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368919

Bug ID: 368919
   Summary: WARNING: unhandled arm64-linux syscall: 274
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_setattr01_valgrind_memory_leak_check stime=1473974662
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_setattr01"
contacts=""
analysis=exit
<<>>
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
--25451-- WARNING: unhandled arm64-linux syscall: 274
--25451-- You may be able to write your own handler.
--25451-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25451-- Nevertheless we consider this a bug.  Please report
--25451-- it at http://valgrind.org/support/bug_reports.html.
sched_setattr011  TFAIL  :  sched_setattr01.c:96: sched_setattr(0,attr,0)
returned: -1 expected: 0: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr012  TFAIL  :  sched_setattr01.c:109:
sched_setattr(32768,attr,0): expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38):
Function not implemented
sched_setattr013  TFAIL  :  sched_setattr01.c:109: sched_setattr(0,attr,0):
expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr014  TFAIL  :  sched_setattr01.c:109:
sched_setattr(0,attr,1000): expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38):
Function not implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=54 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368918] New: WARNING: unhandled arm64-linux syscall: 127

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368918

Bug ID: 368918
   Summary: WARNING: unhandled arm64-linux syscall: 127
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=sched_rr_get_interval01_valgrind_memory_leak_check stime=1473974647
cmdline=" valgrind -q --leak-check=full --trace-children=yes
sched_rr_get_interval01"
contacts=""
analysis=exit
<<>>
--25352-- WARNING: unhandled arm64-linux syscall: 127
--25352-- You may be able to write your own handler.
--25352-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25352-- Nevertheless we consider this a bug.  Please report
--25352-- it at http://valgrind.org/support/bug_reports.html.
sched_rr_get_interval011  TFAIL  :  sched_rr_get_interval01.c:105: Test
Failed, sched_rr_get_interval()returned -1: TEST_ERRNO=ENOSYS(38): Function not
implemented
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=45 cstime=1
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368917] New: WARNING: unhandled arm64-linux syscall: 218

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368917

Bug ID: 368917
   Summary: WARNING: unhandled arm64-linux syscall: 218
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=request_key01_valgrind_memory_leak_check stime=1473974601
cmdline=" valgrind -q --leak-check=full --trace-children=yes request_key01"
contacts=""
analysis=exit
<<>>
tst_test.c:756: INFO: Timeout per run is 0h 05m 00s
--25192-- WARNING: unhandled arm64-linux syscall: 218
--25192-- You may be able to write your own handler.
--25192-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--25192-- Nevertheless we consider this a bug.  Please report
--25192-- it at http://valgrind.org/support/bug_reports.html.
request_key01.c:46: FAIL: request_key() failed: ENOSYS

Summary:
passed   0
failed   1
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=51 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368914] New: WARNING: unhandled arm64-linux syscall: 142

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368914

Bug ID: 368914
   Summary: WARNING: unhandled arm64-linux syscall: 142
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=reboot01_valgrind_memory_leak_check stime=1473973971
cmdline=" valgrind -q --leak-check=full --trace-children=yes reboot01"
contacts=""
analysis=exit
<<>>
--24614-- WARNING: unhandled arm64-linux syscall: 142
--24614-- You may be able to write your own handler.
--24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24614-- Nevertheless we consider this a bug.  Please report
--24614-- it at http://valgrind.org/support/bug_reports.html.
--24614-- WARNING: unhandled arm64-linux syscall: 142
--24614-- You may be able to write your own handler.
--24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24614-- Nevertheless we consider this a bug.  Please report
--24614-- it at http://valgrind.org/support/bug_reports.html.
reboot011  TFAIL  :  reboot01.c:109: reboot(2) Failed for option
LINUX_REBOOT_CMD_CAD_ON
reboot012  TFAIL  :  reboot01.c:109: reboot(2) Failed for option
LINUX_REBOOT_CMD_CAD_OFF
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=44 cstime=2
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368913] New: WARNING: unhandled arm64-linux syscall: 117

2016-09-16 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368913

Bug ID: 368913
   Summary: WARNING: unhandled arm64-linux syscall: 117
   Product: valgrind
   Version: 3.11.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=ptrace01_valgrind_memory_leak_check stime=1473972958
cmdline=" valgrind -q --leak-check=full --trace-children=yes ptrace01"
contacts=""
analysis=exit
<<>>
--23224-- WARNING: unhandled arm64-linux syscall: 117
--23224-- You may be able to write your own handler.
--23224-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23224-- Nevertheless we consider this a bug.  Please report
--23224-- it at http://valgrind.org/support/bug_reports.html.
ptrace010  TWARN  :  ptrace01.c:237: ptrace() failed in child
ptrace011  TFAIL  :  ptrace01.c:182: Test Failed
--23225-- WARNING: unhandled arm64-linux syscall: 117
--23225-- You may be able to write your own handler.
--23225-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23225-- Nevertheless we consider this a bug.  Please report
--23225-- it at http://valgrind.org/support/bug_reports.html.
ptrace010  TWARN  :  ptrace01.c:237: ptrace() failed in child
ptrace012  TFAIL  :  ptrace01.c:182: Test Failed
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=58 cstime=3
<<>>


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368866] New: WARNING: unhandled arm64-linux syscall: 238

2016-09-15 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368866

Bug ID: 368866
   Summary: WARNING: unhandled arm64-linux syscall: 238
   Product: valgrind
   Version: 3.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=migrate_pages01_valgrind_memory_leak_check stime=1473956002
cmdline=" valgrind -q --leak-check=full --trace-children=yes migrate_pages01"
contacts=""
analysis=exit
<<>>
--11538-- WARNING: unhandled arm64-linux syscall: 238
--11538-- You may be able to write your own handler.
--11538-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--11538-- Nevertheless we consider this a bug.  Please report
--11538-- it at http://valgrind.org/support/bug_reports.html.
migrate_pages011  TCONF  :  migrate_pages01.c:227: syscall(238)
__NR_migrate_pages not supported on your arch
migrate_pages012  TCONF  :  migrate_pages01.c:227: Remaining cases not
appropriate for configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=51 cstime=2
<<>>


Reproducible: Always

Steps to Reproduce:
1. runltp -M3
2.
3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368865] New: WARNING: unhandled arm64-linux syscall: 272

2016-09-15 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368865

Bug ID: 368865
   Summary: WARNING: unhandled arm64-linux syscall: 272
   Product: valgrind
   Version: 3.11.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=kcmp01_valgrind_memory_leak_check stime=1473954056
cmdline=" valgrind -q --leak-check=full --trace-children=yes kcmp01"
contacts=""
analysis=exit
<<>>
tst_test.c:756: INFO: Timeout per run is 0h 05m 00s
--4087-- WARNING: unhandled arm64-linux syscall: 272
--4087-- You may be able to write your own handler.
--4087-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--4087-- Nevertheless we consider this a bug.  Please report
--4087-- it at http://valgrind.org/support/bug_reports.html.
kcmp.h:49: CONF: syscall(272) __NR_kcmpnot supported
tst_test.c:284: CONF: Reported by child (4087)

Summary:
passed   0
failed   0
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=59 cstime=3
<<>>


Reproducible: Always

Steps to Reproduce:
1. runltp -M3
2.
3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368864] New: WARNING: unhandled arm64-linux syscall: 262

2016-09-15 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368864

Bug ID: 368864
   Summary: WARNING: unhandled arm64-linux syscall: 262
   Product: valgrind
   Version: 3.11.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

<<>>
tag=fanotify01_valgrind_memory_leak_check stime=1473954036
cmdline=" valgrind -q --leak-check=full --trace-children=yes fanotify01"
contacts=""
analysis=exit
<<>>
--3974-- WARNING: unhandled arm64-linux syscall: 262
--3974-- You may be able to write your own handler.
--3974-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--3974-- Nevertheless we consider this a bug.  Please report
--3974-- it at http://valgrind.org/support/bug_reports.html.
fanotify011  TCONF  :  fanotify01.c:348: fanotify is not configured in this
kernel.
fanotify012  TCONF  :  fanotify01.c:348: Remaining cases not appropriate
for configuration
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=32 corefile=no
cutime=48 cstime=1
<<>>


Reproducible: Always

Steps to Reproduce:
1. runltp -M3

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 368863] New: WARNING: unhandled arm64-linux syscall: 100

2016-09-15 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=368863

Bug ID: 368863
   Summary: WARNING: unhandled arm64-linux syscall: 100
   Product: valgrind
   Version: 3.11.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

During run of LTP with valgrind:

<<>>
tag=get_robust_list01_valgrind_memory_leak_check stime=1473953400
cmdline=" valgrind -q --leak-check=full --trace-children=yes get_robust_list01"
contacts=""
analysis=exit
<<>>
--1850-- WARNING: unhandled arm64-linux syscall: 100
--1850-- You may be able to write your own handler.
--1850-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--1850-- Nevertheless we consider this a bug.  Please report
--1850-- it at http://valgrind.org/support/bug_reports.html.
get_robust_list011  TCONF  :  get_robust_list01.c:98: syscall(100)
__NR_get_robust_list not supported on your arch
get_robust_list012  TCONF  :  get_robust_list01.c:98: Remaining cases not
appropriate for configuration
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=48 cstime=2
<<>>


Reproducible: Always

Steps to Reproduce:
1. runltp -M3

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

2016-09-14 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359503

Marcin Juszkiewicz  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|FIXED   |---

--- Comment #11 from Marcin Juszkiewicz  ---
tag=adjtimex01_valgrind_memory_leak_check stime=1473840632
cmdline=" valgrind -q --leak-check=full --trace-children=yes adjtimex01"
contacts=""
analysis=exit
<<>>
--7168-- WARNING: unhandled arm64-linux syscall: 171
--7168-- You may be able to write your own handler.
--7168-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--7168-- Nevertheless we consider this a bug.  Please report
--7168-- it at http://valgrind.org/support/bug_reports.html.
adjtimex011  TBROK  :  adjtimex01.c:107: failed to save current parameters:
errno=ENOSYS(38): Function not implemented
adjtimex012  TBROK  :  adjtimex01.c:107: Remaining cases broken

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

2016-03-04 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359503

Marcin Juszkiewicz  changed:

   What|Removed |Added

  Attachment #97263|0   |1
is obsolete||

--- Comment #5 from Marcin Juszkiewicz  ---
Created attachment 97685
  --> https://bugs.kde.org/attachment.cgi?id=97685=edit
add all missing syscalls for aarch64 - rebased to svn HEAD, fixed, build tested

Mark Wielaard pointed that previous patch does not build. Checked, fixed few
syscall names, disabled few.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 359757] New: Back button does not go "directory up" in browsing mode

2016-02-24 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359757

Bug ID: 359757
   Summary: Back button does not go "directory up" in browsing
mode
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: mar...@juszkiewicz.com.pl
CC: myr...@kde.org

org.kde.gwenview 15.12.2

I launched Gwenview to search for some photos in my collection - used browse
dirs mode for it. But pressing "Back" key on mouse or on keyboard does not go
directory up like it is in Dolphin. 

I can setup keyboard one in prefs but no way to enable mouse button for it.

Reproducible: Always

Steps to Reproduce:
1. launch gwenview
2. browse dirs
3. press Back mouse button

Actual Results:  
nothing happens

Expected Results:  
directory up is displayed

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

2016-02-17 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359503

Marcin Juszkiewicz  changed:

   What|Removed |Added

  Attachment #97262|0   |1
is obsolete||

--- Comment #2 from Marcin Juszkiewicz  ---
Created attachment 97263
  --> https://bugs.kde.org/attachment.cgi?id=97263=edit
add all missing syscalls for aarch64 - rebased to svn HEAD

Ops, previous version was done against older valgrind tree...

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 356676] Unhandled arm64-linux syscalls: 125 and 126 (sched_get_priority_max/min)

2016-02-17 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=356676

Marcin Juszkiewicz  changed:

   What|Removed |Added

 CC||mar...@juszkiewicz.com.pl

--- Comment #1 from Marcin Juszkiewicz  ---
patch from https://bugs.kde.org/show_bug.cgi?id=359503 handles it

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 356678] unhandled arm64-linux syscall: 232 (mincore)

2016-02-17 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=356678

Marcin Juszkiewicz  changed:

   What|Removed |Added

 CC||mar...@juszkiewicz.com.pl

--- Comment #1 from Marcin Juszkiewicz  ---
patch from https://bugs.kde.org/show_bug.cgi?id=359503 handles it

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 359503] Add missing syscalls for aarch64 (arm64)

2016-02-17 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359503

--- Comment #1 from Marcin Juszkiewicz  ---
Created attachment 97262
  --> https://bugs.kde.org/attachment.cgi?id=97262=edit
Add all aarch64 syscalls

This patch adds all syscalls. LINX_/LINXY etc was based on commented versions
and on amd64-linux ones.

Not built yet with this code.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 359503] New: Add missing syscalls for aarch64 (arm64)

2016-02-17 Thread Marcin Juszkiewicz via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=359503

Bug ID: 359503
   Summary: Add missing syscalls for aarch64 (arm64)
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: mar...@juszkiewicz.com.pl

There is a huge amount of syscalls not handled on AArch64 architecture.

https://bugs.kde.org/show_bug.cgi?id=356678 wants one,
https://bugs.kde.org/show_bug.cgi?id=356676 wants another.

I wanted another ones. So instead of adding few I decided to add all of them.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

68 matches

Mail list logo