Qt Creator Freezes at "Setting Breakpoints" When Starting Debug

[Josiah Bryan]

When trying to start a debugging session (by pressing F5), Necessitas (alpha 3) Qt Creator freezes at "Setting Breakpoints..." - this is on Windows 7 64bit

Notes:

- I *have* changed the "build" mode to "Debug" instead of release

- I've cleaned the project (Build->Clean All) and rebuilt (F5 auto rebuilt, rather)

- Qt Creator really doesn't freeze, rather it sits there with a "Wait" cursor (pointer + spinner) for around 5 - 15 minutes - eventually a popup appears indicating my process (org.jdbryan.etc... process) has died

- I've quit Qt Creator and restarted it all over again - still didn't work

- My app also runs just fine in release mode

- When running the app on linux (not in Necessitas, just building with Qt), but with all appros defines (DEFINES+=Q_OS_ANDROID) to ensure my android-specific code paths are ran, the app runs just fine

Any thoughts on why I can't get debugger to start?

(If anyone wants to try it themselves, my code is on Google Code at http://code.google.com/p/wifisigmap - the latest rev has a problem where pressing the menu key three times causes it to crash on Android, but not on any other platform. Necessitas debugger is my last hope for figure out why it crashes in this case, since it doesn't crash in that code path under Linux on my laptops or desktops.)

Thanks so much!

-Josiah

--
Josiah Bryan
765-215-0511
josia...@gmail.com

[paulus]

I had some issues with development on Windows 7 64-bit too, this is why I changed to linux. The biggest issue I had was with ADB, which could cause freezes in QtCreator. Now the problem you describe doesn't fit exactly the problem I had. But maybe killing ADB and restarting it before starting a debug session might help.

[Nalin Savara]

On Wed, Aug 1, 2012 at 10:14 PM, paulus <paul....@gmail.com> wrote:

I had some issues with development on Windows 7 64-bit too, this is why I changed to linux. The biggest issue I had was with ADB, which could cause freezes in QtCreator. Now the problem you describe doesn't fit exactly the problem I had. But maybe killing ADB and restarting it before starting a debug session might help.

yah... even I had freezes; am using windows-7 64-bit.

however, development experience on Mac OS X Lion is much better... and faster too when installing apk.

On Windows: Often it helps to open task-manager-- and kill all instances of adb--> 

but in general UX on windows is not as good as should be.

Regards,

Nalin

[Josiah Bryan]

On Wed, Aug 1, 2012 at 12:59 PM, Nalin Savara <nsn...@gmail.com> wrote:

On Wed, Aug 1, 2012 at 10:14 PM, paulus <paul....@gmail.com> wrote:

I had some issues with development on Windows 7 64-bit too, this is why I changed to linux. The biggest issue I had was with ADB, which could cause freezes in QtCreator. Now the problem you describe doesn't fit exactly the problem I had. But maybe killing ADB and restarting it before starting a debug session might help.

yah... even I had freezes; am using windows-7 64-bit.

I'd love to develop on linux instead - but my linux laptop is 64bit and Necessitas doesn't do 64bit yet. My linux desktop is 32 bit - but it's too old (CentOS 5.X) to run Necessitas alpha 3. 

however, development experience on Mac OS X Lion is much better... and faster too when installing apk.

I wish I had a Mac machine to devel on - the only Mac OS X I can run is in a Virtual Box emulator so far - now I just need to save up enough $$ to buy a Mac off ebay! :-)

On Windows: Often it helps to open task-manager-- and kill all instances of adb--> 

but in general UX on windows is not as good as should be.

Good advice re: kill adb - I'll try that when I get home tonight and see if that gets me anywhere. Thanks!

 

-Josiah

[Nalin Savara]

one more thing-- when it freezes and you close Necessitas QtCreator--> also go to task manager and kill QtCreator.exe and adb.exe--->> surprisingly they persist even after closing qtcreator.

Regards,

Nalin 

[Ray Donnelly]

This bug sounds like an adb issue that we've seen on all platforms
(but probably worse on Windows). Killing adb (usually there are two
adb processes) does the trick, generally. Also, devices work better
than emulators. Another trick is to launch the emulator well before
you want to use it.

As for having a 64bit Linux laptop, you should be able to install the
32bit runtime libs so you can run 32bit Necessitas. Lastly I did
manage to build 64bit Linux Qt Creator if you want to go down that
route.

Cheers,

Ray.

[Josiah Bryan]

On Wed, Aug 1, 2012 at 4:18 PM, Ray Donnelly <mingw....@gmail.com> wrote:

This bug sounds like an adb issue that we've seen on all platforms
(but probably worse on Windows). Killing adb (usually there are two
adb processes) does the trick, generally. Also, devices work better
than emulators. Another trick is to launch the emulator well before
you want to use it.

