Search
Saturday, 20th of January 2018, 14:32:24 UTC
14:32:52
froggey
the miscompiled functions I saw had multiple variables simultaneously occupying one stack stack slot, which pointed me towards assign-stack-slots in the register allocator
14:33:32
froggey
and that iterates over a hash table while reading from it. that turned out to be enough to figure out what was probably going wrong
14:41:24
ebrasca
Do you have some tips for working in tcp/ip?
14:44:15
froggey
qemu & virtualbox can be configured to capture packets, you can use wireshark to look at the capture log
14:44:47
froggey
it's also possible to connect the vm directly to your network, avoiding qemu's internal network, but I don't know how to do this
14:45:06
froggey
nothing beyond that, I don't really know much about networking
14:45:56
ebrasca
about qemu I think your are talking about :
14:45:58
ebrasca
-net tap,ifname=tap2,script=no,downscript=no -net nic,model=virtio,macaddr=\"52:54:~x:~x:~x:~x\"
14:50:28
ebrasca
I have email server on my own debian VM with own IP.
15:15:12
ebrasca
I have conect wireshark to mezzano.
15:32:47
ebrasca
Mezzano connection lock dead in my wireshark.
17:05:35
ebrasca
froggey: I can't connect slime to mezzano if mezzano have own tap.
17:08:49
froggey
did you configure mezzano for your network? (see net/network-setup.lisp)
17:16:58
ebrasca
froggey: I have found I can analyze it in local loopback with normal mezzano start.
19:29:56
ebrasca
froggey: Have you see my bug fix?
19:34:53
ebrasca
https://github.com/froggey/Mezzano/pull/68
Sunday, 21st of January 2018, 2:32:24 UTC