valgrind, on AMD x64, no useful stack info available - stack-trace

when use valgrind to check memory leaks, I encouter a very strange problem.
On 32bit linux, the leak stack infos are very clear like:
==10650== by 0x8130FD3: SFNTSetContactServer
==10650== by 0x81106CA: CLibLicense::GetOneLicense(std::string&, void*&)
==10650== by 0x81108C2: CLibLicense::StartingGet(void*&)
==10650== by 0x810F01A: CLibLicense::GetLicense()
==10650== by 0x810DEBB: CLicenseManager::DoGetLicense(void*, unsigned int)
But on x64 linux, I can only get ??? infos like this:
==31031== 8 bytes in 1 blocks are definitely lost in loss record 196 of 2,210
==31031== at 0x4A0646F: malloc (vg_replace_malloc.c:236)
==31031== by 0x46AF78: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x46B016: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x421F99: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x42C240: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x42D731: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x42FC65: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x465C01: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x463DB6: ??? (in /opt/usr/local/sbin/Server)
==31031== by 0x3116A1D993: (below main) (in /lib64/libc-2.5.so)
The program doesn't use dlopen/dlclose as the valgrind FAQ said.
update 1, add file stat infos
file Server
Server: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
any comments are welcome!

Well it looks like you have stripped the symbols from your program.

Related

How does Qemu locate its image file or How does Eclipse interact with Qemu?

for studying Qemu I got the 'QEMU Eclipse' plugin, built the 'blinky' project from https://gnu-mcu-eclipse.github.io/tutorials/blinky-arm/ and when I let it run, it produces the following output:
xPack 64-bit QEMU v2.8.0-9 (qemu-system-gnuarmeclipse).
Board: 'STM32F4-Discovery' (ST Discovery kit for STM32F407/417 lines).
Board picture: '/home/hgiese/Work/qemu-arm-dev/linux-x64/install/qemu-arm/share/qemu/graphics/STM32F4-Discovery.jpg'.
Device file: '/home/hgiese/Work/qemu-arm-dev/linux-x64/install/qemu-arm/share/qemu/devices/STM32F40x-qemu.json'.
Device: 'STM32F407VG' (Cortex-M4 r0p0, MPU, 4 NVIC prio bits, 82 IRQs), Flash: 1024 kB, RAM: 128 kB.
Command line: 'blinky' (6 bytes).
...
and when I let it run everything was fine.
Now, when I called Qemu directly (outside of Eclipse) with the exact command line the output was this:
xPack 64-bit QEMU v2.8.0-9 (qemu-system-gnuarmeclipse).
Board: 'STM32F4-Discovery' (ST Discovery kit for STM32F407/417 lines).
Board picture: '/home/hgiese/Work/qemu-arm-dev/linux-x64/install/qemu-arm/share/qemu/graphics/STM32F4-Discovery.jpg'.
Device file: '/home/hgiese/Work/qemu-arm-dev/linux-x64/install/qemu-arm/share/qemu/devices/STM32F40x-qemu.json'.
Device: 'STM32F407VG' (Cortex-M4 r0p0, MPU, 4 NVIC prio bits, 82 IRQs), Flash: 1024 kB, RAM: 128 kB.
Command line: 'blinky' (6 bytes).
qemu-system-gnuarmeclipse: Guest image must be specified (using --image)
no matter how I specified 'blinky':
being in the Debug directory
calling it as blinky.elf
calling it with its complete path
It got even stranger: In an attempt to produce an error message from Qemu (which might tell me something) I replaced 'blinky' with 'xyz' (in the command line field of the 'Debugger' pane in the 'Debug Configuration' dialog) - and it still worked. The only difference being the line
Command line: 'xyz' (3 bytes).
in Qemu's output, which showed me that Qemu had received this dummy parameter - and it didn't make the slightest difference for it: it still had the correct image file.
How do I have to communicate the image file to Qemu (or 'How does Eclipse does its magic?')
Any insight will be greatly appreciated.
Helmut

Install4J fails to startup on Mac OS X

