Displaying 3 results from an estimated 3 matches for "obsurdly".
Did you mean:
absurdly
1999 Feb 22
0
Forw: RedHat sysklogd vulnerability
...tr, but it will solve the problem. However, later on:
>
> ExpandKadds(line, eline)
>
> Where eline is the same size as line. I think the real solution is to make
> sure the buffer is larger (LOG_LINE_LENGTH) like Michal said, and make sure
> modules and programs don't generate obsurdly long messages, because you
> can't be certain how much room is necessary for the expanded symbols. It
> would be nice if ExpandKadds() allocated memory dynamically, but it doesn't.
RedHat immediately issued a "fix" to their current package: sysklogd-1.3-26
This "fix&q...
2004 Jun 14
0
[LLVMdev] Memory Alignment, Heap allocation.
On Mon, 14 Jun 2004, Tobias Nurmiranta wrote:
> A small question: How do I ensure memory alignment? I want all malloced
> memory, globals and functions to be 4-byte aligned. Does llvm have any
> ".align" keyword?
In the medium term, we plan to add alignment requirements to the
alloca/malloc instructions and to globals (vars/functions) but we do not
have this yet. Currently
2004 Jun 14
4
[LLVMdev] Memory Alignment, Heap allocation.
Hi,
1.
A small question: How do I ensure memory alignment? I want all malloced
memory, globals and functions to be 4-byte aligned. Does llvm have any
".align" keyword?
I'm currently implementing a small scheme toy-compiler, and want to use
the lowest 2 bits for type tags. It's Currently 380 lines of
scheme-code[1], quite similar to the compiler in SICP[2], which I hope to
get