Strange hang when calling signal()

[Gleb Popov]

On Thu, Oct 4, 2018 at 11:21 AM Konstantin Belousov <kostikbel at gmail.com>
wrote:

> On Thu, Oct 04, 2018 at 10:56:41AM +0300, Gleb Popov wrote:
> > On Thu, Oct 4, 2018 at 12:34 AM Konstantin Belousov <kostikbel at gmail.com
> >
> > wrote:
> >
> > > On Wed, Oct 03, 2018 at 03:18:12PM +0300, Gleb Popov wrote:
> > > > I failed to extract a reproducing testcase from that test. The
> extracted
> > > > code works fine, so either I missed something, or some hidden
> conditions
> > > > must be fulfilled for the bug to appear.
> > > >
> > > > Maybe I can try to dive into libc myself? Can you give me some
> guidance?
> > > Or
> > > > maybe you just build kdevelop yourself? It is a matter of handful of
> > > > commands.
> > >
> > > Can you provide me the minimal self-contained set of binaries and
> shared
> > > libraries and the instruction to reproduce the issue ?
> > >
> >
> > Pull in all needed depndencies
> > # pkg install kdevelop gmake cmake git
> >
> > Get KDevelop sources
> > # git clone git://anongit.kde.org/kdevelop.git
> >
> > # Build the test executable
> > # mkdir kdevelop/build
> > # cd kdevelop/build
> > # cmake ..
> > # gmake -j4 test_qthelpplugin
> >
> > Run the test executable and see that it hangs
> > # ./plugins/qthelp/tests/test_qthelpplugin testDefaultValue
> This is exactly the opposite of 'minimal'.  Provide me the tarball which
> have just the binary and non-base shared libs needed to reproduce.
>
> I am not going to install kde on my crash boxes.
>

Ok, can do that, but

# ldd ./plugins/qthelp/tests/test_qthelpplugin | wc -l

gives 286. Would that suit you?