#2286 closed defect (fixed)
"memory could not be allocated" if no MALLOC_GLIBC_COMPAT by "malloc(0)"
Reported by: | sergay | Owned by: | |
---|---|---|---|
Priority: | minor | Component: | General |
Severity: | medium | Keywords: | |
Cc: | Sensitive: | no |
Description
If uClibc's MALLOC_GLIBC_COMPAT
is not set, oscam crashes on startup with memory could not be allocated
. This occurs if in the oscam.srvid a channel is multiple times (with different caids).
On some routers with uClibc 0.9.31 and 0.9.32 MALLOC_GLIBC_COMPAT is not set anymore, so please commit the attached patch to trunk and 1.1.
Please also commit attached target "cross-mips-router-linux-uclibc931" to trunk and 1.1. "cross-mips-router-linux-uclibc930" is still missing in 1.1
Attachments (3)
Change History (10)
by , 12 years ago
Attachment: | MALLOC_GLIBC_COMPAT-is_not_set.patch added |
---|
by , 12 years ago
Attachment: | trunk--mips-router-linux-uclibc931.patch added |
---|
by , 12 years ago
Attachment: | tag11--mips-router-linux-uclibc93x.patch added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
patch added to trunk, tag will not receive any new feature!
comment:5 by , 12 years ago
So MALLOC_GLIBC_COMPAT-is_not_set
seems not to be a feature and should be merged?
Btw why should users of a specific uClibc version be force to use the unstable trunk instead of the "stable rc tag" because of a lack (not missing "feature") of the build system?
comment:6 by , 12 years ago
grmpf - "MALLOC_GLIBC_COMPAT-is_not_set.patch" only went to TRUNK and not to TAG. accept that the dev´s can only maintain ONE development branch.
comment:7 by , 12 years ago
If you think this is right i cant change it. It would not be the first wired decision, like calling a branch a tag or merging into a tag... ;-)
trunk-patch added in r6184