From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: [PATCH] generate debug_frame info for __syscall_cp_asm (i386) so gdb can get backtrace
Date: Wed, 29 Apr 2015 13:03:08 -0400 [thread overview]
Message-ID: <20150429170308.GW17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150429165129.GA15839@alex-ThinkPad-L530>
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
next prev parent reply other threads:[~2015-04-29 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 16:51 Alex Dowad
2015-04-29 17:03 ` Rich Felker [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-29 14:46 Alex Dowad
2015-04-29 15:57 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150429170308.GW17573@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).