[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Fw: [epp-dev] Testing Luna M4 packages
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of kesselhaus
> Sent: Friday, December 20, 2013 6:53 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: Re: [cdt-dev] Fw: [epp-dev] Testing Luna M4 packages
>
> Am 19.12.2013 17:40, schrieb Doug Schaefer:
> Can someone grab one of the CDT builds and give it a quick sanity for me?
> I'm on holidays and will be out most of the day.
>
> The main thing to look out for is being able to create a new project, have it
> build and then hit a breakpoint in debug. Also check that the cdt plugins are
> from this week.
> Just tried the Build #56.
> I have only the equation.com GCC, seems to work here on Win7 64bit,
> Eclipse Luna 4.4M4.
>
> Create "Executable Hello World" Project, with MinGW compiler, I have no
> Visual Studio installed and also no LLVM (who know if they will ever provide
> up-to-date binaries for windows ever).
> Created another test.c/.h, some function and an extern int and accessing
> them from main.c within a loop.
> Compile and run is ok.
>
> Breakpoint in test function is hit. but when resuming over and over, after
> the last loop, when the program reaches the end and quits I get this in the
> gdb-trace console:
>
> 254,068 foobar = 17 Testing = 272
> 254,068 foobar = 18 Testing = 306
> 254,068 foobar = 19 Testing = 342
> 254,068 foobar = 20 Testing = 380
> 254,068 =thread-exited,id="1",group-id="i1"
> 254,068 =thread-group-exited,id="i1",exit-code="0"
> 254,068 *stopped,reason="exited-normally"
> 254,068 (gdb)
> 254,073 &"Quit (expect signal SIGINT when the program is resumed)\n"
> 254,089 378-gdb-exit
> 254,090 379-break-delete --thread-group i1 1
> 254,093 378^exit
>
> Is this "expect signal SIGINT when the program resumed" a
> normal/expected gdb output?
I believe this happens when we send a ^C to gdb, which we do
in all-stop mode. My guess is that you pressed the Terminate button
while the program was running, so we had to interrupt it so that
we could send -gdb-exit. So, it is ok.
> Also, the console still seems to get confused with printf("blah
> blah\n"); scanf("%lf", &mydouble); It already stays at the scanf without
> printing the "blah blah" before, even though there is a '\n' there.
>
> How far is that WinPTY support done, and where can this WinPTY be used? I
> see the contribution mentioned in Build #52.
I believe it has been committed, but it is disabled by default.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419391#c36
It can be enabled via system property (org.eclipse.cdt.core.winpty_console_mode=true)
>
> BTW. did you see the cool new Split Editor feature. Even though, the key
> mapping is a bit strange for non-US keyboards (CTRL+{ which can be hardly
> reached on german layout, the same for CTRL+_ which is actually a
> CTRL+Shift+- on german layout).
I'm going to install M4 just to try that out :)
>
>
> Thanks!
>
> Sent from my BlackBerry Z30 smartphone.
> From: Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>
> Sent: Thursday, December 19, 2013 6:09 AM
> To: EPP Developer Mailing List
> Reply To: Eclipse Packaging Project
> Subject: [epp-dev] Testing Luna M4 packages
>
> Hi Package Maintainers,
> the Luna M4 packages are waiting to be tested... please note that the
> download location has changed. They are now available from
>
> https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/34/
> Just follow 'Build Artifacts' > 'org.eclipse.epp.packages' > 'packages' and
> follow the next links to your zip/tar.gz archive with the package.
> Thanks,
> Markus
>
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
