Displaying 15 results from an estimated 15 matches similar to: "error on startup"
2006 Oct 31
0
6316708 LD_DEBUG should provide a means of identifying/isolating individual link-map lists (fix unref)
Author: rie
Repository: /hg/zfs-crypto/gate
Revision: c8b1a957b6932793bf1ec075bba368e687c7fbca
Log message:
6316708 LD_DEBUG should provide a means of identifying/isolating individual link-map lists (fix unref)
Files:
create: deleted_files/usr/src/cmd/sgs/liblddbg/common/_synonyms.h
delete: usr/src/cmd/sgs/liblddbg/common/_synonyms.h
2009 May 13
8
kernel: 4gb seg fixup messages...
Hey everyone,
I''ve searched through all of the previous posts and tried everything
mentioned but I am still getting these messages. Is there anything
else I can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My
Xen VM is also running CentOS 5.
I''ve tried doing:
# echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf && ldconfig
2016 Feb 08
2
[LLD] Incorrect comparision of pointers to function defined in DSO
Yes, I had just reduced it too.
I am pretty sure this was implemented at some point. Taking a look.
Cheers,
Rafael
On 8 February 2016 at 17:52, Sean Silva <chisophugis at gmail.com> wrote:
> Sounds like it is related to this:
>
> http://www.airs.com/blog/archives/42
> """
>
> The fact that C permits taking the address of a function introduces an
>
2016 Feb 08
3
[LLD] Incorrect comparision of pointers to function defined in DSO
Hi,
It looks like I have found a bug in LLD. Suppose DSO defines a global
variable 'data' and initializes it by the address of function
'set_data' defined in the same DSO. If an executable file (linked by
LLD) gets address of the '&set_data' function and compares it with a
value stored in the 'data' variable it gets different result. If the
executable is linked
2014 Apr 14
2
[LLVMdev] Proposal: AArch64/ARM64 merge from EuroLLVM
> - Inline ASM (I think Eric said at the Hackers Lab that he might be
> willing to do this)
I am, yes.
> - For others who want to help test, compiling and running your
> codebases on QEMU (no crypto extensions)
Some reasonable description of how this works would be awesome.
>
> - Feature parity - to the level found in the ARM64 and AArch64 backends today
As a note this
2009 Dec 01
1
LD_PRELOAD temporary patch
I've used that patch to close the hole. This patch is temporary and doesn't fix real trouble maker - problem in new version in getenv() (after 6.3 it got changed to something monstrous and non-working right if environment has only one variable), hope it will get fixed soon.
*** rtld.c.orig Tue Dec 1 16:55:13 2009
--- rtld.c Tue Dec 1 16:55:55 2009
***************
*** 357,374 ****
2016 Jun 07
1
CentOS 6, gdb
Got a user who claims he was running this program, then it broke recently.
Almost no updates in a while, and none relevant. I'm guessing the
program's compiled from fortran to c.... Anyway, the issue's on two
servers. On one, I installed a couple of compat libs, and it runs. The
other still fails (but it doesn't have some of the i686 libs. When it
fails, it's immediate, and
2001 Feb 08
2
Installling more than one wine version (fwd)
On Thu, 8 Feb 2001, Rick Moulton wrote:
> It seems that Corel Office 2000 for linux will not run on any version of
> wine later that the 1022999 ver.. Seems Any newer version causes an
> "ERROR no 6 and stuff about not being able to find "wordperfect" or
> quattropro executuables, and also saying it is a wine error.
> My question, is there a way to install
2023 Feb 01
1
dyn.load(now = FALSE) not actually lazy?
? Wed, 1 Feb 2023 14:16:54 +1100
Michael Milton <ttmigueltt at gmail.com> ?????:
> Is this a bug in the `dyn.load` implementation for R? If not, why is
> it behaving like this? What should I do about it?
On Unix-like systems, dyn.load forwards its arguments to dlopen(). It
should be possible to confirm with a debugger that R passes RTLD_NOW to
dlopen() when calling dyn.load(now =
2015 Apr 02
3
[LLVMdev] Cross Compiling LLVM's test-suite
Hi all,
I'm working in a company to port LLVM on their own processor.
I'm trying to run the test-suite, but it seems that it is usually run directly on the processor which is tested. In my case, I cannot run it on the processor, but I have a simulator on which I would like to run the test-suite.
Also, it seems to me that the test-suite start by compiling some tools that have to be run
2008 Feb 26
4
Why dtrace doesn''t work on some workstation?
Dtrace does work on some workstation, such as as follows,
-----------------------------------------------------------
bash-3.00# dtrace -s ./mem.d `pgrep test`
dtrace: script ''./mem.d'' matched 5 probes
^C
bash-3.00# uname -a
SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100
bash-3.00# dtrace -V
dtrace: Sun D 1.1
2023 Feb 01
2
dyn.load(now = FALSE) not actually lazy?
On Linux, if I have a .so file that has a dependency on another .so, and I
`dyn.load(now=FALSE)` the first one, R seems to try to resolve the symbols
immediately, causing the load to fail.
For example, I have `libtorch` installed on my HPC. Note that it links to
various libs such as `libcudart.so` and `libmkl_intel_lp64.so.2` which
aren't currently in my library path:
? ~ ldd
2003 Apr 28
1
Red Hat 9 regex symbol conflict
Hello,
I've been struggling with a problem for the past several weeks, trying
to get PL/R (R procedural language handler for PostgreSQL,
http://www.joeconway.com/plr/) to work on Red Hat 9. In brief, R dumps
core during the embedded library initialization, while in Rf_regcomp(),
working on on Rprofile. Below I've included the important parts of a
backtrace:
Program received signal
2009 Oct 23
3
rdtsc in userspace
I''m continuing to investigate the usage of rdtsc in
userspace and whether there are programs "out there"
that use it "unsafely" that might randomly break
under Xen if rdtsc is not emulated, e.g. across a migration.
Some have argued that nobody should use rdtsc and any
programs that use rdtsc directly are "fundamentally broken"
so the default for rdtsc
2010 Aug 12
59
[PATCH 00/15] RFC xen device model support
Hi all,
this is the long awaited patch series to add xen device model support in
qemu; the main author is Anthony Perard.
Developing this series we tried to come up with the cleanest possible
solution from the qemu point of view, limiting the amount of changes to
common code as much as possible. The end result still requires a couple
of hooks in piix_pci but overall the impact should be very