re: kern/54322: strange kdump output

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR kern/54322; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: gnats-bugs%netbsd.org@localhost, martin%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost
Subject: re: kern/54322: strange kdump output
Date: Mon, 24 Jun 2019 19:47:55 +1000

 > While ktracing a threaded application I noticed strange output in kdump:
 > 
 >   6851      1 gxemul   CALL  read(4,0x7d05e3f9e000,0x1000)
 >   6851      1 gxemul   GIO   fd 4 read 4088 bytes
 > [... data content stripped ...]
 >   6851      1 gxemul   GIO   fd 4 read 8 bytes
 >        "%\M^@\M^@\0\^D\0@\^P"
 >   6851      1 gxemul   RET   read 4096/0x1000
 > 
 > I expected a request of 0x1000 to just trigger the transfer of upto
 > 4096/0x1000 bytes. Why is GIO accounting for additional stuff?
 
 what is fd4?  is it perhaps a block device or a file system
 with 4KB blocks?
 
 
 .mrg.