My application in working fine in Samsung BADA simulator but not working in device. My application is for S8500, available for download https://sourceforge.net/projects/wavechm/ with source code. I don't know what to do now?
please see the video of application how it is behaving. I have no idea what to do next. It is open source project and I do lot of hardwork and getting no result.
http://developer.bada.com/badaforum/board/thread/view.do?boardName=ide-sdk&messageId=24162&frm=1
I tried to run this app on phone
6,0,0,1,2011-05-13,02:10:27.578,1|5
Transfer completed.
The "COM5" port is closed.
The "COM5" port is open.
Command message: [1600:1601]EnableDiagWrite
Command message: [1600:1601]TerminateProcessEx feu46uenau 0
Command message: [1600:1601]AppPkgInstall /Osp/Applications/feu46uenau
Command message: [0:2]MID_PROCESSMGR,0xFF
3,0,0,1,2011-05-13,02:10:29.421,00004|10:47:85|PHONESTATUS:04> app installed, errType=0
Installation completed.
2,0,0,1,2011-05-13,02:10:29.421,Info, Installation completed.
The "COM5" port is closed.
6,0,0,1,2011-05-13,02:10:31.953,2|1|5
2,0,0,1,2011-05-13,02:10:37.406,0072.217,EXCEPTION,P28,T00,A119,Osp::Ui::Controls::Popup::Show (689) > [E_SYSTEM] Unable to show itself.
The "COM6" port is closed.
It is short log. App crashed and broke os too. (didn't stop in IDE)
Let me know which details you need. I try to help.
Related
I'm trying to run a Qt d-bus example (chat) on Windows. It compiles fine but I get this error:
Cannot connect to the D-Bus session bus. Please check your system
settings and try again. QEventDispatcherWin32::wakeUp: Failed to post
a message
I installed D-Bus on Windows through a ready made installer found in Google archives.
Can someone give me an idea how to run dbus-daemon on Windows?
On my server I am using Chromedp (a Go package) that runs a headless version of chrome to generate PDFs for me.
When I run this process on my windows machine it works great. Then when I try to run it on my Amazon Linux AMI server I always get the error message "context cancelled"
I asked on their github page if that was an issue with something I was doing and I was told that it might be happening if the browser crashes or fails to start.
How can I verify that my version of chrome is working through the command line?
I followed this guide when I was installing chrome.
This is relatively minor, and I wasn't able to find any other record of this issue, but it cost me several stressful hours. I'm considering opening an Appcelerator Jira ticket about this bug, so any feed back is welcome before I do so. Questions: Are there any other workarounds besides what I wrote below? What are some better ways to log the actual error?
Environment
Titanium SDK: 7.0.2.GA
Javascript Engine: V8
Platform & version: iOS 11.2
Device Details: iOS simulator (iPhone 7+)
Host Operating System: OS X 10.13 64 bit
Node Version: 7.10.0
Titanium CLI: 5.0.14
Npm Version: 4.2.0
Description
When building an iOS app and there is an issue connecting to the iOS log-server, it always output "Another process is currently bound to port xxxxx" even if there is another server connection issue such as the port not existing.
Workaround
Figure out the real issue by logging the actual error within the sdk itself (at ~/Library/Application Support/Titanium/mobilesdk/osx/7.0.2.GA/iphone/cli/commands/_build.js in the determineLogServerPort function).
Steps to Reproduce
Create a different type of error with the server. For example, my /etc/hosts file did not have an entry for 127.0.0.1 localhost, so the actual node error was 'ENOTFOUND'.
Create a new titanium app with appc ti new.
Build with appc ti build -p ios
Actual Result
Build errors out with following text:
[ERROR] Another process is currently bound to port 27973
[ERROR] Set a unique <log-server-port> between 1024 and 65535 in the <ios> section of the tiapp.xml
Expected Result
More detailed error. I.E. Something like:
Failed to create/connect to log server port with error "[error given by node net package]".
Followed by suggested solution. For example if the node error was EADDRINUSE, then you could still use the existing error message. But if it's another error, log accordingly so the user has the best information for solving the issue.
Close current emulator running and try again
when emulator was opened by xcode, I got such issue
Please make sure you are executing the app with same App name and ID.
If there is a change, please delete the app from device and retake the build.
I opened the ticket with appcelerator here: https://jira.appcelerator.org/browse/TIMOB-25872
They have just marked it as closed so it will hopefully be included in the next sdk version.
The solution for me was what was mentioned as a solution in the JIRA ticket on appcelerator https://jira.appcelerator.org/browse/TIMOB-25872.
I had recently moved to a new Mac and migrated everything, it created a copy of my host file renaming it but didn't update main one so it had no reference to the localhost in there. Once this was fixed it was building no problem again.
Below is what is in the host file.
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
Hope that helps someone, didn't see the answer on JIRA at first glance.
I've been setting up remote debugging for an embedded Linux target. I've tested that I have the correct combination of gdbserver running on the target and gdb client running on my workstation. I can start the server and on the workstation side run:
(gdb) target remote 10.28.22.226:2345
and I can list source and step just fine.
In Qt Creator I have configured a device. In that window I specify the GDB server executable: gdbserver (see pic).
I also configure the cross debugger in the 'Build & Run' Debuggers tab as shown below:
In this case, I have manually started the gdbserver with my executable on the target with port 2345. To start debugging with Qt Creator, I choose the Debug->Start Debugging->Attach to running Debug server pulldown menu. It gives me the prompt shown below, where I enter the server port (2345). I give it the appropriate kit and local executable (copy of the executable on the remote target).
After I hit OK, it seems to run the gdb client locally with a few commands, then times out trying to communicate with the gdbserver. I have debug logging turned on with the server, so I know the server never sees anything from the client run from Qt Creator. Additionally, I did Window->Views->Debugger Log to help me get a better idea of what was going on. The log shows the correct IP address and port for my device, but I don't see anything that looks like a 'target remote IP:port' call.
I'm looking for a hint or reference here. I seem to be a bit stuck at the moment. Thanks!
EDIT: additional information - I've verified that my gdb client has support for python compiled in. I see that Qt Creator requires python support. I also have further support that nothing ever goes out on the wire from Qt Creator. I did a wireshark capture and don't see anything going to port 2345 on the target.
Alternately, if anyone would share their Qt Creator debugger-log output with me so I can compare, that would be helpful.
Avoid Qt Creator 4.5-beta1. It seems 4.5RC1 doesn't have this problem. I was able to do remote debugging using the method described above just fine.
Even QtCreator 4.5.0 seems to have the same bug.
The only workaround I've found is to start the GDB server manually on the remote target: with "top" I get the pid of the remote process to debug then I run the following command: gdbserver --attach remote ip:remote port pid.
After the server is listening, I finally choose: "Attach to Running Debug" server".
Maybe you can write a server start script on target which include the above statement...
I followed the steps in this link
and I manage to debug a binary which resides in linux host from my windows machine from command prompt.
I have gdbserver in linux and I installed gdb with the help of mingw in windows. As I told I can prompt "target remote x.x.x.x:10000 test" to command in windows and debug my test application.
My problem is I can't do the same with eclipse gui, it seems to me it has tones of buttons, options but they make no sense to me.
I am choosing debug_configurations-->C/C++ Remote Application(the only one which allows me to input linux machine ip/port), in "Main" tab to connection I am inputting my linux ip. In same menu under Debugger tab I am inputting my window's gdb path and gdbserver port.
After doing all those I believe I gave enough info to eclipse for connect gdb server but it never enough for eclipse. I am checking gdbserver logs by starting gdbserver with --debug, gdbserver never gets triggered, it does not writes a single line of log. Eclipse even does not starts a connection. But instead it gives me a error like "Error during file upload." which makes no sense to me.
I am using "Eclipse Version: Juno Service Release 2" . Any help will be appreciated .
I believe that the "C/C++ Remote Application" option uses Eclipse's RDT (Remote Development Tools) and RSE (Remote System Explorer) to connect, upload, execute, and debug the application itself. It
If all you want to do is connect to a gdbserver, then create a "C/C++ Attach to Application" debug configuration, and under the Debugger tab, set Debugger to gdbserver.
I also encountered this error message for other reason on Eclipse version 2019-09 R (4.13.0).
I very recommend to read paragraph "How do I debug a remote application?" from this great guide.
It explains which of three remote debugging options you should be using - Automatic Remote Launcher, Manual Remote Launcher and Remote Attach Launcher and how to use each one.
I was using the wrong launcher and hence got the error, while on the remote side gdbserver was listening and waiting for a connection. Switching to Manual Remote Launcher solved it.
for example it says:
If you don't have RSE installed, you cannot use the "Automatic Remote
Launch"
RSE = Remote System Explorer End-User Runtime
Launcher setting is configured from the bottom of the Remote Debug Configuration window - "Using GDB (DSF) Automatic/Manual Remote Debugging Launcher".