Thursday 15 August 2013

osx - Xcode lldb error in lauch program -


"itemprop =" text ">

I get a smilar error when I launch the application from xcode (c ++ command line), right from the application (terminal) Try.

I tried to answer the above questions but none of them helped me in the solution.

The problem I found in the end is LLDB Using GDB is working fine then I use lLDB to debug my program and default config in xcode

The error is in the following lldb function.

  error PlatformRemoteGDBServer :: LaunchProcess (ProcessLaunchInfo & amp; launch_info) {error error; lldb :: pid_t PID M = Test (eLaunchFlagDisableASLR) const char * work_dir = launch_info.GetWorkingDirectory (); if (functional & amp; Amp; Work_dir [0]) {m_gdb_client.SetWorkingDir (work_dir);} // Send environment after Ment and program + logic we connect const char ** argv = launch_info.GetArguments (). GetConstArgumentVector (); Const char ** envp = launch_info.GetEnvironmentEntries (). GetConstArgumentVector (); If (envp) {const char * env_entry; For (int i = 0; (env_entry = envp [i]); ++ i) {if (m_gdb_client.SendEnvironmentPacket (env_entry) = 0!) Break; }} Const uint32_t old_packet_timeout = m_gdb_client.SetPacketTimeout (5); Int arg_packet_err = m_gdb_client.SendArgumentsPacket (argv); M_gdb_client.SetPacketTimeout (old_packet_timeout); If (arg_packet_err == 0) {std :: string error_str; If (m_gdb_client.GetLaunchSuccess (error_str)) {pid = m_gdb_client.GetCurrentProcessID (); If (pid! = LLDB_INVALID_PROCESS_ID) launch_info.SetProcessID (pid); } And {error.SetErrorString (error_str.c_str ()); }} And {** error.SetErrorStringWithFormat ("** 'A' packet returned an error:% i", ** arg_packet_err); **} Return error; }   

As you can see the 'A' packet error is in lldb Now the question is how can this fix the problem? Is there a way to reset / reconfigure the LLDB in Xcode? Can anyone say the problem with the LDD function.

I am using the latest Mac OS + Xcode 4.6.3 latest

please share your thoughts

This error occurs when the debugserver can not start the app you are trying to debug. Launches, engages, stops, inspects and controls debugserver processes - it is a small program with all these responsibilities. It contacts LLDB (possibly inside the xcode) via "GDB Remote Protocol" with some small extensions.

If you have created your own LLDB, then it is likely that debugger is not a code signed properly, so this app can not launch.

If you have changed your / etc / hosts file, check that you have a line like 127.0.0.1 localhost there Some people have modified their / etc / hosts (I do not know why) and this line has been removed, and it creates problems for lldb in an attempt to communicate with DDbServer Are of

Otherwise, check to see if a useful message is logged in Console.app to see the output.

No comments:

Post a Comment