Home
last modified time | relevance | path

Searched hist:"670528 cd789a9ce3d51e32edddc02e6b7ff358f9" (Results 1 – 3 of 3) sorted by relevance

/freebsd/bin/sh/
H A Dmemalloc.hdiff 670528cd789a9ce3d51e32edddc02e6b7ff358f9 Fri Oct 28 12:45:19 CEST 2005 Stefan Farfeleder <stefanf@FreeBSD.org> Protect malloc, realloc and free calls with INT{ON,OFF} directly in chkalloc,
ckrealloc and ckfree (added), respectively. sh jumps out of the signal handler
using longjmp which is obviously a bad idea during malloc calls.

Note: I think there is still a small race here because volatile sig_atomic_t
only guarantees atomic reads and writes while we're doing increments and
decrements.

Protect a setmode call with INT{ON,OFF} as it calls malloc internally.

PR: 45478
Patch from: Nate Eldredge
diff 670528cd789a9ce3d51e32edddc02e6b7ff358f9 Fri Oct 28 12:45:19 CEST 2005 Stefan Farfeleder <stefanf@FreeBSD.org> Protect malloc, realloc and free calls with INT{ON,OFF} directly in chkalloc,
ckrealloc and ckfree (added), respectively. sh jumps out of the signal handler
using longjmp which is obviously a bad idea during malloc calls.

Note: I think there is still a small race here because volatile sig_atomic_t
only guarantees atomic reads and writes while we're doing increments and
decrements.

Protect a setmode call with INT{ON,OFF} as it calls malloc internally.

PR: 45478
Patch from: Nate Eldredge
H A Dmemalloc.cdiff 670528cd789a9ce3d51e32edddc02e6b7ff358f9 Fri Oct 28 12:45:19 CEST 2005 Stefan Farfeleder <stefanf@FreeBSD.org> Protect malloc, realloc and free calls with INT{ON,OFF} directly in chkalloc,
ckrealloc and ckfree (added), respectively. sh jumps out of the signal handler
using longjmp which is obviously a bad idea during malloc calls.

Note: I think there is still a small race here because volatile sig_atomic_t
only guarantees atomic reads and writes while we're doing increments and
decrements.

Protect a setmode call with INT{ON,OFF} as it calls malloc internally.

PR: 45478
Patch from: Nate Eldredge
diff 670528cd789a9ce3d51e32edddc02e6b7ff358f9 Fri Oct 28 12:45:19 CEST 2005 Stefan Farfeleder <stefanf@FreeBSD.org> Protect malloc, realloc and free calls with INT{ON,OFF} directly in chkalloc,
ckrealloc and ckfree (added), respectively. sh jumps out of the signal handler
using longjmp which is obviously a bad idea during malloc calls.

Note: I think there is still a small race here because volatile sig_atomic_t
only guarantees atomic reads and writes while we're doing increments and
decrements.

Protect a setmode call with INT{ON,OFF} as it calls malloc internally.

PR: 45478
Patch from: Nate Eldredge
H A Dmiscbltin.cdiff 670528cd789a9ce3d51e32edddc02e6b7ff358f9 Fri Oct 28 12:45:19 CEST 2005 Stefan Farfeleder <stefanf@FreeBSD.org> Protect malloc, realloc and free calls with INT{ON,OFF} directly in chkalloc,
ckrealloc and ckfree (added), respectively. sh jumps out of the signal handler
using longjmp which is obviously a bad idea during malloc calls.

Note: I think there is still a small race here because volatile sig_atomic_t
only guarantees atomic reads and writes while we're doing increments and
decrements.

Protect a setmode call with INT{ON,OFF} as it calls malloc internally.

PR: 45478
Patch from: Nate Eldredge
diff 670528cd789a9ce3d51e32edddc02e6b7ff358f9 Fri Oct 28 12:45:19 CEST 2005 Stefan Farfeleder <stefanf@FreeBSD.org> Protect malloc, realloc and free calls with INT{ON,OFF} directly in chkalloc,
ckrealloc and ckfree (added), respectively. sh jumps out of the signal handler
using longjmp which is obviously a bad idea during malloc calls.

Note: I think there is still a small race here because volatile sig_atomic_t
only guarantees atomic reads and writes while we're doing increments and
decrements.

Protect a setmode call with INT{ON,OFF} as it calls malloc internally.

PR: 45478
Patch from: Nate Eldredge