Re: Little question around mach_debug interface

2006-12-17 Thread Thomas Schwinge
Hello Christian!

On Thu, Dec 14, 2006 at 06:42:21PM +0100, christian nastasi wrote:
 [...]

Please, in the future, post such questions to the bug-hurd@gnu.org
mailing list.  I also cced this email there.  You don't need to be
subscribed to post there.


 Is the mach_debug interface already built in in the gnumach kernel (because
 I don't think so)?
 I see there aren't  the header files for the mach_debug in the /usr/include,
 it is correct?

The interface itself seems to be compiled in (see `Makefrag.am':
``nodist_libkernel_a_SOURCES += [...] kern/mach_debug.server.c''), but
you are right that the C header files aren't installed into
`PREFIX/include/'.

 I could try to use them directly

Yes, that's what I'd suggest: just copy the C header files from `[GNU
Mach]/include/mach_debug/' somewhere locally and if you then can tell me
that they're in fact useful, I can of course change the GNU Mach build
system to install them alongside the other C header files.

 but i think it is not easy for me to build
 the mach_debug as an external lib, because I don't know how to make that
 work with the mach kernel.

You'll need to use `mig' to create client-side C stub files from the
`mach_debug/mach_debug.defs' file and then can use these in your
user-space code.


Again I want to note that I have no idea how much of the `mach_debug'
interface is properly implemented inside GNU Mach itself.  But you'll
notice if it'll work or not.  :-)


Regards,
 Thomas


signature.asc
Description: Digital signature
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd


Re: Maintaining Tool Chain

2006-12-17 Thread Thomas Schwinge
Hello Halil!

On Fri, Nov 24, 2006 at 03:20:06PM +0200, Halil Demirezen wrote:
 I want to apply for the Maintaining Tool Chain project. 

Please describe the experience you already have with the GNU tool chain
and which parts you would like to work on.


Regards,
 Thomas


signature.asc
Description: Digital signature
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd


Re: [bug #17647] glibc: GCC 4.1

2006-12-17 Thread Thomas Schwinge
Hello!

On Sun, Nov 26, 2006 at 11:27:58PM +0100, I wrote:
 [Building glibc with GCC 4.1.]
 
 And in fact also glibc-proper code is affected:
 
 #v+
 [EMAIL 
 PROTECTED]:/var/tmp/glibc-GCC4.1-without_Roland_patches/glibc-2.3.6.ds1/build-tree/hurd-i386-libc
  $ LD_LIBRARY_PATH=. gdb --args locale/localedef --help
 GNU gdb 6.5-debian
 [...]
 This GDB was configured as i486-gnu...
 (gdb) r
 Starting program: 
 /var/tmp/glibc-GCC4.1-without_Roland_patches/glibc-2.3.6.ds1/build-tree/hurd-i386-libc/locale/localedef
  --help
 Usage: localedef [OPTION...] NAME
   or:  localedef [OPTION...] [--add-to-archive|--delete-from-archive] FILE...
   or:  localedef [OPTION...] --list-archive [FILE]
 Compile locale specification
 
  Input Files:
   -f, --charmap=FILE Symbolic character names defined in FILE
   -i, --inputfile=FILE   Source definitions are found in FILE
 
 Program received signal SIGSEGV, Segmentation fault.
 0x011389a8 in __argp_fmtstream_update (fs=0x8098158) at argp-fmtstream.c:232
 232   while (p = buf  !isblank (*p))
 (gdb) print p
 $1 = 0x80981e9 values\n\n Input Files:\n  -f, e] FILE...\n, '\223' repeats 
 88 times, ???
 (gdb) print *p
 $2 = 118 'v'
 (gdb) bt
 #0  0x011389a8 in __argp_fmtstream_update (fs=0x8098158) at 
 argp-fmtstream.c:232
 #1  0x0113cc74 in _help (argp=0x1019ab0, state=0x1019ba4, stream=0x1188be0, 
 flags=value optimized out, name=0x101a05e localedef)
 at argp-fmtstream.h:255
 #2  0x0113d31e in __argp_state_help (state=0x1019ba4, stream=0x80981e9, 
 flags=634) at argp-help.c:1730
 #3  0x0113d7a8 in argp_default_parser (key=63, arg=0x0, state=0x1019ba4) at 
 argp-parse.c:119
 #4  0x0113d595 in group_parse (group=0x8097efc, state=0x1019ba4, key=63, 
 arg=0x0) at argp-parse.c:257
 #5  0x0113df93 in __argp_parse (argp=0x1019ab0, argc=2, argv=0x1019db4, 
 flags=0, end_index=0x1019d58, input=0x0) at argp-parse.c:755
 #6  0x0804a854 in main (argc=2, argv=0x1019db4) at programs/localedef.c:206
 #v-
 
 Any offhand guesses what's going on there?  I would expect nothing in the
 argp code to be Hurd specific and I'm not aware of any Linux system
 having such a problem.

