From: Peter Kosinar (goober@ksp.sk)
Date: Mon Apr 24 2006 - 18:11:59 EDT
> ###Content of exp.py########################
> #! /bin/env python
>
> import os
> os.system("./test "+("A" * 524))
> ############################################
As the others have already pointed out, the program (most likely) DOES
crash you just don't see the fancy "Speicherzugriffsfehler" /
"Segmentation fault" message. The reason is simple -- that message is not
produced by the failing program itself; it's written by bash/zsh/whatever
nice shell you're using when it detects that the spawned child process
has died because of SIGSEGV (signal 11). If you increase the rlimit on
coresize, you'll get the core file for later analysis.
It might be a good idea to prefix the os.system() call with something like
"print"; the program should output "11" which corresponds to the SIGSEGV
mentioned before.
Peter
-- [Name] Peter Kosinar [Quote] 2B | ~2B = exp(i*PI) [ICQ] 134813278 ------------------------------------------------------------------------------ This List Sponsored by: Cenzic Concerned about Web Application Security? Why not go with the #1 solution - Cenzic, the only one to win the Analyst's Choice Award from eWeek. As attacks through web applications continue to rise, you need to proactively protect your applications from hackers. Cenzic has the most comprehensive solutions to meet your application security penetration testing and vulnerability management needs. You have an option to go with a managed service (Cenzic ClickToSecure) or an enterprise software (Cenzic Hailstorm). Download FREE whitepaper on how a managed service can help you: http://www.cenzic.com/news_events/wpappsec.php And, now for a limited time we can do a FREE audit for you to confirm your results from other product. Contact us at request@cenzic.com for details. ------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:55:52 EDT