Re: [lldb-dev] Linux core dump doesn't show listing when loaded

2015-12-02 Thread Todd Fiala via lldb-dev
Does our init file mechanism have the ability to do something conditionally if it's a core file? (i.e. do we already have a way to get Ted's desired behavior via an inserted call to "thread backtrace all" that somehow gets triggered by the init, but only when we're talking about a core file?)

Re: [lldb-dev] Linux core dump doesn't show listing when loaded

2015-12-02 Thread Jim Ingham via lldb-dev
> On Dec 2, 2015, at 8:35 AM, Todd Fiala via lldb-dev > wrote: > > Does our init file mechanism have the ability to do something conditionally > if it's a core file? (i.e. do we already have a way to get Ted's desired > behavior via an inserted call to "thread

Re: [lldb-dev] Linux core dump doesn't show listing when loaded

2015-11-30 Thread Greg Clayton via lldb-dev
"thread list" should just list the threads and their stop reasons (no backtraces). If you want backtraces just do "thread backtrace all". On Nov 24, 2015, at 1:09 PM, Ted Woodward via lldb-dev wrote: > > I’ve been working on an old rev that we’d released on; now I’m

Re: [lldb-dev] Linux core dump doesn't show listing when loaded

2015-11-25 Thread Pavel Labath via lldb-dev
There has been some discussion in , as to what get's printed when, but I don't think any changes went in yet. I wouldn't be opposed to bringing back the old behavior (or keeping the current one, for that matter), but I feel that any change here should consistent

[lldb-dev] Linux core dump doesn't show listing when loaded

2015-11-24 Thread Ted Woodward via lldb-dev
I've been working on an old rev that we'd released on; now I'm much closer to ToT as we move towards our next major Hexagon release. Core dumps on the old rev would print out a listing/disassembly for each thread in the core dump. Now it doesn't. ToT does this, on x86 Linux: >bin/lldb