MALLOC_PERTURB_: Finding real bugs in condor_chirp

If you are not familiar with MALLOC_PERTURB_, you should read the fedora-devel post by Jim Meyering.

After condor_ssh_to_job, which gives you a shell in the environment of your running job,

$ /usr/libexec/condor/condor_chirp get_job_attr Owner                 
$ MALLOC_PERTURB_=97 /usr/libexec/condor/condor_chirp get_job_attr Owner
$ MALLOC_PERTURB_=98 /usr/libexec/condor/condor_chirp get_job_attr Owner
$ MALLOC_PERTURB_=0 /usr/libexec/condor/condor_chirp get_job_attr Owner

From io_proxy_handler.cpp:

		result = REMOTE_CONDOR_get_job_attr(name,recv_expr);
		if(result==0) {
			sprintf(line,"%u",(unsigned int)strlen(recv_expr));
		} else {

From chirp_client_get_job_attr in chirp_client.c:

		*expr = (char*)malloc(result);
		if(*expr) {
			actual = fread(*expr,1,result,c->rstream);
			if(actual!=result) chirp_fatal_request("get_job_attr");
		} else {

From condor_chirp.cpp:

	char *p = 0;
	chirp_client_get_job_attr(client, argv[2], &p);
	printf("%s\n", p);

Tags: , , , ,

One Response to “MALLOC_PERTURB_: Finding real bugs in condor_chirp”

  1. Reuben Schwartz Says:

    Hello, superb site you have right here, although I simply needed to let you know about what may well potentially be considered a web browser compatibility issue. So i am running Windows XP 64 bit together with Ie, and the format is screwed up. It’s a tad hard to check out a few aspects of your blog, and I’m running my screen resolution at 1680 x 480. I’m certain you did not intend for your site to look so peculiar, so is there any way you can help me deal with this matter?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: