basename implicitly converted to pointer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rasmol (Debian) |
Fix Released
|
Unknown
|
|||
rasmol (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Karmic |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: rasmol
In 2.7.4.2-1:
Function `basename' implicitly converted to pointer at molecule.c:338
Function `basename' implicitly converted to pointer at molecule.c:338
Function `basename' implicitly converted to pointer at molecule.c:338
Function `basename' implicitly converted to pointer at molecule.c:338
Our automated build log filter[1] detected the problem(s) above that will
likely cause your package to segfault on 64-bit architectures (where the
size of a pointer is greater than the size of an integer.)
This is often due to a missing function prototype definition.
For more information, see [2].
Since use of implicitly converted pointers is always (eventually
and/or itermittantly) fatal to the application, they are errors.
Please correct them for your next upload.
[1] http://
[2] http://
Changed in rasmol (Debian): | |
status: | Unknown → Fix Released |
Changed in rasmol (Ubuntu Karmic): | |
importance: | Undecided → High |
milestone: | none → karmic-alpha-6 |
status: | New → Triaged |
This was fixed in debian in 2.7.4.2-5