Thanks for the info - I'm purely using my device for testing/debugging - a Motorola Droid 4 phone from Verizon with the stock/default ROM. I'll try killing adb tonight.

 

As for having a 64bit Linux laptop, you should be able to install the
32bit runtime libs so you can run 32bit Necessitas. Lastly I did
manage to build 64bit Linux Qt Creator if you want to go down that
route.

Ohhh yes....which 32bit runtime libs do I need? I would *love* to go that route - I just have no idea which libs. Even better, can you point me to the el6 RPMs or package names?

[Off topic]

I know this is asking for the world, but if you feel up to it, a wiki page with a step-by-step on building 64bit Necessitas Qt Creator would be very helpful if you're willing to put one together. I've spent several hours trying to track the various links in the current set of kde/necessitas wiki pages on building/compiling and I can't seem to find one place that says "download all these packages, build all these things, and poof - at the end, you'll have the full set of things known as necessitas." (Of course, I'm could be the idiot here and just not have found the right page or followed the right link!)

Thanks everyone for all your help and thanks for everyone who's helped put Necessitas together.

-Josiah

[Josiah Bryan]

On Wed, Aug 1, 2012 at 4:39 PM, Josiah Bryan <josia...@gmail.com> wrote:

On Wed, Aug 1, 2012 at 4:18 PM, Ray Donnelly <mingw....@gmail.com> wrote:

This bug sounds like an adb issue that we've seen on all platforms
(but probably worse on Windows). Killing adb (usually there are two
adb processes) does the trick, generally. Also, devices work better
than emulators. Another trick is to launch the emulator well before
you want to use it.

Thanks for the info - I'm purely using my device for testing/debugging - a Motorola Droid 4 phone from Verizon with the stock/default ROM. I'll try killing adb tonight.

Killed adb with the fire of a thousand suns - still no love. Still "Freezes" at setting breakpoints....I guess that leaves 32bit libs for Necessitas on 64bit linux to try debugging on linux - any ideas on what 32bit libs I need to install on my 64bit Linux (CentOS 6.2)? Thanks!

Of course, any further ideas on how to debug on Windows 7 64bit is welcome too...

Thanks!

-Josiah

[Nalin Savara]

hi Josiah...
Afaik u just need to run the necessitas installer in superuser mode
(using sudo)... It will find and install necessary libraries itself...

Regards,

Nalin

[Josiah Bryan]

Iirc I did run it as root last time...but ill try that again and report back...

[Josiah Bryan]

Alright, this is really starting to frustrate me - I downloaded and installed CentOS 6.3 - 32bit - in VirtualBox today on my Win 7 laptop. In my fresh install of CentOS, I downloaded and installed necessitas-0.3-online-sdk-installer-linux. I updated ant, downloaded my project from google code, opened it in Necessitas, set buildmode to debug (arm 7a)...annnndddd.....still the EXACT same problem:

- App builds, installs, opens
- Debugmger starts, says thread created, starting inferior, loading symbols, and finally, Setting Breakpoints...
- At this point, my phone sits there with a black screen (well, notification bar up top, but app area is black) and Qt Creator sits there at Setting Breakpoints... (It's been sitting there for 15+ minutes now.)

The ONLY hint I have at a problem is the console from whence I started Qt Creator says:

Unexpected GDB stderr: "/opt/NecessitasQtSDK/android-ndk-r6b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gdb: /lib/libz.so.1: no version information available (required by /opt/NecessitasQtSDK/android-ndk-r6b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gdb)
"

So, two TOTALLY different OS's, a fresh install of Necessitas and fresh build of the app .... and the exact same problem. Any thoughts here on how to fix this and actually get the debugger to...erm...debug?

[Nalin Savara]

try using armv5 instead of arm-7-a.

Does that also give problem ?

Regards,

Nalin

[Willy Gardiol]

Sorry if l chime in late... debug is only supported for android 2.3 or
later ... you must select a later API for the debugger to work...

------- Messaggio originale -------
> Da: Nalin Savara <nsn...@gmail.com>
> A: andro...@googlegroups.com
> Inviato: 2.8.'12, 23:21

[Josiah Bryan]

There is only arm 5 and arm 7a in the build options..is that what you're refering to? Or do I need to up a ver setting somewhere else...?

[Josiah Bryan]

I've tried 6 different version/API level combos, and the debugger still freezes EVERY time at "Setting breakpoints..."

What I've tried exactly:
- Under Qt Creator->Projects->Run->Manifest, I've changed the "Android target SDK" and the "arm" level on the left to the following combos:

- sdk 7 / arm 5
- sdk 7 / arm 7a
- sdk 8 / arm 5
- sdk 8 / arm 7a
- sdk 10 / arm 5
- sdk 10 / arm 7a

Note: In both arm 5 and arm 7a, these were "Debug" modes.

Anybody have any idea why the debugger *still" won't go past "Setting breakpoints" ?

Thanks!
-Josiah