Windows error 0x00000049, 73

Detailed Error Information

PAGE_FAULT_WITH_INTERRUPTS_OFF[1]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x49: PAGE_FAULT_WITH_INTERRUPTS_OFF.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][3]
DescriptionThe default facility code.[2][3]
Error Code73 (0x0049)

Possible solutions

3

adb can't connect to 127.0.0.1:5555

vmware
adb

Only 4 months late, but if you have a router at home (which is very likely), then use a Bridged Adapter, so that it becomes another device on your home network. You can then

./adb connect 192.168.0.5
answered on Stack Overflow Oct 11, 2011 by Mendhak
2

Need help correcting Access Violation with FFmpeg DLL

c++
dll
ffmpeg
visual-studio-2012

Finally, fixed it. I did two steps and I'm not sure which one worked (heh):

  1. Added the '.lib' files as linker input dependencies
  2. I picked up the Sept 7 build and made sure I have all the same build-date for the dll's, libraries, and include files.

Everything appears to work fine now.

answered on Stack Overflow Sep 26, 2012 by James
1

Android 127.0.0.1 (loopback) connection: Works on WiFi, fails with 3G/4G

android
networking
mobile-webkit
loopback
3g-network

Finally it looks it was a problem with the WebView trying to access an external proxy even for the lookback interface. I fixed the issue following the solution proposed at: WebView android proxy

answered on Stack Overflow Jun 1, 2015 by earizon • edited May 23, 2017 by Community
1

Eclipse Android X86 Cannot connect to 127.0.0.1

android

Hello James, I tried a similar set up and I got the same error as you. I eventually gave up using virtualbox. After struggling for two days I switched to using vmware and I had to use a different image. I used the following image: http://android-x86.googlecode.com/files/android-x86-2.2-r2-eeepc.iso and for the vmware set up I followed this tutorial: http://vmetc.com/2010/12/27/install-androidx86-in-a-vmware-workstation-vm/

Do not skip over the part that says to edit the virtual machines configuration file. I hope this helps.

You might also want to consider using the android image provided by http://www.vmlite.com/ it worked right away for me and I connected using "adb connect 127.0.0.1"

answered on Stack Overflow Nov 11, 2011 by Marco RS • edited Feb 14, 2012 by Marco RS
1

How to know that camera is currently being used by another application with UWP?

windows
camera
uwp
c++-cx

StartPreviewAsync method will throw a FileLoadException if another app has exclusive control of the capture device. We can catch this error to alert the user that the camera is currently being used by another application. A simple sample can be found at Use MediaCapture to start the preview stream.

However, this is a C# sample and FileLoadException is what used in .Net. For C++/CX, we can check the HRESULT value which should be 0x80070020. Following is the simple sample in C++/CX version.

MainPage.xaml

<Grid Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
    <CaptureElement Name="PreviewControl" Stretch="Uniform"/>
    <Button Click="Button_Click">Click</Button>
</Grid>

MainPage.xaml.h

public ref class MainPage sealed
{
public:
    MainPage();

private:
    // Prevent the screen from sleeping while the camera is running
    Windows::System::Display::DisplayRequest^ _displayRequest;

    // MediaCapture
    Platform::Agile<Windows::Media::Capture::MediaCapture^> _mediaCapture;

    void Button_Click(Platform::Object^ sender, Windows::UI::Xaml::RoutedEventArgs^ e);
};

MainPage.xaml.cpp

MainPage::MainPage()
    : _mediaCapture(nullptr)
    , _displayRequest(ref new Windows::System::Display::DisplayRequest())
{
    InitializeComponent();
}


void MainPage::Button_Click(Platform::Object^ sender, Windows::UI::Xaml::RoutedEventArgs^ e)
{
    _mediaCapture = ref new Windows::Media::Capture::MediaCapture();
    create_task(_mediaCapture->InitializeAsync())
        .then([this](task<void> previousTask) {
        try
        {
            previousTask.get();
            _displayRequest->RequestActive();
            Windows::Graphics::Display::DisplayInformation::AutoRotationPreferences = Windows::Graphics::Display::DisplayOrientations::Landscape;
            PreviewControl->Source = _mediaCapture.Get();
            create_task(_mediaCapture->StartPreviewAsync())
                .then([this](task<void>& previousTask)
            {
                try
                {
                    previousTask.get();
                }
                catch (Exception^ exception)
                {
                    if (exception->HResult == 0x80070020)
                    {
                        auto messageDialog = ref new Windows::UI::Popups::MessageDialog("Cannot setup camera; currently being using.");
                        create_task(messageDialog->ShowAsync());
                    }
                }
            });
        }
        catch (AccessDeniedException^)
        {
            auto messageDialog = ref new Windows::UI::Popups::MessageDialog("The app was denied access to the camera.");
            create_task(messageDialog->ShowAsync());
        }
    });
}

