From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of kesselhaus [kesselhaus@xxxxxxx]
Sent: Friday, 20 December 2013 7:13 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Fw: [epp-dev] Testing Luna M4 packages
Oh, just forgot to check my .log and I see a bunch of key binding conflicts.
Not a big deal, but lots of reconfiguration which wouldn't be necessary, if Eclipse Plugin projects (at least that from the foundation) would communicate with each other and being not so greedy on their scope selection. I guess they come from, when one hooks
it's binding not to it's specific editors/views but to "In Windows".
Like ALT+SHIFT+R, Refactoring, the Java Plugin hooks to "In Windows", while others only to specific edit/views.
Am 21.12.2013 00:52, schrieb kesselhaus:
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?
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.
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).
Thanks!
Sent from my BlackBerry Z30 smartphone.
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
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
