This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients chris.jerdonek, ned.deily, vstinner
Date 2012-07-27.07:51:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
faulthandler has arbitrary limits to avoid an unlimited loop if some
data are corrupted.

#define MAX_FRAME_DEPTH 100
#define MAX_NTHREADS 100

The string limit is maybe too short. MAX_STRING_LENGTH can be set to
500 characters, what do you think?

We may also add a function to change these limits at runtime.

> Without investigating further, my instinct would be to prefer to truncate in the middle,
> if possible, otherwise truncate the head of the path, rather than truncate the tail.

faulthandler does not trust anything, including the length of the
string. Change the limit to 500 characters should be safer.

Remember that faulthandler is called when something really bad
happens, like a segfault or an illegal instruction.

faulthandler may be less strict when it is called explicitly, ex:
Date User Action Args
2012-07-27 07:51:56vstinnersetrecipients: + vstinner, ned.deily, chris.jerdonek
2012-07-27 07:51:55vstinnerlinkissue15463 messages
2012-07-27 07:51:55vstinnercreate