From owner-freebsd-questions Fri Mar 8 5:39:15 2002 Delivered-To: freebsd-questions@freebsd.org Received: from oxe.cs.umu.se (oxe.cs.umu.se [130.239.40.14]) by hub.freebsd.org (Postfix) with ESMTP id EAE1E37B402 for ; Fri, 8 Mar 2002 05:39:08 -0800 (PST) Received: from bark (rfc1413 says tdv94ped@bark.cs.umu.se [130.239.40.185]) by oxe.cs.umu.se (8.8.8/8.8.8) with ESMTP id OAA27816; Fri, 8 Mar 2002 14:39:02 +0100 (MET) Date: Fri, 8 Mar 2002 14:39:02 +0100 (MET) From: Paul Everlund To: Mike Dewhirst Cc: Subject: RE: c-shell scripts In-Reply-To: <0B0368CED76DD4118E1200D0B73E9B5D041E9F27@MAIL1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > the last 10 lines... > > The docs say that we should use C shell scripts to write extension modules, > but these don't look like it, do they? I'm guessing they're not c shell > scripts at all, but rather compiled binaries. > > If somebody could suggest a decompiler (yes Jan, I'm prepared for the hard > to understand results, but something is _always_ better than nothing :) ) I > would be very greatful. > > result of tail -10: > > ÿÿÿÿüÿÿÿÿÿÿÿÿ@ > @A.interp.MIPS.options.reginfo.dynamic.liblist.dynstr.hash.dynsym.MIPS.symli > b.msym.MIPS.stubs.text.init.rodata.data.got.sbss.sdata.srdata.lit8.lit4.bss. > MIPS.events.init.MIPS.post_rel.text.MIPS.events.text.MIPS.content.sdata.MIPS > .content.data.MIPS.content.rodata.debug_info.debug_pubnames.d0p°° > È)pààP200X@aranges.debug_funcnames.debug_abbrev.debug_frame.comment.MIPS.int > erfaces.shstrtab p > 7ä7ä&Hp ]ô]ôUp`X[s`sìg|L|L|mÈÈs ÐиXXP§¡§ § §°§Uv°Q§ Looks like an executable binary to me. I think you can find debuggers in /usr/ports/devel. How these works exactly is however more than I know of. :-) Best regards, Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message