[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Please comment out constants in header files for features not being

From: Samuel Thibault
Subject: Re: Please comment out constants in header files for features not being supported yet. And remove stubs??
Date: Fri, 18 Dec 2020 12:12:01 +0100
User-agent: NeoMutt/20170609 (1.8.3)

Svante Signell, le ven. 18 déc. 2020 11:58:53 +0100, a ecrit:
> On Thu, 2020-12-17 at 17:11 +0100, Samuel Thibault wrote:
> > Svante Signell, le jeu. 17 déc. 2020 15:54:28 +0100, a ecrit:
> > > # define CLOCK_REALTIME_COARSE          5
> > > 
> > > The problem with that option is that it is not yet supported,
> > > resulting in EINVAL and a crash message on the console:
> > > /hurd/crash: host <address> crashed ...
> > 
> > We could comment this out indeed.
> > 
> > But the program assuming that "it's defined so it works" is
> > completely bogus on Linux as well: one may run an application built
> > against a recent libc, on an old Linux kernel...
> You are right, but how common is this combination?

For this precise combination, it's non-existing, but the principle still

> BTW: Any ideas about the second crash written about in my previous mail
> that you edited away?

What second crash? I only see one gdb session. There is first a SIGTRAP,
which is used by gdb for its own debugging purpose, then a SIGABRT. The
second signal is very probably just a consequence of bad interaction
between the program and gdb on the SIGTRAP. Thus why rather working on a
core file.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]