With JabRef, we experience a weird situation where some users get the following error when starting JabRef
We do not ship a JRE with our application and rely on that Java is installed on the machine of the users.
We have a long issue on GitHub about this particular error and despite all our efforts, it seems we cannot find the source of the issue. Especially, since none of the devs can reproduce it. Fortunately, one of the users who experiences this error was kind enough to provide all information about his machine:
$ java -version
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
$ which java
/usr/bin/java
$ ls -l /usr/bin/java
lrwxr-xr-x 1 root wheel 74 Aug 14 12:09 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java
$ /usr/libexec/java_home -V
Matching Java Virtual Machines (2):
1.8.0_161, x86_64: "Java SE 8" /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home
1.8.0_121, x86_64: "Java SE 8" /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home
$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home
$ echo $JDK_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home
I asked this particular user to provide the INSTALL4J_LOG and so that we can compare the log-files of Install4J on my machine where it works and on the users machine where it fails.
My machine runs OS X 10.13.2 and the system of the user is OS X 10.12.6.
There are two main differences between them. The first difference is that when I invoke the JabRef launcher, it instantly tells me the order of places to search for Java:
2018-01-24 02:10:14.437 JavaApplicationStub[4846:345347] -[Launcher findJavaBundle:] [Line 479] search sequence (
EPATH,
Y,
"EJAVA_HOME",
"EJDK_HOME"
)
This is exactly the order we have configured in Install4J
On the users log-file this part is missing completely. However, it doesn't really matter, because the JRE/JDK is very rarely included in the $PATH variable. The next things to check are the default locations and this will find the JRE in Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin first.
Therefore, on my machine and on the users machine, JabRef will use this JRE and not any of additionally installed JDK's.
Now, there is the probably more important difference. On the machine of the user, it seems the JRE needs to be unpacked which does not happen for me:
2018-01-23 12:27:08.320 JavaApplicationStub[40695:1133965] -[Launcher findJavaBundle:] [Line 474] Running unpacker
2018-01-23 12:27:08.323 JavaApplicationStub[40695:1133965] +[Unpacker unpack:withProgress:] [Line 24] found ()
2018-01-23 12:27:08.323 JavaApplicationStub[40695:1133965] +[Unpacker unpack:withProgress:] [Line 24] found ()
After that, the logs look similar but when finally the JRE is invoked, it cannot be found on the user's machine and we get the error message
2018-01-23 12:27:08.328 JavaApplicationStub[40695:1133965] int launcher_main(int, char **) [Line 925] Could not load JRE from The bundle “Java SE 8” couldn’t be loaded because its executable couldn’t be located..: (
0 CoreFoundation 0x00007fff8ff882cb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffa4d9e48d objc_exception_throw + 48
2 CoreFoundation 0x00007fff90006c3d +[NSException raise:format:] + 205
3 JavaApplicationStub 0x0000000100008644 -[Launcher launch] + 468
4 JavaApplicationStub 0x0000000100008ef5 launcher_main + 645
5 JavaApplicationStub 0x0000000100009062 main + 34
6 JavaApplicationStub 0x0000000100001504 start + 52
)
Now, I'm not sure why unpacking is necessary and if it can be explained by the particular JRE or the different Mac OS versions.
In any way, I have asked the user to install the Oracle JRE 1.8.0_161 so that we both have the exact same Java and I'll report back if this solved the problem.
However, has someone a bright idea why the Install4J launcher crashes?

How do I compile swift without any dynamic libraries?

