Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Marco Bubke <Marco.Bubke@qt.io>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
	"qt-creator@qt-project.org" <qt-creator@qt-project.org>
Subject: Re: [Qt-creator] Qt Creator for Linux Kernel Development
Date: Tue, 29 Nov 2016 20:21:01 +0100	[thread overview]
Message-ID: <CAHmME9rLoJbKda+i9z2AA2jpqfZ96XG_ZEVurKbHbZ2TfPqdRQ@mail.gmail.com> (raw)
In-Reply-To: <HE1PR02MB16597D89414EB2F7E6265BA2F08A0@HE1PR02MB1659.eurprd02.prod.outlook.com>

Hi Marco,

I'll start compiling a list for you, so that I can give you something
more useful than my last message. For starters, here's one bug found
within seconds:

1. Open a file in the project. All seems fine.
2. Ctrl click on a function that points to somewhere in the Linux
kernel headers.
3. Close that file. Now there are all sorts of non-nonsensical clang
errors in the original file.

Here's a video to demonstrate:
https://data.zx2c4.com/qt-creator-clang-model-bug-ff94c572-d8ff-4c54-a5ac-3aa6485251a9.mp4

Jason

  reply	other threads:[~2016-11-29 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23  5:51 Jason A. Donenfeld
2016-11-23  7:45 ` [Qt-creator] " Konstantin Tokarev
2016-11-28 18:03   ` Jason A. Donenfeld
2016-11-28 19:49     ` Marco Bubke
2016-11-29 19:21       ` Jason A. Donenfeld [this message]
2016-11-28 21:34     ` André Pönitz
2016-11-29  8:55     ` Nikolai Kosjar
2016-11-29 19:23       ` Jason A. Donenfeld
2016-11-30  8:41         ` Nikolai Kosjar
2016-11-30  8:43       ` Orgad Shaneh
2016-11-29  8:56   ` Nikolai Kosjar
2016-11-23  7:58 ` Orgad Shaneh
2016-11-23  9:21 ` Eike Ziller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHmME9rLoJbKda+i9z2AA2jpqfZ96XG_ZEVurKbHbZ2TfPqdRQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=Marco.Bubke@qt.io \
    --cc=qt-creator@qt-project.org \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).