[lldb-dev] Failing LIT-based lldb-mi tests

Александр Поляков via lldb-dev lldb-dev at lists.llvm.org
Tue Aug 14 14:56:27 PDT 2018


Yes, it is. Here is the gdb-remote process log:

(gdb)
-file-exec-and-symbols "a.out"
^done
(gdb)
^done
(gdb)
=library-loaded,id="/home/alexander/workspace/gsoc/a.out",target-name="/home/alexander/workspace/gsoc/a.out",host-name="/home/alexander/workspace/gsoc/a.out",symbols-loaded="0",loaded_addr="-",size="0"
^done
(gdb)
^done
(gdb)
^done
(gdb)
^done
(gdb)
^done
(gdb)
^done
(gdb)
^done
(gdb)
^done
(gdb)
^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x000000000040051f",func="main",file="main.c",fullname="/home/alexander/workspace/gsoc/main.c",line="2",times="0",original-location="main"}
(gdb)
=breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x000000000040051f",func="main",file="main.c",fullname="/home/alexander/workspace/gsoc/main.c",line="2",times="0",original-location="main"}
(gdb)
^done
(gdb)
lldb-mi          ProcessGDBRemote::DoLaunch() entered
lldb-mi          ProcessGDBRemote::DoLaunch provided with STDIO paths via
launch_info: stdin=/dev/pts/3, stdout=/dev/pts/3, stderr=/dev/pts/3
lldb-mi
GDBRemoteCommunication::StartDebugserverProcess(url=<empty>, port=0)
lldb-mi          GDBRemoteCommunication::StartDebugserverProcess() found
gdb-remote stub exe '/home/alexander/workspace/gsoc/build/bin/lldb-server'
lldb-mi          launch info for gdb-remote stub:
Executable: lldb-server
Triple: *-*-*
Arguments:
argv[0]="/home/alexander/workspace/gsoc/build/bin/lldb-server"
argv[1]="gdbserver"
argv[2]="--fd=5"
argv[3]="--native-regs"
argv[4]="--setsid"
argv[5]=NULL

Environment:
env[USER] = alexander
env[XAUTHORITY] = /run/user/1000/gdm/Xauthority
env[LOGNAME] = alexander
env[DEFAULTS_PATH] = /usr/share/gconf/gnome.default.path
env[XDG_RUNTIME_DIR] = /run/user/1000
env[LC_PAPER] = ru_RU.UTF-8
env[HOME] = /home/alexander
env[GIT_EDITOR] = vim
env[OLDPWD] = /home/alexander
env[XDG_DATA_DIRS] =
/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
env[LC_NAME] = ru_RU.UTF-8
env[LS_COLORS] =
rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
env[TILIX_ID] = 6ddac5a9-51b9-4cfa-9eb4-6d0b34d0f04d
env[XMODIFIERS] = @im=ibus
env[LC_MONETARY] = ru_RU.UTF-8
env[GNOME_DESKTOP_SESSION_ID] = this-is-deprecated
env[GTK_IM_MODULE] = ibus
env[LANG] = en_US.UTF-8
env[QT_LINUX_ACCESSIBILITY_ALWAYS_ON] = 1
env[XDG_CONFIG_DIRS] = /etc/xdg/xdg-gnome:/etc/xdg
env[SSH_AUTH_SOCK] = /run/user/1000/keyring/ssh
env[XDG_SESSION_ID] = 1
env[LC_TELEPHONE] = ru_RU.UTF-8
env[LC_ADDRESS] = ru_RU.UTF-8
env[LC_MEASUREMENT] = ru_RU.UTF-8
env[SHELL] = /bin/bash
env[TERM] = xterm-256color
env[MANDATORY_PATH] = /usr/share/gconf/gnome.mandatory.path
env[CLUTTER_IM_MODULE] = xim
env[DBUS_SESSION_BUS_ADDRESS] =
unix:abstract=/tmp/dbus-oNfLOnXWYU,guid=f7166ac689c7f7e4acb976a25b72be95
env[USERNAME] = alexander
env[LC_NUMERIC] = ru_RU.UTF-8
env[XDG_MENU_PREFIX] = gnome-
env[WINDOWPATH] = 2
env[XDG_SESSION_TYPE] = x11
env[SHLVL] = 1
env[LESSOPEN] = | /usr/bin/lesspipe %s
env[PWD] = /home/alexander/workspace/gsoc
env[LESSCLOSE] = /usr/bin/lesspipe %s %s
env[XDG_SEAT] = seat0
env[QT4_IM_MODULE] = xim
env[DISPLAY] = :1
env[SSH_AGENT_PID] = 2049
env[LC_IDENTIFICATION] = ru_RU.UTF-8
env[GDMSESSION] = gnome
env[LC_TIME] = ru_RU.UTF-8
env[SESSION_MANAGER] = local/asus-k551:@
/tmp/.ICE-unix/1976,unix/asus-k551:/tmp/.ICE-unix/1976
env[GTK_MODULES] = gail:atk-bridge
env[XDG_SESSION_DESKTOP] = gnome
env[XDG_CURRENT_DESKTOP] = GNOME
env[_] = build/bin/lldb-mi
env[XDG_VTNR] = 2
env[QT_ACCESSIBILITY] = 1
env[PATH] =
/home/alexander/firmware/arc/arcanist/bin:/home/alexander/bin:/home/alexander/.local/bin:/home/alexander/firmware/arc/arcanist/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
env[VTE_VERSION] = 4205
env[GIO_LAUNCHED_DESKTOP_FILE_PID] = 2133
env[GIO_LAUNCHED_DESKTOP_FILE] =
/etc/xdg/autostart/gnome-settings-daemon.desktop
env[DESKTOP_SESSION] = gnome
env[QT_IM_MODULE] = ibus

