Windows7 using VS2013 development of a plug-in, and perfect running on ie8, now transferred to Windows XP, ie8 browser can not load plug-ins.
I take the measures:
VS2013 on Windows 7, select the v120_xp, but there is no effect;
Install the XP system, VS2010 in the virtual machine,Run Firebreath demo again,the following error occurred:
Can not open the program database "d: \ firebreath-master \ build \ npapicore \ npapicore.dir \ debug \ vc100.idb"
how can i do?#taxilian
In general, it's not particularly appropriate to call out a specific person to answer a question on stackoverflow. I do monitor this tag, so I see it, but just so you are aware =]
There are three basic reasons why a plugin may not load:
The plugin is not registered correctly
This shouldn't be possible, since firebreath takes care of that for you; can't guarantee that nothing went wrong, of course. The only way to troubleshoot this is to learn how registration works and double check everything.
The plugin DLL has libraries which are not available on the system
This would be my #1 guess as to what is happening; the best way to check is to use Dependency Walker to see what dependencies it has that may not be available; ieshims.dll is a common one to see looking like it isn't there when it works, but most anything else is likely to be a problem. It's quite possible that there are dependencies added by vs2013 that aren't there with vs2010; I'd also verify that the target set in win_common.h in firebreath is correct for windows XP.
The plugin may actually be loading but then crashing immediately.
The easiest way to test this would be to add a call to __debugbreak() early in the plugin lifecycle; this will make it look like it crashed but let you attach a debugger.
If none of that helps I'd recommend using the firebreath-dev google group which is a more appropriate place for a discussion.
Related
I have compiled my qemu which version is 5.2.0 on mips64el host machine. When I run qemu-system-aarch64 to start a linux OS, I get this problem as follow:
qemu-system-aarch64: ../accel/tcg/cpu-exec.c:681: cpu_loop_exec_tb: Assertion `icount_enabled()' failed
Have anyone miss the same problem, please help me, thanks a lot!
This shouldn't happen -- it is a bug in QEMU. You should confirm that you can reproduce it on a QEMU built from the head of upstream git, and then report it in the QEMU bug tracker at https://gitlab.com/qemu-project/qemu/-/issues with the full instructions on how to reproduce the failure, including the full QEMU command line and any image files that are needed.
It would also be helpful to check whether the problem reproduces on a different host architecture (eg x86-64) -- it may be that the bug is specific to running on MIPS hosts (we don't have good MIPS hosts that we can run CI testing on, so this setup gets a lot less testing).
The -icount flag is buggy for a lot of QEMU architectures. I could not find if it is still supported in qemu. (As pointed out by Peter Maydell it is properly supported). Try removing that flag for now and check if that works or not.
Also check if your device is supported here.
I downloaded the official Chrome nativeMessaging example to test it out.
To do this, I installed the app from chrome://extensions, by choosing Load Unpacked. No problems so far.
I then installed the host. I'm using Windows 7, so I ran install_host.bat, which claimed that "The operation completed successfully." However, when I go to chrome://apps/ and click the Connect button, I get this error:
Failed to connect: Native host has exited.
Is there some reason this would happen? Restarting Chrome did not fix the issue, nor did uninstalling and then reinstalling the host program.
(I noticed that native-messaging-example-host.bat requires Python 2, so I modified it to run Python 2 explicitly. If I run native-messaging-example-host.bat from the command line, it pops up a little example program of its own with a GUI and seems to work correctly.)
Turns out I was using a non-standard character in the path leading to the host executable. This wouldn't be a problem for any other program, but Chrome's native messaging API doesn't like it, I guess.
By the way, the documentation on setting up this example is near-nonexistent, but this stack overflow link has some useful info: Chrome Extension NativeMessaging 'connectNative' undefined
My environment: win8 64bit, vs2010,
I follow every step in the tutorial but my own dll plugin just can't be installed, I have also installed WiX toolsets and made a msi file, but it simply do not work...
(1) I do all the work with prompt(privileged ) cmd.
(2)My files are shown in below
(3)firefox about:plugins page do not contain my dll plugin after my msi file installed..
(4) failed ..
So what is going on here?
Are you building using the prep2010x64.cmd file (or a different x64.cmd file)? if so, that's likely your issue. Many people, failing entirely to read the instructions on the firebreath website, mistakenly build using the x64 because they're running a 64 bit operating system. thing is, the browsers like firefox still are 32 bit, so the plugin needs to be built 32 bit as well.
The next question, if that doesn't help, is whether or not the regsvr32 command succeeds when you run it on the .dll.
Clarification: You figured this out, but for future readers to be very clear:
Do not use prep2010x64.cmd unless you can explain clearly why you need to -- and running a 64 bit OS does not count. Most people want to use prep2010.cmd (or whichever year).
I have built a simple NaCl application. For running the application I use technique 2 described in Nacl Developer's guide, which means that instead of running a local server I load my application as unpacked extension to chrome. The application runs fine so far.
Now I want to experiment with nacl-gdb and attach my application to it at startup.
In the NaCl Developer's guide there are only instructions on how to attach nacl-gdb on an application that is run with local server(technique 1). I made a search to the internet and I ended up with the following approach in order to attach nacl-gdb for an application that is being ran with technique 2:
I enabled "Native Client GDB-based debugging" flag of Chrome.
I started chrome from a terminal like this: ./chrome "--nacl-gdb=gnome-terminal --
/media/sdb1/leonidasbo/AncientRoot/nacl_sdk/pepper_27/toolchain/linux_x86_glibc/bin/x86_64-nacl-gdb"
When Chrome launched, I navigated to my application.
With this approach, Chrome automatically started nacl-gdb when I opened my application.
However nacl-gdb tried to attach but with no success. The output was the following:
*This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=x86_64-nacl".
Reading symbols from /opt/google/chrome/nacl_irt_x86_64.nexe...(no debugging symbols found)...done.
Don't know how to attach. Try "help target".
(gdb)*
It seems that gdb cannot attach to my application. I tried executing "target exec /path/to/my.nexe", but nothing changed.
Am I missing something here? Is there any other way to debug applications loaded as unpacked extensions with nacl-gdb?
My OS is Ubuntu 12.04 and I am using pepper_27 of nacl_sdk. Chrome version is 27.0.1453.93.
Thanks
I assume you were using this guide, which I was using earlier as well. It is out of date. These are the real instructions. It seems that the way you attach the debugger has completely changed, and it is no longer possible to use --nacl-gdb (that is planned for removal). You must manually attach the debugger by following these steps.
The full guide is here, but I'll summarize:
Launch Chrome with chrome --enable-nacl --enable-nacl-debug --no-sandbox --disable-hang-monitor.
Run <NACL_SDK_ROOT>/toolchain/win_x86_newlib/bin/x86_64-nacl-gdb (with no arguments).
Enter these commands into the gdb prompt:
(gdb) nacl-manifest <path-to-your-.nmf-file>
(gdb) nacl-irt <CHROME-DIR>/nacl_irt_x86_64.nexe
(gdb) target remote localhost:4014
Now you can use gdb as normal. (If you just want to run the application until it crashes, start by typing continue.)
I knew this day would come, so I guess it is here. (P.S. I am on windows XP).
I am trying to use this program here. I installed it fine, but it doesnt seem to work when I type in equations. So I went back to the site and it says I need JRE version 5.0 or above, (check). Then it also says I need dvipng, which I dont think I have.
So I went to the site it tells me to, (here), and I downloaded the most recent one, "dvipng-1.14.tar.gz". I unzipped it and I have it all sitting in one directory.
Ok... now what?
Im afraid I need guidance on exactly how to proceed here. The readme and installation instructions say to run "./configure", then "make", etc, I opened the command prompt and did all that but doesnt recognize. I have never had to build in this way, I always used an IDE for compiling C++ programs that I write myself. (Anyway, why am I even having to make an exe why dont they just make one and let us download that?)
Very confused as to what I need to do here, appreciate some step by step help.
Thank you
Even though Mohammad's problem was solved in the comments, I'll have a go at answering his question:
To run a build system that uses ./configure, you need something that can run shell scripts, as well as the usual suite of unix tools that the script expects, plus a compiler that behaves in the standard sort of way.
The two projects that I know of that do this are cygwin and MSYS. cygwin is aimed at creating a full POSIX environment on windows, while MSYS is an add-on to MinGW that aims to provide just the parts needed to run a ./configure script and build a program.