On Tue, Sep 27, 2011 at 9:17 PM, Eric Merritt <[email protected]>wrote:
> On 09/27/11 at 09:12pm, Jordan Wilberding wrote: > > On Tue, Sep 27, 2011 at 9:03 PM, Eric Merritt <[email protected] > >wrote: > > > > > On 09/27/11 at 08:38pm, Jordan Wilberding wrote: > > > > On Tue, Sep 27, 2011 at 10:02 AM, Eric Merritt < > [email protected] > > > >wrote: > > > > > > > > > On 09/26/11 at 11:00pm, Jordan Wilberding wrote: > > > > > > Sure man. I left it in a bit of a mess, so let me regroup and see > > > exactly > > > > > > what is left on the code. > > > > > > > > > > > > > > > > No problem. We should be basing this probably off my latest master, > > > > > with the move to term based configs and the split of config and > state > > > > > thats going to affect you quite a bit. You might want to take a > look > > > > > there. > > > > > > > > > > I am more then willing to take a look at the code. > > > > > > > > > > > > > You can find where I left off here: > > > > > > > > https://github.com/jwilberding/otp/commit/10747727369c0eef4a0ec78b38464c0da3a6870c > > > > > > > > As you can see I am trying to add a flag to ignore abstract errors. > > > Whenever > > > > you run dialyzer on a beam that wasn't compiled with debug info, it > will > > > > break the whole process. > > > > > > > > I have some print statements sprinkled in right now to figure out why > my > > > > code changes weren't working. My suggestion is to first get dialyzer > to > > > work > > > > by testing it indexing two apps, one that was compiled with debug > info > > > and > > > > one that was not. If you use the current version of dialyzer it will > bomb > > > > out once it hits the app that doesn't have debug info. My version is > > > > supposed to catch that and continue working and just ignore when that > > > > happens, but there is a bug or something in my code. > > > > > > > > Once you are able to fix and run dialyzer on that example, then we > can > > > work > > > > on integrating it back into sinan, which I also have some code for. > Keep > > > in > > > > mind, we will need to rebase this fix to dialyzer, as I haven't > updated > > > my > > > > otp branch from canonical in a while. > > > > > > I think in the short term we have to discard the idea of modifying > > > dializer itself. What do you think of adding to the build config the > > > option to exclude applications from the dialyzer analysis. That is to > > > simply give the user the option to not include apps that do not have > > > debugging info compiled in? > > > > > > > > Yeah, that would be the best short term solution. > > You willing to take that task on? > > Yep. Assign it to me on pivotal. -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
