Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APP CRASH (1.5.0.1 okular) #252

Closed
derekbruening opened this issue Nov 27, 2014 · 4 comments
Closed

APP CRASH (1.5.0.1 okular) #252

derekbruening opened this issue Nov 27, 2014 · 4 comments

Comments

@derekbruening
Copy link
Contributor

From [email protected] on January 21, 2010 15:17:12

What steps will reproduce the problem? 1. Setup Debian Testing (AMD64)
2. Get the latest Dynamorio release 1.5.0.1
3. Launch okular (a PDF reader): bin64/drdeploy -client
samples/bin64/libempty.so 0x1 "" okular What is the expected output? What do you see instead? Expected the program to run like it does normally, unfortunately it crashes.
<Application okular (2012)
** Received SIGSEGV at DynamoRIO pc 0xc28e1691 in thread 2012>

if i launch with the -debug flag, then the output is:
<Application okular (2025) DynamoRIO usage error : instr_encode error: no
encoding found> What version of the product are you using? On what operating system? Linux debian 2.6.30-2-amd64 #1 SMP Mon Dec 7 05:21:45 UTC 2009 x86_64 GNU/Linux Please provide any additional information below. i've compiled revision 261 and the problem remains. on some programs the
provided clients in the release work ok, on others they either hang or crash.

programs that work: ls, vim, links2 -g, rxvt
.. that hang: gvim, firefox, openoffice
.. that crash: okular

hopefully these issues can be resolved, as i'm planning on relying on
dynamorio as the basis for a 3d visualization debugger. feel free to ask if
u you need more info on the bug report. i'll report on the other programs
in a seperate entry.
david

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=252

@derekbruening
Copy link
Contributor Author

From [email protected] on January 24, 2010 13:52:20

Here's a backtrace:

bin64/drdeploy -ops "-pause_on_error" -debug -client samples/bin64/libempty.so 0x1 ""
okular
<Starting application okular (3949)>
<Application okular (3949) DynamoRIO usage error : instr_encode error: no encoding found>
<Application okular (3949). Waiting for debugger to attach.>


gdb which okular 3949:

#0 0x000000007116e89c in syscall_ready ()
from
/home/david/Applications/Source/DynamoRIO-Linux-1.5.0-1/lib64/debug/libdynamorio.so
#1 0x00000000714032a0 in ?? ()
from
/home/david/Applications/Source/DynamoRIO-Linux-1.5.0-1/lib64/debug/libdynamorio.so
#2 0x0000000071178e45 in thread_yield ()
at /work/dr/tot/opensource/core/linux/os.c:2024
#3 0x0000000071185e5f in os_dump_core (msg=)
at /work/dr/tot/opensource/core/linux/signal.c:4229
#4 0x00000000710ca49d in report_dynamorio_problem (
dcontext=, dumpcore_flag=16, exception_addr=0x0,
report_ebp=0x77f21ac0 " \033\362w", fmt=)
at /work/dr/tot/opensource/core/utils.c:2111
#5 0x00000000710ca5ca in external_error (
file=0x711adb90 "/work/dr/tot/opensource/core/x86/encode.c", line=1943,
msg=0x711ae428 "instr_encode error: no encoding found")
at /work/dr/tot/opensource/core/utils.c:199
#6 0x0000000071132be3 in instr_encode_common (dcontext=0x77ed3700,
instr=0x77f2ad88, pc=, check_reachable=1,
assert_reachable=0) at /work/dr/tot/opensource/core/x86/encode.c:1943
#7 0x00000000711333f9 in instr_encode_check_reachability (dcontext=0x18,
---Type to continue, or q to quit---
instr=0x0, pc=0x3d <Address 0x3d out of bounds>)
at /work/dr/tot/opensource/core/x86/encode.c:2248
#8 0x0000000071148234 in private_instr_encode (dcontext=0x77ed3700,
instr=0x77f2ad88, always_cache=0)
at /work/dr/tot/opensource/core/x86/instr.c:1795
#9 0x0000000071149555 in instr_length (dcontext=0x77ed3700, instr=0x77f2ad88)
at /work/dr/tot/opensource/core/x86/instr.c:2734
#10 0x000000007109c7d1 in emit_fragment_common (dcontext=0x77ed3700,
tag=0x7f0867745155 "f\017n\302\017\357\300\201\371\377", ilist=0x77f2adf0,
flags=150996480, vmlist=0x791209c8, link_fragment=1, add_to_htable=1,
replace_fragment=0x0) at /work/dr/tot/opensource/core/emit.c:468
#11 0x000000007109fd60 in emit_fragment_ex (dcontext=0x18, tag=0x0,
ilist=0x3d, flags=4294967295, vmlist=0x3d, link=96, visible=1)
at /work/dr/tot/opensource/core/emit.c:1009
#12 0x000000007115cdd0 in build_basic_block_fragment (dcontext=0x77ed3700,
start=0x7f0867745155 "f\017n\302\017\357\300\201\371\377",
initial_flags=0, link=1, visible=1, for_trace=0, unmangled_ilist=0x0)
at /work/dr/tot/opensource/core/x86/interp.c:4067
#13 0x000000007109adb6 in dispatch (dcontext=0x77ed3700)
at /work/dr/tot/opensource/core/dispatch.c:184
#14 0x0000000077ebad59 in ?? ()
#15 0x0000000000000000 in ?? ()

@derekbruening
Copy link
Contributor Author

From [email protected] on January 25, 2010 08:08:21

We have fixed the bug and committed into the source code.
It was caused by mishandling the register %mm3 as a general register in mangle_rel_addr.

Cc: [email protected]

@derekbruening
Copy link
Contributor Author

From [email protected] on January 25, 2010 08:08:36

Status: Fixed

@derekbruening
Copy link
Contributor Author

From [email protected] on January 26, 2010 05:40:57

that fixed it :) thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant