On Mon, 20 May 2013, Ian Lance Taylor wrote: > To be clear: are you withdrawing your earlier patch?
Yes; at this point I don't think it improves anything sufficiently to spend more time on it. Forgive me a digression, but having now actually used libbacktrace, I have the following questions. 1. The documentation does not say whether reusing "state" objects is allowed. For instance, I'm using backtrace_simple, and then in the callback I'm invoking dladdr and backtrace_pcinfo to gather file-line info if available. Looks like at the moment it's fine, as no frame-specific information is stored there. 2. The reason I'm invoking dladdr instead of backtrace_syminfo is the need to obtain the name of the module containing the symbol. Is that intended? (IOW, would be nice if libbacktrace syminfo callback provided name and base address of the loaded module as well) 3. In libbacktrace/elf.c, elf_syminfo() does not seem to walk the chain of elf_syminfo_data (i.e. does not use edata->next). Is that a bug? Thanks. Alexander
