Re: James Rogers - Status Report #6 of 17

[James Rogers <jamesmrogers () gmail com>]

Right now I am just trying to figure out if what clang reported even
is a real bug.  Clang reported about 60 issues inside nping so I
thought I would start my bug fixing efforts there as a self contained
area to work in and see some results.

Thanks for the heads up on the location of the dev version of nping.
I'll check that out and run clang on it tonight to see what is
happening there.


On Tue, Jun 5, 2012 at 5:28 PM, Luis MartinGarcia. <luis.mgarc () gmail com> wrote:
> On 06/04/2012 09:01 PM, James Rogers wrote:
>
>     - Nping has most of the clang bugs, working on classifying bugs
> and posting them to the dev-nmap list.
>
>
> Hi James,
>
> It's great that you are fixing some bugs in Nping! Just note that the
> current dev version of Nping is located in
> nmap-exp/luis/nmap-npingchanges/nping. The Nping on that branch is quite
> different from the trunk (many new features and bugfixes there). I suggest
> that you first test whether the bugs you are trying to fix can be reproduced
> in the dev branch, and in that case, to fix them there, not in trunk (unless
> the bugs are critical, of course). Otherwise, it's going to be a nightmare
> to merge the branch later, as the code has suffered a lot of changes. What
> do you think?
>
> Btw, which bugs are you working on?
>
> Best regards,
>
> Luis MartinGarcia.
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/