Process r2 was stopped if machine hasn't enough memory #13143
Labels
Projects
Comments
|
That's debian fault, there are kernel configuration options to disable this oomthing, but anyway, you should report this properly (use ldpreload or asan or strace) but provide us a proper backtrace with the offending line highlighted. I dont use debian so i cant reproduce.
… On 18 Feb 2019, at 17:29, Boris Ryutin ***@***.***> wrote:
Work environment
Questions Answers
OS/arch/bits (mandatory) VM Ubuntu 18 x64, 4Gb RAM
r2 -v full output, not truncated (mandatory) rradare2 3.3.0-git 21034 @ linux-x86-64 git.3.2.1-384-g2dc2de305
commit: 2dc2de3 <2dc2de3> build: 2019-02-18__01:53:27
$ r2 -A /usr/lib/firefox/libxul.so
WARNING: bin_strings buffer is too big (0x012ad527). Use -zzz or set bin.maxstrbuf (RABIN2_MAXSTRBUF) in r2 (rabin2)
Cannot compute hash
Cannot compute hash
oops
[[anal.jmptbl] Missing predecesessor cjmp bb at 0x011bec83
[anal.jmptbl] Missing predecesessor cjmp bb at 0x03622647
[anal.jmptbl] Missing predecesessor cjmp bb at 0x036725b7
[anal.jmptbl] Missing predecesessor cjmp bb at 0x022d0557
[anal.jmptbl] Missing predecesessor cjmp bb at 0x03622637
[anal.jmptbl] Missing predecesessor cjmp bb at 0x04905255
[anal.jmptbl] Missing predecesessor cjmp bb at 0x037af4b7
[anal.jmptbl] Missing predecesessor cjmp bb at 0x022d0547
[x] Analyze all flags starting with sym. and entry0 (aa)
...
[x] Analyze function calls (aac)
[x] Analyze len bytes of instructions for references (aar)
[Invalid asr shift of 58 at 0x3bc3d5bnctions (aaft)
Invalid asr shift of 58 at 0x3bc3e25
Invalid asr shift of 58 at 0x3bc3ebf
Invalid asr shift of 58 at 0x3bc3f61
Invalid asr shift of 58 at 0x3bc3ffb
Invalid asr shift of 58 at 0x3bc40aa
Invalid asr shift of 58 at 0x3bc375c
Invalid asr shift of 58 at 0x3bc3889
Invalid asr shift of 58 at 0x3bc390f
Invalid asr shift of 58 at 0x3bc397c
Invalid asr shift of 58 at 0x3bc3a59
Invalid asr shift of 58 at 0x3bc3ac6
Invalid asr shift of 58 at 0x3bc3b80
Invalid asr shift of 58 at 0x3bc3bed
Invalid asr shift of 58 at 0x3bc44e1
Invalid asr shift of 58 at 0x3bc4bd4
Invalid asr shift of 32 at 0x371cfa4
Invalid asr shift of 46 at 0x371e281
Invalid asr shift of 46 at 0x371e2df
Invalid asr shift of 33 at 0x370511d
Invalid asr shift of 35 at 0x36dfd1b
Invalid asr shift of 46 at 0x36e2068
Invalid asr shift of 32 at 0x36dbcf3
Invalid asr shift of 36 at 0x36dbdb6
Killed
Additional info in #6322 <#6322>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#13143>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-loh8mUYCQilWXxnS-QkId5RmSjlUks5vOtUEgaJpZM4bBOiM>.
|
|
bt is empty in gdb session. How can I make asan build? (what options) |
|
sys/asan.sh
… On 19 Feb 2019, at 15:34, Boris Ryutin ***@***.***> wrote:
bt is empty in gdb session. How can I make asan build? (what options)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#13143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-lkhuBARbr38gBhoF-yNOegS40wxdks5vPAtugaJpZM4bBOiM>.
|
|
@radare with default arguments? |
|
yes, no need to pass any option
… On 19 Feb 2019, at 15:37, Boris Ryutin ***@***.***> wrote:
@radare <https://github.com/radare> with default arguments?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#13143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-loLIKHU_85hEIozhbGK_r0U9Pa6zks5vPAwdgaJpZM4bBOiM>.
|
|
asan build doesn't show another errors |
|
Does it show the stack trace when the program gets killed? |
|
Nope |
|
thats why debian sucks so hard, the process is killed by the kernel, the debugger have no control in here, pls @ret2libc share your ldpreloaded lib so he can have an int3 when a big allocation happens
… On 19 Feb 2019, at 16:41, Riccardo Schirone ***@***.***> wrote:
Does it show the stack trace when the program gets killed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#13143 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-ln5n6qncC_BN_q3R-2D6tNFjz0ZOks5vPBs6gaJpZM4bBOiM>.
|
|
This is not about a big malloc, but a series of relatively small mallocs, because the program keeps calling brk. If there was a big malloc it would have probably used |
|
is this bug still there? i think we fixed all those memory problems |
|
Well... I think the problem is still there, because r2 uses in general a lot of memory and on some machines with not a lot of ram r2 could be killed. That said.... at the moment and for some time I think there isn't much we can do. |
|
Yep, it was aborted again. |
|
Fix it with hardware
… On 17 Apr 2019, at 15:21, Boris Ryutin ***@***.***> wrote:
Yep, it was aborted again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Work environment
Additional info in #6322
The text was updated successfully, but these errors were encountered: