From c4ad3f73033c7e0511c3e7df961e1232cc503478 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 26 Feb 2014 12:32:06 +0100 Subject: IRC. --- .../mach/gnumach/interface/syscall/mach_print.mdwn | 32 +++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) (limited to 'microkernel/mach/gnumach/interface/syscall/mach_print.mdwn') diff --git a/microkernel/mach/gnumach/interface/syscall/mach_print.mdwn b/microkernel/mach/gnumach/interface/syscall/mach_print.mdwn index a169e92e..d03c9674 100644 --- a/microkernel/mach/gnumach/interface/syscall/mach_print.mdwn +++ b/microkernel/mach/gnumach/interface/syscall/mach_print.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -88,3 +88,33 @@ License|/fdl]]."]]"""]] the caller's address space without going through a special copy-from-user function not very portable + + +## IRC, freenode, #hurd, 2013-11-25 + + can we get the mach_printf function somewhere so that it's + easier to use please ? + well + i'm not comfortable with that + y not ? + i don't consider mach_print being part of the interface yet + ... + it's really a debugging call + not always available + so what, let it fail if it is not + ok + i should change it first + pass a size argument + and do a proper copyin + cool, thanks :) + then we could add that printf function in libshouldbeinlibc i + guess + that'd be nice, yes + hm + that would make only hurd servers able to use it though + unless we preload it + well, i thought it's a staging area for libc ? + in theory yes, in practice some functions have been stuck there + for ages + we'll discuss that with youpi and tschwinge + and pinotree -- cgit v1.2.3