Tring to make a "hello, world" style program to see if I can use Swift on the web by running it through emscripten to get asm.js output.
The problem is that when I compile it, its bitcode tries to link dynamic libraries. It doesn't seem like it should need to do this, or it seems like someone who understands how all these pieces fit together could tell me how to provide the file it needs (I'm willing to implement some of the functions it depends on in JavaScript, if necessary).
I have a more comprehensive explanation of the environment here, but this is the basics:
The file:
$ cat f.swift
var message = 1
Compile it to bitcode:
$ xcrun swiftc -emit-bc f.swift -o f.bc
Fail to compile the bitcode to asm.js:
$ emcc f.bc
WARNING: Linking two modules of different data layouts: '/Users/josh/.emscripten_cache/libc.bc' is 'e-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-p:32:32:32-v128:32:128-n32-S128' whereas '/Users/josh/deleteme/swift-play/f.bc' is 'e-m:o-i64:64-f80:128-n8:16:32:64-S128'
WARNING: Linking two modules of different target triples: /Users/josh/.emscripten_cache/libc.bc' is 'asmjs-unknown-emscripten' whereas '/Users/josh/deleteme/swift-play/f.bc' is 'x86_64-apple-darwin13.2.0'
Unknown specifier in datalayout string
UNREACHABLE executed at /Users/clb/emscripten-fastcomp/lib/IR/DataLayout.cpp:300!
0 opt 0x00000001086d04ae llvm::sys::PrintStackTrace(__sFILE*) + 46
1 opt 0x00000001086d07bb PrintStackTraceSignalHandler(void*) + 27
2 opt 0x00000001086d0b4c SignalHandler(int) + 412
3 libsystem_platform.dylib 0x00007fff8b0e35aa _sigtramp + 26
4 libsystem_platform.dylib 0x00007fff6492d380 _sigtramp + 3649347056
5 opt 0x00000001086d07eb raise + 27
6 opt 0x00000001086d08a2 abort + 18
7 opt 0x000000010865a7a6 llvm::llvm_unreachable_internal(char const*, char const*, unsigned int) + 198
8 opt 0x0000000108416b74 llvm::DataLayout::parseSpecifier(llvm::StringRef) + 2804
9 opt 0x0000000108415c57 llvm::DataLayout::init(llvm::StringRef) + 471
10 opt 0x000000010749b47e llvm::DataLayout::DataLayout(llvm::StringRef) + 158
11 opt 0x0000000107482ba5 llvm::DataLayout::DataLayout(llvm::StringRef) + 37
12 opt 0x000000010747943c main + 3756
13 libdyld.dylib 0x00007fff8a2865fd start + 1
Stack dump:
0. Program arguments: /Users/josh/code/emsdk_portable/clang/e1.25.0_64bit/opt /var/folders/7g/mbft22555w3_2nqs_h1kbglw0000gn/T/tmp93OFuV/a.out.bc -strip-debug -internalize -internalize-public-api-list=main,malloc,free -globaldce -pnacl-abi-simplify-preopt -pnacl-abi-simplify-postopt -enable-emscripten-cxx-exceptions -o /var/folders/7g/mbft22555w3_2nqs_h1kbglw0000gn/T/tmp93OFuV/a.out.bc.opt.bc
Traceback (most recent call last):
File "/Users/josh/code/emsdk_portable/emscripten/1.25.0/emcc", line 1224, in <module>
shared.Building.llvm_opt(final, link_opts)
File "/Users/josh/code/emsdk_portable/emscripten/1.25.0/tools/shared.py", line 1357, in llvm_opt
assert os.path.exists(target), 'Failed to run llvm optimizations: ' + output
AssertionError: Failed to run llvm optimizations:
Looks like you're out of luck here. The IR compiler is generating is not standard - it includes some private Apple changes which were not upstreamed (in particular, the data layout string is non-standard at least).
And no, it is not trying to link any dynamic libraries. It tries to link statically (at LLVM IR level) all necessary stuff, in particular, C standard library.

IO::Pty perl module cpan solaris installation