I can add another bit of information here: pay attention to `LC_ALL'.

#v+
[EMAIL 
PROTECTED]:/var/tmp/glibc-GCC4.1-without_Roland_patches/glibc-2.3.6.ds1/build-tree/hurd-i386-libc
 $ LC_ALL=unknown LD_LIBRARY_PATH=. locale/localedef --help
Usage: localedef [OPTION...] NAME
  or:  localedef [OPTION...] [--add-to-archive|--delete-from-archive] FILE...
  or:  localedef [OPTION...] --list-archive [FILE]
Compile locale specification

 Input Files:
  -f, --charmap=FILE Symbolic character names defined in FILE
  -i, --inputfile=FILE   Source definitions are found in FILE
  -u, --repertoire-map=FILE  FILE contains mapping from symbolic names to UCS4
[...]
[EMAIL 
PROTECTED]:/var/tmp/glibc-GCC4.1-without_Roland_patches/glibc-2.3.6.ds1/build-tree/hurd-i386-libc
 $ LC_ALL=de_DE.UTF-8 LD_LIBRARY_PATH=. lo
cale/localedef --help
Aufruf: localedef [Option...] NAME
  oder:  localedef [Option...]
[--add-to-archive|--delete-from-archive] Datei...
  oder:  localedef [Option...] --list-archive [Datei]
Umwandeln der Lokale-Spezifikation

 Eingabedateien:
  -f, --charmap=FILE Symbolische Namen f??r Zeichen sind DATEI
 definiert
  -i, --inputfile=FILE   Die Quell-Definitionen stehen in DATEI
  -u, --repertoire-map=FILE  DATEI enth??lt Zuordnungen von symbolischen Namen
[...]
[EMAIL 
PROTECTED]:/var/tmp/glibc-GCC4.1-without_Roland_patches/glibc-2.3.6.ds1/build-tree/hurd-i386-libc
 $ LC_ALL=C LD_LIBRARY_PATH=. locale/localedef --help
Usage: localedef [OPTION...] NAME
  or:  localedef [OPTION...] [--add-to-archive|--delete-from-archive] FILE...
  or:  localedef [OPTION...] --list-archive [FILE]
Compile locale specification

 Input Files:
  -f, --charmap=FILE Symbolic character names defined in FILE
  -i, --inputfile=FILE   Source definitions are found in FILE
Segmentation fault
#v-

I.e. invalid values for `LC_ALL' work, as well as localized ones, only
the `C' one makes it segfault.  Due to the situation with glibc HEAD
being unbuildable at the moment, I can't test that.  Any ideas?


Regards,
 Thomas


signature.asc
Description: Digital signature
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd


Re: how test the mach_debug interface

2006-12-17 Thread Thomas Schwinge
Hello!

On Sun, Dec 17, 2006 at 04:15:18PM +0100, christian nastasi wrote:
 how can I proceed to test the mach_debug interface? What kind of test do you
 suggest me to verify it work properly in kernel? It seems that give some
 result, but since I didn' t find any documentation on this interface I want
 to know if somebody have an idea.

Sorry, I can't help any further.  I have myself never looked at or even
used that interface.


Regards,
 Thomas


signature.asc
Description: Digital signature
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd