Bug #1786
Calling NULL function pointer initiates panic loop
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
Further description in the commit message,
http://gitweb.dragonflybsd.org/~sjg/dragonfly.git/log/refs/heads/null_fp
Please review, I am not sure this is necessarily the best way to
address this, for instance, you don't actually see where the panic
occurred.
Sam
Related todos
History
Updated by nthery almost 3 years ago
On 21 June 2010 19:26, Samuel J. Greear <sjg@evilcode.net> wrote:
> Further description in the commit message,
>
> http://gitweb.dragonflybsd.org/~sjg/dragonfly.git/log/refs/heads/null_fp
>
> Please review, I am not sure this is necessarily the best way to
> address this, for instance, you don't actually see where the panic
> occurred.
It looks fine to me.
Updated by alexh over 2 years ago
Are there still plans to commit this?
Updated by sjg over 2 years ago
I'm not sure it is commit-able as-is, you are unable to manipulate anything with
gdb with this patch, although it does solve the panic loop issue. I think there
is a better fix to be had.