[lldb-dev] lldb warning or developer options

2019-09-26 Thread Sourabh Singh Tomar via lldb-dev
Hi Folks,

Is their a developer switch or diagnostic switch, that we can set in lldb,
to show warnings and other useful stuff when lldb process the binary,
building table and utilizing DWARF.

I stumble upon, a rather trivial test case. where I deleted the *.dwo file.
and loaded primary binary in lldb. lldb loaded it silently without any
error or diagnostic reports for not found *.dwo file. Obviously, debug data
wasn't loaded, as I entered list command, nothing happened.

Why need this, as new dwarf-5 features are in development, if lldb can
report some diagnostics like section not found or ill-formed section, this
would be immensely useful .

Thanks!
-- Sourabh Singh Tomar
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] lldb warning or developer options

2019-09-27 Thread Sourabh Singh Tomar via lldb-dev
Hi Pavel,

Thanks for sharing this, I'll look into this.


 -- Sourabh Singh Tomar

On Fri, Sep 27, 2019 at 12:18 PM Pavel Labath  wrote:

> On 27/09/2019 07:52, Sourabh Singh Tomar via lldb-dev wrote:
> > Hi Folks,
> >
> > Is their a developer switch or diagnostic switch, that we can set in
> > lldb, to show warnings and other useful stuff when lldb process the
> > binary, building table and utilizing DWARF.
> >
> > I stumble upon, a rather trivial test case. where I deleted the *.dwo
> > file. and loaded primary binary in lldb. lldb loaded it silently without
> > any error or diagnostic reports for not found *.dwo file. Obviously,
> > debug data wasn't loaded, as I entered list command, nothing happened.
> >
> > Why need this, as new dwarf-5 features are in development, if lldb can
> > report some diagnostics like section not found or ill-formed section,
> > this would be immensely useful .
> >
> > Thanks!
> > -- Sourabh Singh Tomar
> >
>
> Hi Sourabh,
>
> there the Module::ReportWarning function, which will print a warning (to
> stderr generally). We should probably make use of that functionality to
> report missing dwo files. Care to put up a patch?
>
> pl
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] How/where to add test cases in LLDB.

2020-01-10 Thread Sourabh Singh Tomar via lldb-dev
Hello Everyone,

I've wrote a patch for extending support for new forms[DWARFv5] in macro
section. Planning to file a review soon.

But I'm stuck with writing test case for this. My feature works well when
using LLDB in interactively, but I need to write a test case to accompany
my patch.

To put things in perspective:
here' s how I tested it interactively:

$lldb a.out
$display MACRO1  -- macro defined in source/a.out
$ b main
$ run
LLDB output
- Hook 1 (expr -- MACRO1)
(int) $0 = 4
Process 18381 stopped
* thread #1, name = 'a.out', stop reason = breakpoint 1.1

Need to write/add test case for this so that it will be run by "make
check-lldb", any ideas/pointers how to proceed forward from here.

Thanks in anticipation!
Sourabh Singh Tomar
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev