network profile
| bio | website | google.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Nov 8 '12 at 12:46 | |
| stats | profile views | 1 |
|
Nov 5 |
awarded | Student |
|
Nov 5 |
comment |
sigsegv in php5.3.10 D.W. Excellent answer again! Thank you very much. Indeed this two params (--leak-check and --show-reachable) helps me with identifying this (kind of) bug. And as on friend of mine said: this bug is not exploitable. Honestly - I don't know how far is it true, but seems to be, if he said so ;) Anyway, if You want to check it, let me know (could be privately) and I can share this information with You. If you're using valgrind and you want to teach me a little let me know. I will be very glad to get some knowledge from someone with practice:) Anyway, once again very big thanks D.W.! :) |
|
Nov 5 |
comment |
sigsegv in php5.3.10 UPDATE: ok, i've installed it with -g symbols, and I started valgrind with -v --leak-check=full --show-reachable=yes --log-file=valgrind.%p parameters (one of the manuals said that will be good for start). Now I have a few lines to check... if you would like to help me more, feel free to ask. it will be very usefull ;) |
|
Nov 5 |
comment |
sigsegv in php5.3.10 Wow, this is very good answer, thanks D.W. Can You tell me more about, how can I compile it with debugging symbols (I suppose that I should add to Makefile '-g' - correct me if I'm wrong please). Also any tip for valgrind usage? I've read about this program, but newer used it before to exploit developing. Once again, big thanks! :) |
|
Nov 5 |
asked | sigsegv in php5.3.10 |
