[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150429144618.GA12549@alex-ThinkPad-L530>
Date: Wed, 29 Apr 2015 16:46:18 +0200
From: Alex Dowad <alexinbeijing@...il.com>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] generate debug_frame info for __syscall_cp_asm (i386) so
gdb can get backtrace
On Mon, 27 Apr 2015 16:57:22 -0400, Rich Felkner wrote:
> This has been requested before, but it really uglifies the asm and
> makes it unreadable. Do you have any ideas for mitigating the problem?
Perhaps using PUSH() and POP() macros which automatically add .cfi_*
directives?
> Another idea would be programmatically generating the cfi from the asm
> with a script that runs at compile-time, and passing the output of the
> script to the assembler. One benefit of this approach is that it could
> be tuned based on whether -g is in use or not. With hard-coded .cfi_*
> I don't see a clear way to suppress it when -g is not in use.
Conditionally defining the PUSH() and POP() macros to omit the .cfi_*
stuff when debugging is disabled?
Of course using a script to parse the asm is SO much more slick... but
you probably don't want to add too many dependencies to your build process
either. Would it have to be just a plain shell script?
Thanks for your feedback, AD
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.
