One crash location found (con.c line 393), reference through null pointer:
[cid:image001.png@01D0A9AA.222B9380]


I3-with-shmlog is indeed the process to attach to. I started i3 clean, and then 
as root I was able to attach to this process. For some reason, though i3 is 
running as ubuntu, I was not able to attach as ubuntu. Once attached, I then 
initiated the sequence of events that I expected to crash i3, the crash did 
indeed occur (so this is quite repeatable).

I'll continue to see if I can isolate other crash points.

I'll post a bug on the bug tracker to ensure that this hits Michael's radar.





From: Sargrad, Dave
Sent: Thursday, June 18, 2015 9:16 AM
To: 'i3-discuss@i3.zekjur.net'
Subject: i3 4.10.2 crash

I3 4.10.2 has crashed on me. I've seen crashes before but have ignored them. 
I'm interested in seeing if I can isolate the crash, particularly since I think 
I know how to repeat the crash. Once isolated I can provide feedback to the dev 
team.

I am currently presented with the "crash response window" (red border with 
options to: attach gdb, save a backtracke, restart i3 in place, forget the 
current layout and restart i3).

When I putty into the box and see what i3 processes are running (with an eye 
towards attaching gdb), I see the following:

ubuntu@sensis-8930:~$ ps -aef | grep i3
ubuntu    2349  2075  0 Jun17 ?        00:00:01 i3-with-shmlog
ubuntu    2420  2349  0 Jun17 ?        00:00:00 /usr/bin/ssh-agent 
/usr/bin/dbus                                                      -launch 
--exit-with-session /usr/bin/im-launch i3-with-shmlog
ubuntu    2423     1  0 Jun17 ?        00:00:00 /usr/bin/dbus-launch 
--exit-with                                                      -session 
/usr/bin/im-launch i3-with-shmlog
ubuntu    2484     1  0 Jun17 ?        00:00:00 /bin/sh -c i3bar --bar_id=bar-0 
                                                      
--socket="/run/user/1000/i3/ipc-socket.2349"
ubuntu    2485  2484  0 Jun17 ?        00:00:29 i3bar --bar_id=bar-0 
--socket=/r                                                      
un/user/1000/i3/ipc-socket.2349
ubuntu    2487  2485  0 Jun17 ?        00:00:00 /bin/sh -c i3status
ubuntu    2489  2487  0 Jun17 ?        00:00:24 i3status
ubuntu    2510     1  0 Jun17 ?        00:00:00 /bin/sh -c i3-sensible-terminal
ubuntu    6031  6005  0 12:12 pts/1    00:00:00 grep --color=auto i3


The area that I built i3 out of is:  /home/ubuntu/work/i3/i3-4.10.2

This is where I should be able to find the source code and symbol files 
required by gdb.

I've attached gdb to debuggable processes in the past (I don't need help with 
that). I do need some guidance relative to the following questions:
1] If I save a backtrace, where will that get saved on the system
2] Of the processes listed above, which one do I attach to (I don't see i3.. 
perhaps i3-with-shmlog)?
3] What are the commands that I should enter into gdb so that it loads the 
proper symbol files?

Thanks for any thoughts or guidance.

ubuntu@sensis-8930:~/work/i3$ ls
i3-4.10.2  i3-4.10.2.tar.bz2  i3status-2.9  i3status-2.9.tar.bz2


This message is intended only for the addressee and may contain information 
that is company confidential or privileged. Any technical data in this message 
may be exported only in accordance with the U.S. International Traffic in Arms 
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be 
unlawful. If you are not the intended recipient, or the person responsible for 
delivering to the intended recipient, you should not read, copy, disclose or 
otherwise use this message. If you have received this email in error, please 
delete it, and advise the sender immediately.

Reply via email to