Date: Wed, 29 Apr 2015 13:03:08 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: Re: [PATCH] generate debug_frame info for __syscall_cp_asm (i386) so gdb can get backtrace On Wed, Apr 29, 2015 at 06:51:29PM +0200, Alex Dowad wrote: > On Wed, 29 Apr 2015 11:57:03 -0400, Rich Felkner wrote: > > It would be either sed or awk most likely. Plain shell would work for > > writing it too but would probably be uglier, and sed is already > > required anyway for alltypes.h generation. If any new tool were > > required (unlikely) then configure would just detect its absence and > > turn off cfi generation for asm if it's missing/broken. > > I can try coding up an awk script if you like (no sed, sorry). It will be a > filter which the asm passes through to add the .cfi_* directives. Does that > sound good? > > (I really, really hope you weren't looking for an awk/sed script which takes > asm as input and generates a DWARF file as output...) Of course not; I meant for it to produce asm with cfi directives as output. If you'd like to give it a try that would be great. Some of the main criteria that would matter for inclusion in musl would be portable awk usage (standard awk, not gawk/etc., and compatible with Busybox) and the ability to support multiple archs -- even if the initial code is x86-only, it should take $ARCH as an argument and be reasonably easy for others to extend it to support other archs. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.