Re: [Qt-creator] Odd QtCreator hang
> > Disassembler > > 0x7741000c cc int3 > > 0x7741000d <+0x0001>c3 ret > > 0x7741000e <+0x0002>90 nop > > There are other threads running at that time. The output of > 'thread apply all backtrace full' would be interesting. How do I acquire this? > Perhaps even in JIRA. As a new bug, or attached to one of the two ones that seem related? Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] Odd QtCreator hang
On Tue, Apr 17, 2018 at 12:27:07PM +, Murphy, Sean wrote: > > > I've got an odd hang with QtCreator when debugging my software. > > Oh, as you are on Windows, that's the third platform that show > > clipboard-related strage effects. > > > > We already have QTCREATORBUG-20262 and QTBUG-67729. Can you please > > check > > these? > > I had stumbled upon QTBUG-67729 yesterday when searching for this issue, and > I > think I read this line from it differently than I am today: " We consistently > get a hang > when we hit a breakpoint if we happen to copy text to the clipboard before we > hit > the breakpoint". I dismissed that as different than what I was doing, but > this morning > I think it might be essentially the same. What I was doing was setting a > breakpoint > well above the QClipboard::setText() call (which is why I thought it wasn't > quite the same), > but then I was stepping one line at a time through my code including over > that line, > which I'm now guessing is effectively the same as setting a breakpoint after > the copy. > > I didn't find QTCREATORBUG-20262 yesterday, but I just built it and ran it as > the reporter > described. They didn't post the .pro file used, so I'm not sure if all of > those build settings were > the same. Anyways, when I ran it Qt Creator didn't lock up, but I did get the > attached popup. If I > switch the QClipboard::setImage() call in his example to > QClipboard::setText(), leaving the > breakpoint on the qDebug() line, Creator again doesn't hang, but it does drop > into the > disassembler (relevant info pasted below). > > I'm realizing that I neglected to mention that I am using the mingw toolchain > on Windows, > so maybe it's a gdb issue? > > Call stack when disassembler hit > 1 ntdll!DbgBreakPoint 0x7741000d > 2 ntdll!DbgUiRemoteBreakin0x7749f306 > 3 ?? 0x6ac2b5ef > 4 KERNEL32!BaseThreadInitThunk0x76be343d > 5 ntdll!RtlInitializeExceptionChain 0x77439832 > 6 ntdll!RtlInitializeExceptionChain 0x77439805 > 7 ?? > > Disassembler > 0x7741000c cc int3 > 0x7741000d <+0x0001>c3 ret > 0x7741000e <+0x0002>90 nop There are other threads running at that time. The output of 'thread apply all backtrace full' would be interesting. Perhaps even in JIRA. Andre' ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] make stalling on OSX
I always provide bug reports where I think Qt/QtC need correction, but
sometimes I like to check the mailing lists first for quick fixes/known issues,
or and this is the big one, other people who are experiencing it but have not
reported it ("me too!" situation)
:-)
It might be a good idea to get the bug creation reports dumped into the mailing
lists? (Purely for collaborative effect)
> Sent: Tuesday, April 17, 2018 at 3:31 AM
> From: "Eike Ziller"
> To: Andy
> Cc: "Jason H" , "qt-creatorqt-project.org"
>
> Subject: Re: [Qt-creator] make stalling on OSX
>
> If you get lock-ups of Qt Creator on macOS, please open Activity Monitor,
> select the Qt Creator process and trigger “Sample” from the “gear” menu. That
> often contains useful information about what it currently tries to do / what
> it is waiting for.
> Of course best attached to a bug report ;)
>
> Br, Eike
>
> > On Apr 16, 2018, at 16:54, Andy wrote:
> >
> > I have this issue too (macOS 10.12.6 w/Qt Creator 4.6).
> >
> > Usually if I just switch the editor using Option-tab it continues ok.
> >
> > I also get these (or something like them) when doing "Follow symbol under
> > cursor" and "Rename symbol" sometimes.
> >
> > ---
> > Andy Maloney // https://asmaloney.com
> > twitter ~ @asmaloney
> >
> >
> > On Mon, Apr 16, 2018 at 10:34 AM, Jason H wrote:
> > I've got a pretty chronic problem of the latest creator stalling on OSX.
> > I'll hit the play button, it'll say:
> > 10:30:17: Running steps for project winston...
> > 10:30:17: Configuration unchanged, skipping qmake step.
> > 10:30:17: Starting: "/usr/bin/make"
> >
> > Then nothing. When I cancel the build using the red square, then it dumps a
> > bunch of compiler output.
> >
> > It goes through periods where 50% of make invocations are stalled.
> > ___
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/qt-creator
> >
> > ___
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg,
> HRB 144331 B
>
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] Odd QtCreator hang
> > I've got an odd hang with QtCreator when debugging my software. > Oh, as you are on Windows, that's the third platform that show > clipboard-related strage effects. > > We already have QTCREATORBUG-20262 and QTBUG-67729. Can you please > check > these? I had stumbled upon QTBUG-67729 yesterday when searching for this issue, and I think I read this line from it differently than I am today: " We consistently get a hang when we hit a breakpoint if we happen to copy text to the clipboard before we hit the breakpoint". I dismissed that as different than what I was doing, but this morning I think it might be essentially the same. What I was doing was setting a breakpoint well above the QClipboard::setText() call (which is why I thought it wasn't quite the same), but then I was stepping one line at a time through my code including over that line, which I'm now guessing is effectively the same as setting a breakpoint after the copy. I didn't find QTCREATORBUG-20262 yesterday, but I just built it and ran it as the reporter described. They didn't post the .pro file used, so I'm not sure if all of those build settings were the same. Anyways, when I ran it Qt Creator didn't lock up, but I did get the attached popup. If I switch the QClipboard::setImage() call in his example to QClipboard::setText(), leaving the breakpoint on the qDebug() line, Creator again doesn't hang, but it does drop into the disassembler (relevant info pasted below). I'm realizing that I neglected to mention that I am using the mingw toolchain on Windows, so maybe it's a gdb issue? Call stack when disassembler hit 1 ntdll!DbgBreakPoint 0x7741000d 2 ntdll!DbgUiRemoteBreakin0x7749f306 3 ?? 0x6ac2b5ef 4 KERNEL32!BaseThreadInitThunk0x76be343d 5 ntdll!RtlInitializeExceptionChain 0x77439832 6 ntdll!RtlInitializeExceptionChain 0x77439805 7 ?? Disassembler 0x7741000c cc int3 0x7741000d <+0x0001>c3 ret 0x7741000e <+0x0002>90 nop 0x7741000f <+0x0003>90 nop 0x77410010 <+0x0004>90 nop 0x77410011 <+0x0005>90 nop 0x77410012 <+0x0006>90 nop 0x77410013 <+0x0007>90 nop 0x77410014 <+0x0008>90 nop 0x77410015 <+0x0009>90 nop 0x77410016 <+0x000a>90 nop 0x77410017 <+0x000b>90 nop 0x77410018 <+0x000c>90 nop 0x77410019 <+0x000d>90 nop 0x7741001a <+0x000e>90 nop 0x7741001b <+0x000f>90 nop 0x7741001c <+0x0010>90 nop 0x7741001d <+0x0011>90 nop 0x7741001e <+0x0012>90 nop 0x7741001f <+0x0013>90 nop 0x77410020 <+0x0014>90 nop 0x77410021 <+0x0015>90 nop 0x77410022 <+0x0016>90 nop 0x77410023 <+0x0017>90 nop 0x77410024 <+0x0018>90 nop 0x77410025 <+0x0019>90 nop 0x77410026 <+0x001a>90 nop 0x77410027 <+0x001b>90 nop 0x77410028 <+0x001c>90 nop 0x77410029 <+0x001d>90 nop 0x7741002a <+0x001e>90 nop 0x7741002b <+0x001f>90 nop 0x7741002c <+0x0020>90 nop 0x7741002d <+0x0021>90 nop 0x7741002e <+0x0022>90 nop 0x7741002f <+0x0023>90 nop 0x77410030 <+0x0024>90 nop 0x77410031 <+0x0025>90 nop 0x77410032 <+0x0026>90 nop 0x77410033 <+0x0027>90 nop 0x77410034 <+0x0028>90 nop 0x77410035 <+0x0029>90 nop 0x77410036 <+0x002a>90 nop 0x77410037 <+0x002b>90 nop 0x77410038 <+0x002c>90 nop 0x77410039 <+0x002d>90 nop 0x7741003a <+0x002e>90 nop 0x7741003b <+0x002f>90 nop 0x7741003c <+0x0030>90 nop 0x7741003d <+0x0031>90 nop 0x7741003e <+0x0032>90 nop 0x7741003f <+0x0033>90 nop 0x77410040 <+0x0034>8b 4c 24 04 mov0x4(%esp),%ecx 0x77410044 <+0x0038>f6 41 04 06 testb $0x6,0x4(%ecx) 0x77410048 <+0x003c>74 05 je 0x7741004f 0x7741004a <+0x003e>e8 a1 1d 01 00 call 0x77421df0 0x7741004f <+0x0043>b8 01 00 00 00 mov$0x1,%eax 0x77410054 <+0x0048>c2 10 00ret$0x10 0x77410057 <+0x0
[Qt-creator] What are new features of Qt Creator 4.7?
Hi, What are new features of Qt Creator 4.7? Will ClangRefactoring plugin come back? Thanks, Vincent ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
Re: [Qt-creator] make stalling on OSX
If you get lock-ups of Qt Creator on macOS, please open Activity Monitor, select the Qt Creator process and trigger “Sample” from the “gear” menu. That often contains useful information about what it currently tries to do / what it is waiting for. Of course best attached to a bug report ;) Br, Eike > On Apr 16, 2018, at 16:54, Andy wrote: > > I have this issue too (macOS 10.12.6 w/Qt Creator 4.6). > > Usually if I just switch the editor using Option-tab it continues ok. > > I also get these (or something like them) when doing "Follow symbol under > cursor" and "Rename symbol" sometimes. > > --- > Andy Maloney // https://asmaloney.com > twitter ~ @asmaloney > > > On Mon, Apr 16, 2018 at 10:34 AM, Jason H wrote: > I've got a pretty chronic problem of the latest creator stalling on OSX. > I'll hit the play button, it'll say: > 10:30:17: Running steps for project winston... > 10:30:17: Configuration unchanged, skipping qmake step. > 10:30:17: Starting: "/usr/bin/make" > > Then nothing. When I cancel the build using the red square, then it dumps a > bunch of compiler output. > > It goes through periods where 50% of make invocations are stalled. > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
