Debian Bug report logs -
#323425
implicitly converted pointers
Reported by: dann frazier <dannf@hp.com>
Date: Tue, 16 Aug 2005 17:18:09 UTC
Severity: important
Found in version cronolog/1.6.2-5
Fixed in version cronolog/1.6.2-5.1
Done: Kurt Roeckx <kurt@roeckx.be>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded to debian-bugs-dist@lists.debian.org, Joel Baker <fenton@debian.org>:
Bug#323425; Package cronolog.
(full text, mbox, link).
Acknowledgement sent to dann frazier <dannf@hp.com>:
New Bug report received and forwarded. Copy sent to Joel Baker <fenton@debian.org>.
(full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: cronolog
Version: 1.6.2-5
Severity: important
Tags: patch
Our automated buildd log filter[1] detected a problem[2] that will cause
your package to segfault on architectures where the size of a pointer is
greater than the size of an integer, such as ia64.
_XOPEN_SOURCE must be defined when using the strptime() function. See
strptime(3) for details. There might be a more autoconfy patch, but
this one works.
[1]http://people.debian.org/~dannf/check-implicit-pointer-functions
[2]Function `strptime' implicitly converted to pointer at cronoutils.c:673
--- cronolog-1.6.2/src/Makefile.in~ 2001-05-04 03:02:03.000000000 -0600
+++ cronolog-1.6.2/src/Makefile.in 2005-08-16 11:11:19.000000000 -0600
@@ -95,7 +95,7 @@
cronolog_LDFLAGS =
SCRIPTS = $(sbin_SCRIPTS)
-CFLAGS = @CFLAGS@
+CFLAGS = @CFLAGS@ -D_XOPEN_SOURCE
COMPILE = $(CC) $(DEFS) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
CCLD = $(CC)
LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(LDFLAGS) -o $@
Information forwarded to debian-bugs-dist@lists.debian.org, Joel Baker <fenton@debian.org>:
Bug#323425; Package cronolog.
(full text, mbox, link).
Acknowledgement sent to dann frazier <dannf@hp.com>:
Extra info received and forwarded to list. Copy sent to Joel Baker <fenton@debian.org>.
(full text, mbox, link).
Message #10 received at 323425@bugs.debian.org (full text, mbox, reply):
As these bugs have been open for a month without a response from the
maintainers, I plan to NMU these packages in 1 week (or sooner, at the
maintainers' request).
Tags added: fixed
Request was from dann frazier <dannf@debian.org>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Joel Baker <fenton@debian.org>:
Bug#323425; Package cronolog.
(full text, mbox, link).
Acknowledgement sent to Joel Aelwyn <fenton@debian.org>:
Extra info received and forwarded to list. Copy sent to Joel Baker <fenton@debian.org>.
(full text, mbox, link).
Message #17 received at 323425@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
tags 323425 -patch
done
dann frazier wrote:
> Package: cronolog
> Version: 1.6.2-5
> Severity: important
> Tags: patch
>
> Our automated buildd log filter[1] detected a problem[2] that will cause
> your package to segfault on architectures where the size of a pointer is
> greater than the size of an integer, such as ia64.
>
> _XOPEN_SOURCE must be defined when using the strptime() function. See
> strptime(3) for details. There might be a more autoconfy patch, but
> this one works.
>
> [1]http://people.debian.org/~dannf/check-implicit-pointer-functions
> [2]Function `strptime' implicitly converted to pointer at cronoutils.c:673
I have applied a fix to the package, and stand duly chastized for having
failed to follow up on it in a more useful fashion. Mea culpa. However, the
patch provided is not the most appropriate way to fix the problem; since it
involves adding a -D flag to CFLAGS, this is perfectly capable of happening in
the debian/rules file, rather than requiring a source patch (I guess you could
call that 'more autoconfy'; certainly, it seems cleaner).
However, since I have changed the behavior, it would be helpful if I could
arrange to validate that the -6 package will, in fact, correctly solve this
problem on a 64-bit architecture. Since I don't particularly trust that I can
verify this sufficiently, myself, would it be possible to get a test build
verified in some fashion?
--
Joel Aelwyn <fenton@debian.org> ,''`.
: :' :
`. `'
`-
[signature.asc (application/pgp-signature, attachment)]
Tags removed: patch
Request was from Joel Aelwyn <fenton@debian.org>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Joel Baker <fenton@debian.org>:
Bug#323425; Package cronolog.
(full text, mbox, link).
Acknowledgement sent to dann frazier <dannf@hp.com>:
Extra info received and forwarded to list. Copy sent to Joel Baker <fenton@debian.org>.
(full text, mbox, link).
Message #24 received at 323425@bugs.debian.org (full text, mbox, reply):
On Mon, 2005-11-14 at 23:28 -0700, Joel Aelwyn wrote:
> tags 323425 -patch
> done
>
> dann frazier wrote:
> > Package: cronolog
> > Version: 1.6.2-5
> > Severity: important
> > Tags: patch
> >
> > Our automated buildd log filter[1] detected a problem[2] that will cause
> > your package to segfault on architectures where the size of a pointer is
> > greater than the size of an integer, such as ia64.
> >
> > _XOPEN_SOURCE must be defined when using the strptime() function. See
> > strptime(3) for details. There might be a more autoconfy patch, but
> > this one works.
> >
> > [1]http://people.debian.org/~dannf/check-implicit-pointer-functions
> > [2]Function `strptime' implicitly converted to pointer at cronoutils.c:673
>
> I have applied a fix to the package, and stand duly chastized for having
> failed to follow up on it in a more useful fashion. Mea culpa. However, the
> patch provided is not the most appropriate way to fix the problem; since it
> involves adding a -D flag to CFLAGS, this is perfectly capable of happening in
> the debian/rules file, rather than requiring a source patch (I guess you could
> call that 'more autoconfy'; certainly, it seems cleaner).
>
> However, since I have changed the behavior, it would be helpful if I could
> arrange to validate that the -6 package will, in fact, correctly solve this
> problem on a 64-bit architecture. Since I don't particularly trust that I can
> verify this sufficiently, myself, would it be possible to get a test build
> verified in some fashion?
Of course - you could either post a source package for me, or log into
merulo and perform a build and run the log through the above script.
--
dann frazier <dannf@hp.com>
Tags removed: fixed
Request was from Kurt Roeckx <kurt@roeckx.be>
to control@bugs.debian.org.
(Sun, 21 Sep 2008 13:00:10 GMT) (full text, mbox, link).
Bug marked as fixed in version 1.6.2-5.1, send any further explanations to dann frazier <dannf@hp.com>
Request was from Kurt Roeckx <kurt@roeckx.be>
to control@bugs.debian.org.
(Sun, 21 Sep 2008 13:00:10 GMT) (full text, mbox, link).
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Mon, 20 Oct 2008 07:28:13 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Tue Jul 16 11:47:11 2024;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.