Difference between revisions of "Summerschool Aachen 2005/Notes/Thursday Sep 22 2005"
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Typo: | + | '''Typo:''' |
worked on a continuation based microthread engine for python (precursor for a python tcp/ip implementation) | worked on a continuation based microthread engine for python (precursor for a python tcp/ip implementation) | ||
installed solaris and started exploring | installed solaris and started exploring | ||
| + | |||
| + | solaris x86 syscall conventions seem to be: use a lcall $7,$0 instead of int $0x80, push all the arguments on the | ||
| + | stack instead of linux's speedcall convention that uses registers. also the lcall contains nul bytes, so we | ||
| + | need to create some 'lcall;ret' functionlet somewhere in memory before being able to use syscalls. | ||
| + | i think all this is sysv/386 default. | ||
| + | |||
| + | '''Maximillian:''' | ||
| + | workend on makeing ScaPy work on MacOS X and SSL Fingerprinting. I added some new risks I learned about to [http://lufgi4.informatik.rwth-aachen.de/faq/tags/risks our faq] | ||
| + | [[Category:Summerschools]] | ||
Latest revision as of 08:11, 23 September 2005
Typo: worked on a continuation based microthread engine for python (precursor for a python tcp/ip implementation) installed solaris and started exploring
solaris x86 syscall conventions seem to be: use a lcall $7,$0 instead of int $0x80, push all the arguments on the stack instead of linux's speedcall convention that uses registers. also the lcall contains nul bytes, so we need to create some 'lcall;ret' functionlet somewhere in memory before being able to use syscalls. i think all this is sysv/386 default.
Maximillian: workend on makeing ScaPy work on MacOS X and SSL Fingerprinting. I added some new risks I learned about to our faq
