Your message dated Fri, 13 Jan 2017 13:43:18 +0100
with message-id <20170113124318.gh16...@an3as.eu>
and subject line Re: Bug#747185: Do the conflicting return types of function 
DejaVu_create exist in new upstream version?
has caused the Debian Bug report #747185,
regarding Conflicting return types of function DejaVu_create
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
747185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exonerate
Version: 2.2.0-6
Usertags: goto-cc

During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder)
the build failed with the following error. Please note that we use our research
compiler tool-chain (using tools from the cbmc package), which permits extended
reporting on type inconsistencies at link time.

error: conflicting function declarations "DejaVu_create"
old definition in module bsam file ../../src/struct/dejavu.h line 42
DejaVu *DejaVu_create(gchar *seq, gint len)
new definition in module dejavu file dejavu.c line 26
DejaVu *DejaVu_create(gchar *seq, gint len)

reason for conflict at nil.symbol_list in types listed below (array/array):

signed int [2048]
signed int [256]

This is with the following code in dejavu.h:

http://sources.debian.net/src/exonerate/2.2.0-6/src/struct/dejavu.h?hl=26,27,28,30,31,32,33,34,35,36#L26

#ifndef ALPHABET_SIZE
#define ALPHABET_SIZE (1 << CHAR_BIT)
#endif /* ALPHABET_SIZE */

typedef struct {
       gchar *seq;
        gint  len;
        gint *next;
        gint  symbol_list[ALPHABET_SIZE];
        gint  symbol_list_len;
} DejaVu;

Unfortunately, however, a cruel mix of definitions is used for ALPHABET_SIZE
throughout the codebase of exonerate:

http://codesearch.debian.net/search?q=package%3Aexonerate+ALPHABET_SIZE

Any code relying on the size of the symbol_list array will break as it will
access invalid memory; accesses to the symbol_list_len element are invalid as
its offset will be wrong.

Best,
Michael

Attachment: pgp3dIhIFo2Rn.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Hi,

issue is done in my opinion.  Please reopen if not.

Kind regards

      Andreas.

On Wed, Dec 14, 2016 at 07:28:05AM +0100, Andreas Tille wrote:
> Hi Michael,
> 
> I'm currently checking older bugs and stumbled upon this one.  I
> currently can not find the said cruel mix of definitions is used for
> ALPHABET_SIZE in the code base of 2.4.0.  Could you please recheck
> and confirm whether this bug can be closed or explain in more detail
> in how far different definitions are used?
> 
> Kind regards
> 
>       Andreas.
> 
> -- 
> http://fam-tille.de
> 
> _______________________________________________
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

--- End Message ---

Reply via email to