This is irritating, as it can't actually happen if you look at the code path (I don't think :-). However, it does show that we now need to start initializing our auto's on the stack, else gcc is going to make life increasingly annoying for us :-).

Jeremy.

ok, if you think this warning is wrong here, please just close again.

I just wanted to point out all the things I was seeing in internal builds, some of them are real problems, some are not. We just should have a look at those things before final ships.

Thanks Jeremy!

quick update, in master I get:

smbd/smb2_server.c:52: warning: no previous prototype for ‘smb2_opcode_name’
smbd/smb2_server.c: In function ‘smbd_smb2_first_negprot’:
smbd/smb2_server.c:1902: warning: ‘req’ may be used uninitialized in this function
smbd/smb2_tcon.c: In function ‘smbd_smb2_request_process_tcon’:
smbd/smb2_tcon.c:50: warning: ‘out_tree_id’ may be used uninitialized in this function
smbd/smb2_tcon.c:48: warning: ‘out_capabilities’ may be used uninitialized in this function
smbd/smb2_tcon.c:47: warning: ‘out_share_flags’ may be used uninitialized in this function
smbd/smb2_tcon.c:46: warning: ‘out_share_type’ may be used uninitialized in this function
smbd/smb2_getinfo.c: In function ‘smbd_smb2_request_getinfo_done’:
smbd/smb2_getinfo.c:133: warning: ‘call_status.v’ may be used uninitialized in this function

Change component

I think they are all resolved by now. Closing...