similar to: [GSOC-2018]: Clang Static Analyzer- Create a checker for dangling string pointers in C++

Hello Developer Team, My name is Rustam Khadipash, I am a forth year student in Computer Science at Pusan National University. This summer I would like to contribute to your project, however I do not have experience in contributing to open source societies so far. Therefore, I would like to start with not a difficult, in my opinion, project as "a checker for dangling string pointers in

Hello developers, My name is Zhihan Chen and I am currently a year 4 computer science student at the University of Hong Kong. I am interested in building a checker for dangling string pointer. I've learned some essential knowledge about compiler from our university course and built a mini-compiler on my own (Available at https://github.com/CHEN- Zhihan/Compiler). I've gone through the

Hello, I'm Paul Semel, a French student in computer science. I am currently in my 4th year (1st year of graduate school) at EPITA and enrolled in the system and security laboratory of the school. I would be very interested in working on a LLVM project during this GSoC. Implementing a PoC for an unsequenced modification checker in CSA helped me discover LLVM. However, I would like to

Hey, On 02/20/2018 11:51 PM, Paul Semel wrote: > Hello, > > > I'm Paul Semel, a French student in computer science. I am currently in > my 4th year (1st year of graduate school) at EPITA and enrolled in the > system and security laboratory of the school. > > I would be very interested in working on a LLVM project during this > GSoC. Implementing a PoC for an

Hi, Thanks for replying ! On 03/02/2018 10:58 PM, Artem Dergachev wrote: > Hey, welcome! > > I'm curious about the unsequenced modification checker, is it something > that I should have seen but missed for whatever reason? It might be > useful, and I think I'm seeing why don't compiler warnings cover all > cases, i.e. why the analyzer's path sensitivity

Hey, welcome! I'm curious about the unsequenced modification checker, is it something that I should have seen but missed for whatever reason? It might be useful, and I think I'm seeing why don't compiler warnings cover all cases, i.e. why the analyzer's path sensitivity would help here. But I can't answer until I see it :) -eg. on our Phabricator. We are currently having

Hi Eric, As you are pointed to be the confirmed mentor for the "Command line replacements for GNU Binutils" GSOC 2018 subject, I permit myself to add you to this thread ! If you have a few minutes to answer my questions, that'd really great 🙂 On 03/01/2018 08:43 PM, Paul Semel wrote: > Hey, > > On 02/20/2018 11:51 PM, Paul Semel wrote: >> Hello, >>

Hello, Le 29/08/2019 à 01:02, Artem Dergachev a écrit : > Yay thx! > > Sylvestre, is there anything i can help you with in order to get the reports page back up? Sorry, it took me a while to get that back but here is the report of r371718: https://llvm.org/reports/scan-build/ > I'd also indeed love to spam people with warnings that they introduced, even if in the form of a

Hi Anna, I am a fourth year undergraduate student having experience with writing low-level code and program analysis. I would like to work on the project Clang Static Analyzer: Warn if virtual calls are made from constructors or destructors. The things that I have done until now: ----- 1. Compiled clang 2. Went through Kaleidoscope tutorial 3. Implemented a bunch of llvm function passes Looking

I have updated one of my S4 DCs to 4.5.5, somewhat excited about the line in the ChangeLog * Bug #12600 - dbcheck does not find or fix dangling links on live objects Do I misunderstand the scope of this bug? # samba-tool dbcheck --cross-ncs --fix --reset-well-known-acls ... ERROR: no target object found for GUID component for member in object CN=Domain Users,CN=Users,XXXXX -

On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: > Hello List, > > In preparation to update my samba ad-dc's running debian wheezy with > backported samba 4.6.8 to 4.7.3. > I'd like to fix two errors showing up in dbcheck whom hab been reported > by dbckech --cross-ncs for an long time but without causing any issues > so far. > > I'm

Am 25.11.2017 um 04:39 schrieb Andrew Bartlett: > On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: >> On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: >>> Hello List, >>> >>> In preparation to update my samba ad-dc's running debian wheezy with >>> backported samba 4.6.8 to 4.7.3. >>> I'd like to fix

Hello List, In preparation to update my samba ad-dc's running debian wheezy with backported samba 4.6.8 to 4.7.3. I'd like to fix two errors showing up in dbcheck whom hab been reported by dbckech --cross-ncs for an long time but without causing any issues so far. I'm getting this error on my main dc root at server:~# samba-tool dbcheck --cross-ncs Checking 4188 objects ERROR: no

On Oct 13, 2008, at 1:10 PM, Robert Zeh wrote: > > On Oct 13, 2008, at 1:07 PM, Chris Lattner wrote: >> >> Exceptions have a high cost in terms of code size, binary size, and >> even a bit of execution time. Also, they don't magically make the >> code safe from any error: code has to be designed specifically to use >> RAII and other techniques to handle

Sylvestre Ledru looks after the scan-build web report, but I understand it hit a few issues back in June (it normally updates a few times a week). We also discussed whether there was an automated way for those updates to email the summary to the cfe/llvm dev lists, indicating total warnings, and highlighting any new ones (we punted that discussion until the GSoC was done - btw thank you

Hey everyone! This Summer we managed to make the Clang Static Analyzer support the LLVM and LLVM-based projects with my mentors Artem Dergachev and Gabor Horvath. For a more detailed documentation please visit my final report: https://docs.google.com/document/d/1o9-xEWbzivUGKIOXp9jUNZYq0mkecd5KH5dBN5Hdlu8/ The project in a nutshell: I have fixed the most annoying false positives and added

Commit-ID: 08e03dee1485ec4823b3afd465b32938b3a40045 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=08e03dee1485ec4823b3afd465b32938b3a40045 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 3 Sep 2016 21:58:50 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] expand - Fix dangling

Commit-ID: 9885e7650e5daf90ddc2a9bb1dfc6af14e86ad9d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=9885e7650e5daf90ddc2a9bb1dfc6af14e86ad9d Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 3 Sep 2016 21:58:50 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: expand - Fix

On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: > On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: > > Hello List, > > > > In preparation to update my samba ad-dc's running debian wheezy with > > backported samba 4.6.8 to 4.7.3. > > I'd like to fix two errors showing up in dbcheck whom hab been reported > > by

Am 25.11.2017 um 16:55 schrieb Achim Gottinger via samba: > > > Am 25.11.2017 um 04:39 schrieb Andrew Bartlett: >> On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: >>> On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: >>>> Hello List, >>>> >>>> In preparation to update my samba ad-dc's running