Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7379 - [ALPM] alpm_trans_commit pointers
Attached to Project:
Arch Linux
Opened by Georg Grabler (STiAT) - Wednesday, 06 June 2007, 22:19 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 06 June 2007, 22:40 GMT
Opened by Georg Grabler (STiAT) - Wednesday, 06 June 2007, 22:19 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 06 June 2007, 22:40 GMT
|
DetailsHey,
As you know, i'm using alpm currently for continuing pyalpm. I encountered something what isn't a problem, but isn't nice anyway. I accidentally passed NULL to alpm_trans_commit in a sync operation (very accidentally by writing NULL), and alpm segfaulted. Of course, it's nothing expected. A compiler won't warn about NULL, therefore i think it's something alpm should actually be able to handle, since it has nothing to do with type safety, it should return an error code on this. Yours, Georg (STiAT) |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Wednesday, 06 June 2007, 22:40 GMT
Reason for closing: Duplicate
Additional comments about closing: http://bugs.archlinux.org/task/7380
Wednesday, 06 June 2007, 22:40 GMT
Reason for closing: Duplicate
Additional comments about closing: http://bugs.archlinux.org/task/7380