OS is SunOS 5.10 Generic_150400-01 sun4v sparc sun4v. Tried to install IO::Pty perl module via cpan. Got an error related to compiler Tried to Set the PATH env variable to /opt/solarisstudio12.3/bin and modified cpan myconfig.pm to have 'make_arg' => q[CC=/opt/solarisstudio12.3/bin/cc] . But still getting the same error.
cpan> install IO::Pty
CPAN: Storable loaded ok
Going to read /home/D99134/cpan/Metadata
Database was generated on Sat, 09 Nov 2013 06:53:04 GMT
Running install for module IO::Pty
Running make for T/TO/TODDR/IO-Tty-1.10.tar.gz
CPAN: Digest::MD5 loaded ok
CPAN: Compress::Zlib loaded ok
Checksum for /home/D99134/cpan/sources/authors/id/T/TO/TODDR/IO-Tty-1.10.tar.gz ok
Scanning cache /home/D99134/cpan/build for sizes
x IO-Tty-1.10, 0 bytes, 0 tape blocks
x IO-Tty-1.10/ChangeLog, 8192 bytes, 16 tape blocks
x IO-Tty-1.10/MANIFEST, 151 bytes, 1 tape blocks
x IO-Tty-1.10/META.yml, 612 bytes, 2 tape blocks
x IO-Tty-1.10/Makefile.PL, 13360 bytes, 27 tape blocks
x IO-Tty-1.10/Pty.pm, 8709 bytes, 18 tape blocks
x IO-Tty-1.10/README, 1686 bytes, 4 tape blocks
x IO-Tty-1.10/Tty.pm, 7526 bytes, 15 tape blocks
x IO-Tty-1.10/Tty.xs, 22244 bytes, 44 tape blocks
x IO-Tty-1.10/t, 0 bytes, 0 tape blocks
x IO-Tty-1.10/t/test.t, 7306 bytes, 15 tape blocks
x IO-Tty-1.10/try, 2880 bytes, 6 tape blocks
Removing previously used /home/D99134/cpan/build/IO-Tty-1.10
CPAN.pm: Going to build T/TO/TODDR/IO-Tty-1.10.tar.gz
Now let's see what we can find out about your system
(logfiles of failing tests are available in the conf/ dir)...
ERROR: cannot run the configured compiler '/opt/SUNWspro/bin/cc'
(see conf/compilerok.log). Suggestions:
1) The complier '/opt/SUNWspro/bin/cc' is not in your PATH. Add it
to the PATH and try again. OR
2) The compiler isn't installed on your system. Install it. OR
3) You only have a different compiler installed (e.g. 'gcc').
Either fix the compiler config in the perl Config.pm
or install a perl that was built with the right compiler
(you could build perl yourself with the available compiler).
Note: this is a system-administration issue, please ask your local
admin for help. Thank you.
make: Fatal error: No arguments to build
/usr/ccs/bin/make CC=/opt/solarisstudio12.3/bin/cc -- NOT OK
Running make test
Can't test without successful make
Running make install
make had returned bad status, install seems impossible
You have to follow the third suggestion (fixing perl's Config.pm). This is dangerous, but there's a CPAN module which allows you to do Config.pm changes on the fly: ExtUtils::FakeConfig. Just follow the instructions in the documentation.
Here's another article about editing Config.pm on perlmonks: http://www.perlmonks.org/?node_id=570684

A fatal error has been detected by the Java Runtime Environment: Internal Error ; Error: ShouldNotReachHere()

I have no idea what went wrong as I've programmed in Java for about a year and never got this error. Compiling and running in Eclipse worked just a minute ago and now I get this error:
#A fatal error has been detected by the Java Runtime Environment:
#Internal Error (classFileParser.cpp:3494), pid=4636, tid=2380
#Error: ShouldNotReachHere()
#JRE version: 6.0_25-b06
#Java VM: Java HotSpot(TM) Client VM (20.0-b11 mixed mode windows-x86 )
#If you would like to submit a bug report, please visit:
#http://java.sun.com/webapps/bugreport/crash.jsp
--------------- T H R E A D ---------------
Current thread (0x02339800): JavaThread "Unknown thread" [_thread_in_vm, id=2380, stack(0x00240000,0x00290000)]
Stack: [0x00240000,0x00290000], sp=0x0028f86c, free space=318k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x13363a]
V [jvm.dll+0x12e59b]
V [jvm.dll+0x164ce]
V [jvm.dll+0x17cff]
V [jvm.dll+0x26de5]
V [jvm.dll+0x27626]
V [jvm.dll+0x279d5]
V [jvm.dll+0x27a69]
V [jvm.dll+0x27b2c]
V [jvm.dll+0x27baa]
V [jvm.dll+0x27c8d]
V [jvm.dll+0x27f59]
V [jvm.dll+0x6c593]
V [jvm.dll+0x6c96c]
V [jvm.dll+0xf9c1c]
V [jvm.dll+0x1184bb]
V [jvm.dll+0x9eba0]
C [javaw.exe+0x1657]
C [javaw.exe+0x1e2c]
C [javaw.exe+0x8614]
C [kernel32.dll+0x13677] BaseThreadInitThunk+0x12
C [ntdll.dll+0x39f02] RtlInitializeExceptionChain+0x63
C [ntdll.dll+0x39ed5] RtlInitializeExceptionChain+0x36
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
Other Threads:
=>0x02339800 (exited) JavaThread "Unknown thread" [_thread_in_vm, id=2380, stack(0x00240000,0x00290000)]
VM state:not at safepoint (not fully initialized)
VM Mutex/Monitor currently owned by a thread: None
Dynamic libraries:
0x00400000 - 0x00424000 C:\Program Files (x86)\Java\jre6\bin\javaw.exe
0x77370000 - 0x774f0000 C:\Windows\SysWOW64\ntdll.dll
0x752e0000 - 0x753e0000 C:\Windows\syswow64\kernel32.dll
0x75200000 - 0x75246000 C:\Windows\syswow64\KERNELBASE.dll
0x76a30000 - 0x76ad0000 C:\Windows\syswow64\ADVAPI32.dll
0x76b90000 - 0x76c3c000 C:\Windows\syswow64\msvcrt.dll
0x76c40000 - 0x76c59000 C:\Windows\SysWOW64\sechost.dll
0x75940000 - 0x75a30000 C:\Windows\syswow64\RPCRT4.dll
0x74ee0000 - 0x74f40000 C:\Windows\syswow64\SspiCli.dll
0x74ed0000 - 0x74edc000 C:\Windows\syswow64\CRYPTBASE.dll
0x75a40000 - 0x75b40000 C:\Windows\syswow64\USER32.dll
0x75250000 - 0x752e0000 C:\Windows\syswow64\GDI32.dll
0x75790000 - 0x7579a000 C:\Windows\syswow64\LPK.dll
0x76790000 - 0x7682d000 C:\Windows\syswow64\USP10.dll
0x756d0000 - 0x75730000 C:\Windows\system32\IMM32.DLL
0x75600000 - 0x756cc000 C:\Windows\syswow64\MSCTF.dll
0x7c340000 - 0x7c396000 C:\Program Files (x86)\Java\jre6\bin\msvcr71.dll
0x6d7f0000 - 0x6da9f000 C:\Program Files (x86)\Java\jre6\bin\client\jvm.dll
0x74770000 - 0x747a2000 C:\Windows\system32\WINMM.dll
0x70c70000 - 0x70cbb000 C:\Windows\system32\apphelp.dll
0x6d7a0000 - 0x6d7ac000 C:\Program Files (x86)\Java\jre6\bin\verify.dll
0x6d320000 - 0x6d33f000 C:\Program Files (x86)\Java\jre6\bin\java.dll
0x77340000 - 0x77345000 C:\Windows\syswow64\PSAPI.DLL
0x6d7e0000 - 0x6d7ef000 C:\Program Files (x86)\Java\jre6\bin\zip.dll
VM Arguments:
jvm_args: -Dfile.encoding=Cp1252 -Xbootclasspath:C:\Program Files (x86)\Android\android-sdk\platforms\android-7\android.jar
java_command: elf.app.RoomInfoActivity
Launcher Type: SUN_STANDARD
Environment Variables:
CLASSPATH=.;C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip
PATH=C:/Program Files (x86)/Java/jre6/bin/client;C:/Program Files (x86)/Java/jre6/bin;C:/Program Files (x86)/Java/jre6/lib/i386;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\cygwin\bin;C:\"Program Files (x86)"\Java\jdk1.6.0_24\bin;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;C:\Program Files (x86)\Eclipse;
USERNAME=ryu_eMach_E732Z
OS=Windows_NT
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 37 Stepping 5, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows 7 Build 7600
CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 37 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, popcnt
Memory: 4k page, physical 2874176k(1587204k free), swap 5746452k(3983880k free)
vm_info: Java HotSpot(TM) Client VM (20.0-b11) for windows-x86 JRE (1.6.0_25-b06), built on Apr 14 2011 01:04:32 by "java_re" with MS VC++ 7.1 (VS2003)
time: Mon May 16 14:17:52 2011
elapsed time: 0 seconds
I had the same problem when running "pure java junit test" inside an android dev project.
so the solution was to do the following in Eclipse:
Add the std JRE to "properties --> java build path --> libraries"
While running, In the "runconfiguration --> classpath" remove Android (leaving only
std JRE)
Here is your relief for the problem :
I have a problem of running different versions of STS this morning, the application crash with the similar way as the question did.
Excerpt of my log file.
A fatal error has been detected by the Java Runtime Environment:
#a
# SIGSEGV (0xb) at pc=0x00007f459db082a1, pid=4577, tid=139939015632640
#
# JRE version: 6.0_30-b12
# Java VM: Java HotSpot(TM) 64-Bit Server VM
(20.5-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libsoup-2.4.so.1+0x6c2a1] short+0x11
note that exception occured at # C [libsoup-2.4.so.1+0x6c2a1] short+0x11
Okay then little below the line :
R9 =0x00007f461829e550: <offset 0xa85550> in /usr/share/java/jdk1.6.0_30/jre/lib/amd64/server/libjvm.so at 0x00007f4617819000
R10=0x00007f461750f7c0 is pointing into the stack for thread: 0x00007f4610008000
R11=0x00007f459db08290: soup_session_feature_detach+0 in /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 at 0x00007f459da9c000
R12=0x0000000000000000 is an unknown value
R13=0x000000074404c840 is an oop
{method}
This line tells you where the actual bug or crash is to investigate more on this crash issue please use below links to know more , but let continue the crash investigation and how i resolved it and the novelty of this bug :)
links ARE :
a fATAL ERROR JAVA THIS ONE IS GREAT LOTS OF USER!
a fATAL ERROR JAVA 2
Okay , after that here what i found out to casue of this case and why it happens a general advise.
Most of the time ,check that if u have installed , updated recently on Ubunu and Windows there are libraries like libsoup in linux whihc were the casuse of my crash.
Check also a new Hardware problem and try to investigate the Logfile which STS or Java generated and also syslog in linux by
tail - f /var/lib/messages or some other file
Then by carfully looking at those file the one you have crash log ... you can really solve the issue as follow .
sudo unlink /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
or
sudo unlink /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
Done !! Cheers!!
I've had a similar problem.
Error Log:
EAX=0x08aef338
0x08aef338 is pointing to unknown location
EBX=0x7c5e7000
0x7c5e7000: in /usr/lib/i386-linux-gnu/libsoup-2.4.so.1 at 0x7c558000
Fix:
unlink /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
Just check to see what file you're actually running when you hit the run button. I had the same issue when I wrote a "public static void main" statement in a "non-main" file of the program. I even commented it out, but it wouldn't work. This link was very helpful for me.
I just had this error and solved it by using 'Run As' and choosing 'Android Application'.
Looks like a corrupt class file. Rebuild.
Change the workspace.
I don't know the reason but this worked for me..
Hope this helps to you as well !!
I had the same problem after adding main method in one of my classes in an Android project. I just right click on the project and run it as an Android project and then it worked again!
I had faced the same issue. The command
sudo unlink /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
was also not useful as it crashed my system network and not able to connect Wi-Fi or wired lan. Later i got the solution from here.
Adding line -Dorg.eclipse.swt.browser.DefaultType=mozilla at the end of eclipse.ini or org.eclipse.swt.browser.DefaultType=mozilla at the end of /eclipse/configuration/config.ini file solved the issue.