[issue46357] socket module fix warning build on FreeBSD

Change by David CARLIER : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46357] socket module fix warning build on FreeBSD

David CARLIER added the comment: I get what you mean now I thought memset was enough. -- ___ Python tracker ___ ___

[issue46357] socket module fix warning build on FreeBSD

STINNER Victor added the comment: > I took as initialized to avoid undefined behavior rather than anything. I don't get what you mean. Can you please show me which functions initialize sockaddr_l2cap structures and explain how the current code fills all members? I don't know the code well

[issue46357] socket module fix warning build on FreeBSD

David CARLIER added the comment: I took as initialized to avoid undefined behavior rather than anything. -- ___ Python tracker ___

[issue46357] socket module fix warning build on FreeBSD

STINNER Victor added the comment: > Solves the "Make sure new member of socket address initialized." warning for > the bluetooth sockaddr_l2cap usage. You would to elaborate how you checked that all members of the socket address are initialized? Which socketmodule.c functions use this type?

[issue46357] socket module fix warning build on FreeBSD

New submission from David CARLIER : - Solves the "Make sure new member of socket address initialized." warning for the bluetooth sockaddr_l2cap usage. -- components: FreeBSD messages: 410419 nosy: devnexen, koobs priority: normal pull_requests: 28761 severity: normal status: open