[lldb-dev] Introductions

2016-07-21 Thread Pavel Labath via lldb-dev
Hello everyone,

I'd like to introduce Dimitar. He will be with us as an intern for the
next few months and will be looking into adding minidump support for
platforms other than windows. Basically, we'd like to add a new
process plugin which does not depend on native windows api's to parse
the minidump structures (at which point we can hopefully remove
ProcessWinMiniDump).

cheers,
pl
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Introductions

2016-07-21 Thread Adrian McCarthy via lldb-dev
Cool.  Welcome!

I expect that's very do-able (and it was something on my to-do list,
eventually).

I believe the dump file is relatively trivial.  The Windows API
(::MiniDumpReadDumpStream) just returns ranges of the memory mapped dump
file.  I think you could essentially implement that API in a portable way
and swap it in to the one place in ProcessWinMiniDump that calls it.  Once
that's working, you can hoist it of the Windows-specific world and make it
available everywhere.

On Thu, Jul 21, 2016 at 8:22 AM, Pavel Labath  wrote:

> Hello everyone,
>
> I'd like to introduce Dimitar. He will be with us as an intern for the
> next few months and will be looking into adding minidump support for
> platforms other than windows. Basically, we'd like to add a new
> process plugin which does not depend on native windows api's to parse
> the minidump structures (at which point we can hopefully remove
> ProcessWinMiniDump).
>
> cheers,
> pl
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [FYI] Ongoing discussion on llvm-dev: "One or many git repositories?"

2016-07-21 Thread Justin Lebar via lldb-dev
We're having a discussion on the following question on llvm-dev:

Assuming we switch our canonical VCS to git, then
  - should we have one git repository per llvm subproject, or
  - should we have a single monolithic git repository.

https://groups.google.com/forum/#!topic/llvm-dev/aSc9BxXtboc

This will affect all of us, so I wanted to loop in these lists.
Please respond on llvm-dev, not here, so we don't fork the thread.

Regards,
-Justin
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev