lldb doesn't show full stacktrace

[Quuxplusone]

Bugzilla Link	PR19784
Status	NEW
Importance	P normal
Reported by	Ivan Sorokin (vanyacpp@gmail.com)
Reported on	2014-05-18 10:28:53 -0700
Last modified on	2014-05-19 09:28:25 -0700
Version	unspecified
Hardware	PC Linux
CC	tfiala@google.com
Fixed by commit(s)
Attachments
Blocks
Blocked by
See also

Ubuntu 14.04 64-bit. lldb-3.5 rev.201651 (packaged in Ubuntu).

lldb doesn't show full stacktrace for some functions. E.g.

(gdb) bt
#0  0x00007ff38991ffbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ff38846afe4 in g_main_context_poll (priority=2147483647, n_fds=5,
fds=0x11cbf60, timeout=550, context=0x7ff3800011f0)
    at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:4028
#2  g_main_context_iterate (context=context@entry=0x7ff3800011f0,
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3729
#3  0x00007ff38846b0ec in g_main_context_iteration (context=0x7ff3800011f0,
may_block=1) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3795
#4  0x00007ff38a5c27a1 in QEventDispatcherGlib::processEvents (this=0x10ecca0,
flags=...) at kernel/qeventdispatcher_glib.cpp:434
#5  0x00007ff38aeb0bb6 in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#6  0x00007ff38a5940af in QEventLoop::processEvents
(this=this@entry=0x7fff20b93920, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007ff38a5943a5 in QEventLoop::exec (this=this@entry=0x7fff20b93920,
flags=...) at kernel/qeventloop.cpp:204
#8  0x00007ff38a599b79 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1225
#9  0x0000000000626dac in main (argc=1, argv=0x7fff20b940c8) at main.cpp:387

(lldb) bt
* thread #1: tid = 14148, 0x00007ff38991ffbd libc.so.6`__poll + 45, name =
'qbittorrent', stop reason = trace
  * frame #0: 0x00007ff38991ffbd libc.so.6`__poll + 45

The same issue applies to many other functions in libc.

[Quuxplusone]

Hi Ivan,

Can I get you to tell me the exe you are using and the way to produce it so I
can replicate your setup?  I'd like to look into the libc poll backtrace
failure with an identical setup to yours.

Thanks!

Sincerely,
Todd Fiala

[Quuxplusone]

(In reply to comment #1)

> Can I get you to tell me the exe you are using and the way to produce it so
> I can replicate your setup?  I'd like to look into the libc poll backtrace
> failure with an identical setup to yours.

In my case it was qbittorrent compiled from branch
https://github.com/sorokin/qBittorrent/tree/alerts. But I think you can
reproduce this problem on any Qt program (qbittorrent doesn't do anything
special).

[Quuxplusone]

(In reply to comment #2)
> (In reply to comment #1)
>
> > Can I get you to tell me the exe you are using and the way to produce it so
> > I can replicate your setup?  I'd like to look into the libc poll backtrace
> > failure with an identical setup to yours.
>
> In my case it was qbittorrent compiled from branch
> https://github.com/sorokin/qBittorrent/tree/alerts. But I think you can
> reproduce this problem on any Qt program (qbittorrent doesn't do anything
> special).

Ok - thanks, Ivan!  I'll use that when I look into this.