From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Mon, 22 Sep 2003 14:11:48 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 201 ************************************************** Sunday 21 September 2003 Number 201 ************************************************** Subjects for today 1 Re: Re: [Ux2bs] Innotek LIBC : Knut St. Osmundsen" 2 Samba : Bart van Leeuwen" **= Email 1 ==========================** Date: Mon, 22 Sep 2003 03:14:33 +0200 From: "Knut St. Osmundsen" Subject: Re: Re: [Ux2bs] Innotek LIBC Dave and Natalie wrote: > On Sat, 20 Sep 2003 22:04:12 +0200, Knut St. Osmundsen wrote: > > >>Not with 'no debugging'. With link386 we must drop back to an earlier >>level of debug info, HLL v3, which in some cases makes the debugger give >>up displaying sources (and all the rest) for some object files. > > > but what debugger do we use? One that understands HLL v4. For insance: -icsdebug (Visual Age for C++ v3) - idebug (Visual Age for C++ v3.6.5) - ICAT - idbug (Internal IBM debugger which can attach to processes and to on crash debugging.) - sd386 might work too depending on the linker you're using. I don't recall if sd386 reads HLL 4 or not. If does you can use ilink from VAC308 or link386 for the linking. If it doesn't you must use link386. (Note. ilink from VAC365 or ilink v5 produces HLL v6 which sd386 and icsdebug cannot read, but since non of you've got that linker yet, you won't run into that problem yet.) If anyone likes to use (pm)GDB, they'll have to fix it first. I don't know exactly what is broke now, but as I've said earlier it's propbably got something to do with emxbind changes. The other thing about GDB is that we've got an old port, GCC might be producing debuginfo it can't cope with. Kind Regards, knut **= Email 2 ==========================** Date: Mon, 22 Sep 2003 11:45:54 +0200 From: "Bart van Leeuwen" Subject: Samba Hi, did any dare to try to build samba 3.0 ? Bart