IRC channel logs
2025-08-30.log
back to list of logs
<almuhs>hi. where is /mach/msgserver.c ? <almuhs>Because newp doesn't get initial value and remains NULL <almuhs>gdb doesn't provide me capabilities to execute step by step, so i'm simply working by try-error <almuhs>but now seems that io_seek() fails <almuhs>i don't know if there are other possible implementation for this function <almuhs>maybe i can replace io_seek() with fseek() and ftell() <youpi>sneek: later tell almuhs grep is really a convenient tool to find things. You'll be able to see if it's an actual function (documented in the .h and/or .texi), or an RPC (documented in the .defs) <azeem>alextee: it's part of glibc I believe, or what is your problem? <azeem>alextee: nevermind I was stuck in scrollback, sorry for the noise <azeem>the 5min load average on amd64 seems to 0.0 all the time, is this a known issue? <azeem>load average: 3.22, 0.00, 3.55 <azeem>(the 1min/15min look a bit high to me as well) <youpi>it looks like a 32b / 64b int imsmatch <sneek>Welcome back almuhs, you have 1 message! <sneek>almuhs, youpi says: grep is really a convenient tool to find things. You'll be able to see if it's an actual function (documented in the .h and/or .texi), or an RPC (documented in the .defs) <almuhs>youpi: i can't make grep if i don't know in which directory are this file <almuhs>i don't know where are the .h and the .texi, neither the .defs <etno>almuhs: grep -R might be helpful in this case <diegonc>almuhs: for the .defs in the installed system: <diegonc>$ find /usr/include/x86_64-gnu/ | grep .defs <diegonc>I guess they come from hurd, gnumach packages (not sure about glibc) <almuhs>diegonc: /usr/include only have the .h. I need the .c <almuhs>and, where are the .c? I found in gnumach and hurd sources, and these aren't there <diegonc>I think some files are generated by mig, specially when they come from some RPC <diegonc>others may come from glibc which is superpowered on Hurd :) <diegonc>what are you looking for? I may help a bit if you don't mind <almuhs>diegonc: i need to understand better the purpose of trivfs_S_io_seek(), trivfs_S_io_read() and trivfs_S_io_write() <almuhs>when this code is executed? Why this implementation? <almuhs>in my rust port, newp remains NULL, and i don't know the reason. I tried to fix defining the SEEK_SET case calling to io_seek(), but now I have the error "resource lost" <almuhs>i tried to debug with gdb, but the debugger skip these calls <diegonc>From what I can see the implementation is calling io_seek on the underlying filesystem node (i.e the one where ceasar is atteached to with settrans)