[Bug general/4111] ftrace crash

["swagiaal at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From swagiaal at redhat dot com  2007-05-04 20:16 -------
This bug as been fix. It can be seen from the back trace that ftrace is trying
retrieve the syscall number during an exit event.

2007-05-04  Sami Wagiaalla  <swagiaal@redhat.com>
	
	* TestFtrace.java: New file.
	
	2007-05-04  Sami Wagiaalla  <swagiaal@redhat.com>
	
	* TestTaskSyscallObserver.java: Added a syscall cache.
	Replaced SyscallEventInfo.arg() with Syscall.getArguments().
	Replaced SyscallEventInfo.returnCode() with Syscall.getReturnCode().
	* SyscallEventInfo.java (arg): Removed.
	(returnCode): Removed.
	* Syscall.java: Changed all calls to SyscallEventInfo.args() to
	this.getArgument().
	Changed all calls to SyscallEventInfo.returnCode() to
	this.getReturnCode().
	* LinuxIa32Syscall.java: Changed second argument of write system call
	to a string.
	* LinuxX8664Syscall.java: Ditto.
	* LinuxPowerPCSyscall.java: Ditto.
	
	2007-05-04  Sami Wagiaalla  <swagiaal@redhat.com>
	
	* StracePrinter.java: Removed SyscallEventInfo argument.
	Removed when argument.
	Split the handle function into handleEnter and handleExit.
	* SyscallHandler.java: Ditto.
	* Ftrace.java: Added forkObserver for properly following forked
	children.
	Stoped use of Refresh for finding forked children.
	Added procObserver to newly added Procs.
	Added tasksObserver to procs executed by ftrace; fix for bz 2916.
	
	2007-05-04  Sami Wagiaalla  <swagiaal@redhat.com>
	
	* observers/SysCallUtilyInfo.java: Replaced use of
	SyscallEventInfo.arg() with Syscall.getArgument().
	Replaced use of SyscallEventInfo.returnCode() with
	Syscall.getReturnCode().

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


http://sourceware.org/bugzilla/show_bug.cgi?id=4111

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.