* [9fans] lstk() in acid limited due to no type information
@ 2014-02-18 23:48 erik quanstrom
0 siblings, 0 replies; only message in thread
From: erik quanstrom @ 2014-02-18 23:48 UTC (permalink / raw)
To: 9fans
i don't use acid a lot in situations where this makes any
difference, so i hadn't noticed this until now. but lstk()
backtraces can't do the right thing because they don't know how
much of each uintptr-sized stack element is actually used.
assuming 4 bytes often works for 32-bit machines since pointers
look correct. unfortunately, on 64-bit machines, pointers are
mangled. printing 8 bytes at a time unfortunately mangles all
32-bit values on the stack since the upper 32-bits don't have any
defined value. a.out(6) mentions the issue, and suggets 8c(1)'s
-a flag, but this is of no use for backtraces since the compiler
doesn't information for local variables.
does anyone have ideas on how to work around this issue?
- erik
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-02-18 23:48 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-18 23:48 [9fans] lstk() in acid limited due to no type information erik quanstrom
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).