StartPreviewToCustomSinkAsync method is similar to StartPreviewAsync method and can also throw a FileLoadException. You should be able to handle it using the same way. For more info, please also see Handle changes in exclusive control.

answered on Stack Overflow Jun 14, 2017 by Jay Zuo
0

"netcfg wlan0 up" Not working from application

android
networking
native
ifconfig

So what I've done is add a service in init.rc file in android os, That checks every 10 seconds if wl1271 firmware state is 'stopped' with 'getprop init.svc.dhcpcd_wlan0' command. If it is anything other than 'stopped', the service does nothing and checks again in 10 seconds. If getprop returns 'stopped', the the command 'ifconfig wlan0 up' is run and the service waits for 30 seconds before checking again.

answered on Stack Overflow Dec 12, 2016 by Mr. Borad
0

Eclipse Android X86 Cannot connect to 127.0.0.1

android

I had the same problem of "unable to connect to 127.0.0.1:5555". I then found here:

http://www.android-x86.org/documents/debug-howto

...

2.using adb with a NAT'ed VM

•The steps above work nicely if you have a VM which is set up to use Bridged or Host-Only adapters •However, if you have a NAT'ed VM you cannot connect to the VM IP from the host •You will need to set up port forwarding for a host port to be forwarded to the VM port 5555 (which is adb) VBoxManage modifyvm --natpf1 adb,tcp,,,,5555 Example from one machine: VBoxManage modifyvm froyo --natpf1 adb,tcp,,5555,,5555 •Once this is done, you should see the local port (i.e. 5555 in this case) bound on the host via netstat -a •You can now connect to the VM by adb localhost:5555

That solved the problem for me. Good luck!

answered on Stack Overflow Mar 17, 2014 by astackdummy
0

App Crashes with EXC_BAD_INSTRUCTION (SIGILL)?

ios
debugging
crash

There's not much information here, as others pointed out, but this appears to be a problem when upgrading. You didn't mention how you tested this, but you should test it basically like this:

  • Use two projects, one with the previously released version, and one with the new one.
  • Run the previously released version of the app. Do some typical stuff, then close.
  • Now run the new verion of the app.

If there is an upgrade problem, you should be able to trigger it this way.

answered on Stack Overflow Jul 18, 2013 by ecotax
0

adb can't connect to 127.0.0.1:5555

vmware
adb

oh i find answer. before use adb connect command most use adb kill-server command. see following url. thanks to all. android-x86.org

answered on Stack Overflow Mar 11, 2012 by rasoul
0

wlan0 interface fails to fetch IP with udhcpc

linux
networking
wireless-networking
android
dhcp

I had the same issue. I was able to get the IP with the below command:

netcfg wlan0 dhcp

Go for this command instead of udhcpc -i wlan0.

answered on Super User Sep 8, 2016 by user3493629 • edited Sep 21, 2016 by Kamil Maciorowski
-1

get non connected devices, when my device are in tethering mode

android
android-wifi
tethering

Call exec("netcfg");


/**
 * Execute a command in a shell
 * 
 * @param command
 *            command to execute
 * @return the return of the command
 */
public String exec(String command) {
    String retour = "";
    try {
        Runtime runtime = Runtime.getRuntime();

        Process p = runtime.exec(command);

        java.io.BufferedReader standardIn = new java.io.BufferedReader(
                new java.io.InputStreamReader(p.getInputStream()));
        java.io.BufferedReader errorIn = new java.io.BufferedReader(
                new java.io.InputStreamReader(p.getErrorStream()));
        String line = "";
        while ((line = standardIn.readLine()) != null) {
            retour += line + "\n";
        }
        while ((line = errorIn.readLine()) != null) {
            retour += line + "\n";
        }
    } catch (java.io.IOException e) {
        e.printStackTrace();
    }

    return retour;
}

It will execute "netcfg" command in the shell & produces output like the following

lo       UP           127.0.0.1/8   0x00000049  00:00:00:00:00:00

sit0     DOWN         0.0.0.0/0     0x00000080  00:00:00:00:00:00

eth0     UP           0.0.0.0/0     0x00001003  78:c5:e5:a2:b2:d0

wlan0    DOWN         0.0.0.0/0     0x00001002  64:70:02:20:79:31

Including connected network interfaces , status , IP obtained & MAC address .

The last field is for MAC address. You have to parse the MAC address from this single String.

answered on Stack Overflow Apr 10, 2015 by Don Chakkappan • edited Apr 10, 2015 by Don Chakkappan

Comments

Leave a comment

(plain text only)

Sources

  1. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0