lldb-mi          ProcessGDBRemote::StartAsyncThread ()
b-remote.async>  ProcessGDBRemote::AsyncThread (arg = 0x1083930, pid = 0)
thread starting...
b-remote.async>  ProcessGDBRemote::AsyncThread (arg = 0x1083930, pid = 0)
listener.WaitForEvent (NULL, event_sp)...
lldb-mi          ProcessGDBRemote::DoLaunch adjusted STDIO paths for local
platform (IsHost() is true) using slave: stdin=/dev/pts/3,
stdout=/dev/pts/3, stderr=/dev/pts/3
lldb-mi          ProcessGDBRemote::DoLaunch final STDIO paths after all
adjustments: stdin=/dev/pts/3, stdout=/dev/pts/3, stderr=/dev/pts/3
lldb-mi          failed to connect to debugserver: 'A' packet returned an
error: -1
^error,msg="process launch failed: 'A' packet returned an error: -1"
(gdb)
^done
(gdb)
^done
(gdb)
^error,msg="Command 'exec-step-instruction'. Thread ID invalid"
(gdb)
^done
(gdb)
^done
(gdb)
^error,msg="Command 'exec-next-instruction'. Thread ID invalid"
(gdb)
it4(pid=10146)>  ProcessGDBRemote::MonitorDebugserverProcess(process_wp,
pid=10146, signo=2 (0x2), exit_status=-1)
^done
it4(pid=10146)>  ProcessGDBRemote::MonitorDebugserverProcess(process =
0x1083930)
(gdb)
^done
(gdb)
^error,msg="this SBThread object is invalid"
(gdb)
^done
(gdb)
^done
(gdb)
^done
(gdb)
lldb-mi          ProcessGDBRemote::StopAsyncThread ()
b-remote.async>  ProcessGDBRemote::AsyncThread (arg = 0x1083930, pid = 0)
Got an event of type: 2...
b-remote.async>  ProcessGDBRemote::AsyncThread (arg = 0x1083930, pid = 0)
got eBroadcastBitAsyncThreadShouldExit...
b-remote.async>  ProcessGDBRemote::AsyncThread (arg = 0x1083930, pid = 0)
thread exiting...

On Wed, Aug 15, 2018 at 12:49 AM Adrian Prantl <aprantl at apple.com> wrote:

>
>
> On Aug 14, 2018, at 2:43 PM, Александр Поляков <polyakov.alx at gmail.com>
> wrote:
>
> Here is what I got from gdb-remote packet log:
>
> (gdb)
> lldb-mi          <   1> send packet: +
> lldb-mi          history[1] tid=0x784a <   1> send packet: +
> lldb-mi          <  19> send packet: $QStartNoAckMode#b0
> lldb-mi          <   1> read packet: +
> lldb-mi          <   6> read packet: $OK#9a
> lldb-mi          <   1> send packet: +
> lldb-mi          <  41> send packet:
> $qSupported:xmlRegisters=i386,arm,mips#12
> lldb-mi          < 124> read packet:
> $PacketSize=20000;QStartNoAckMode+;QThreadSuffixSupported+;QListThreadsInStopReply+;qEcho+;QPassSignals+;qXfer:auxv:read+#be
> lldb-mi          <  26> send packet: $QThreadSuffixSupported#e4
> lldb-mi          <   6> read packet: $OK#9a
> lldb-mi          <  27> send packet: $QListThreadsInStopReply#21
> lldb-mi          <   6> read packet: $OK#9a
> lldb-mi          <  13> send packet: $qHostInfo#9b
> lldb-mi          <  11> send packet: $qEcho:1#5b
>
> Could somebody help me with understanding of what is happening here?
>
>
> Just to clarify: Is this from a session that failed with the symptoms you
> described earlier?
> I'm not familiar with the protocol, but the fact that there are send and
> read log entries makes it sound like the communication itself is working.
>
> -- adrian
>


-- 
Alexander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20180815/2b668f55/attachment-0001.html>


More information about the lldb-dev mailing list