similar to: LTSpice IV Won't Launch from the Wine Menu

Displaying 20 results from an estimated 2000 matches similar to: "LTSpice IV Won't Launch from the Wine Menu"

2011 Oct 15
2
Problem install LTspiceIV
Hi, I am a Mac osx 10.6 user. I followed this tutorial (http://web.engr.oregonstate.edu/~traylor/ece391/install_ltspice) to install wine and LTspice. After download the LTspiceIV.exe from Linear website. I put it into my home folder, and try to run "wine LTspiceIV.exe" from my terminal. Here is the error message I got: err:module:map_image Could not map section .rdata, file probably
2003 Apr 25
3
A few questions
I've spent some time looking at klibc today, and find myself in a state of some puzzlement. The 0.79 snapshot does not build against 2.5.68; it fails almost immediately, apparently due to problems with include files. I'm hesitant to try patching anything to get it building, because I can find no sign of a CVS or BK repo that I can check against, and I don't want to replicate
2007 Mar 19
1
Wine and MS Access problem
This is a MS Access problem I dont see in other posts. I have wine up and running and I now have it working with one other app, a spice cad program called scad3.exe. When I run it via wine I do get error messages, but since the program comes up and works fine any way I have been ignoring those errors. But I will list them here anyway, in case some expert can tell if they are relevant to my
2013 Nov 15
2
[LLVMdev] asan coverage
I’m waiting to see if this fixes the buildbots. Unfortunately, because they were failing all day, there are a bunch of other regressions that have come up, and I’m still working through them. It takes quite a while to run a bootstrapped LTO clang build, so it will take a while longer. I don’t have any other useful information at this point, and I share your puzzlement about how your changes
2011 Nov 09
1
Invalid 'yscale' in viewport
I tried Googling for help on this problem, but what I saw only increased my puzzlement. I found a lovely bit of code called esplot() that makes scatterplots with associated histograms and rug plots. I have been trying to use it on my own data, but the viewport routine on which it depends (I think) is choking on the data I'm trying to plot. $ Error in valid.viewport(...) : Invalid
2013 Nov 15
2
[LLVMdev] asan coverage
The bit code file produced by the stage 1 compiler for one of the files in the clang driver is corrupt and causes the linker for stage 2 to crash. On Nov 14, 2013, at 10:13 PM, Kostya Serebryany <kcc at google.com> wrote: > What are the symptoms? > > On Fri, Nov 15, 2013 at 9:37 AM, Bob Wilson <bob.wilson at apple.com> wrote: >> I’m waiting to see if this fixes the
2018 Feb 06
2
Call picked up from queue and transferred gets disconnected - about 0.01% of calls
Hi Guys I have an issue where a call is picked up from a queue. The caller asks the person who answered to attended transfer to extension 3082 (for argument's sake.) 3082 picks up the attended transfer and speaks with the outside caller picked up initially from the queue. A few seconds after 3082 has started speaking to the outside caller - 3082's call goes dead in their
2010 Jun 18
2
Problems with NTFS...
My sincere recognition for the great work developed when making Wine. I am having a problem with the version 1.2-rc3; specifically I cannot write (from applications that they run in Wine), toward NTFS partitions; the strange thing is that I can read and until erasing files (from the browser of Wine or from Xplorer2 for example). If I run Ltspice for example, I can load without problems the
2013 Nov 15
0
[LLVMdev] asan coverage
What are the symptoms? On Fri, Nov 15, 2013 at 9:37 AM, Bob Wilson <bob.wilson at apple.com> wrote: > I’m waiting to see if this fixes the buildbots. Unfortunately, because they were failing all day, there are a bunch of other regressions that have come up, and I’m still working through them. It takes quite a while to run a bootstrapped LTO clang build, so it will take a while longer.
2013 Nov 15
2
[LLVMdev] asan coverage
No, not that I am aware of. On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> wrote: > On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote: >> The bit code file produced by the stage 1 compiler for one of the files in the clang driver is corrupt and causes the linker for stage 2 to crash. > > Is AddressSanitizer involved in
2010 Sep 05
0
[LLVMdev] More DIFactory questions - still stumped
On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote: > I've carefully studied the source code of CGDebugInfo in clang as a working > example. One puzzlement is that there's a discrepancy between what the > "source level debugging with LLVM" docs say and what clang does: According > to the docs, DW_TAG_formal_parameter is used to specify a formal
2013 Nov 15
0
[LLVMdev] asan coverage
On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote: > The bit code file produced by the stage 1 compiler for one of the files in the clang driver is corrupt and causes the linker for stage 2 to crash. Is AddressSanitizer involved in any of the stages of the LTO build? > > On Nov 14, 2013, at 10:13 PM, Kostya Serebryany <kcc at google.com> wrote:
2010 Sep 05
2
[LLVMdev] More DIFactory questions - still stumped
I hate to be a nag, but after several days of working on this I am still utterly stumped. Let me recap the situation as it currently stands: I'm trying to write code that generates DWARF debugging information for my compiler using DIFactory and friends. Unfortunately the information I am generating appears to be invalid, but I can't figure out the cause. Based on the advice in the
2013 Nov 15
2
[LLVMdev] asan coverage
I don’t know yet, but I will let you know as soon as I can. On Nov 14, 2013, at 10:18 PM, Kostya Serebryany <kcc at google.com> wrote: > On Fri, Nov 15, 2013 at 10:16 AM, Bob Wilson <bob.wilson at apple.com> wrote: >> No, not that I am aware of. > > So, if my commits did indeed trigger the failures it could be > something like binary size change that caused
2013 Nov 15
0
[LLVMdev] asan coverage
On Fri, Nov 15, 2013 at 10:16 AM, Bob Wilson <bob.wilson at apple.com> wrote: > No, not that I am aware of. So, if my commits did indeed trigger the failures it could be something like binary size change that caused different code alignment or some such and which triggered a latent memory bug somewhere else. It's already late evening for you now. Will you have a chance to reapply
2005 Aug 13
1
A newhidups question
Gentlemen, I think this question is mainly for Arnaud again: When I run my UPS directly with newhidups -D -D -D, with no data changes, and I then observe the interaction with my UPS (still Back-UPS ES 650 FW:818.w1.D USB FW:w1), I see the updateinfo cycle through 3 different forms: (1) a (2 bytes) => 06 08 notification that provides one item: UPS.PowerSummary.APCStatusFlag Note that
2019 Jan 04
0
Wine release 4.0-rc5
The Wine development release 4.0-rc5 is now available. What's new in this release (see below for details): - Bug fixes only, we are in code freeze. The source is available from the following locations: https://dl.winehq.org/wine/source/4.0/wine-4.0-rc5.tar.xz http://mirrors.ibiblio.org/wine/source/4.0/wine-4.0-rc5.tar.xz Binary packages for various distributions will be available
2011 Jan 28
3
sapply puzzlement
Hi, I have this data.frame with two variables in it, > z V1 V2 1 10 8 2 NA 18 3 9 7 4 3 NA 5 NA 10 6 11 12 7 13 9 8 12 11 and a vector of means, > means <- apply(z, 2, function (col) mean(na.omit(col))) > means V1 V2 9.666667 10.714286 My intention was substracting means from z, so instictively I tried > z-means V1 V2 1 0.3333333
2013 Nov 15
2
[LLVMdev] asan coverage
Yes. I'm seeing this as well and it predates Kostya's change. Shows up as memory corruption or double free on Linux. On Nov 14, 2013 10:46 PM, "Alexey Samsonov" <samsonov at google.com> wrote: > FYI I've seen what looked like a memory corruption in (private) Clang > bootstrap process long before Kostya's changes were submitted. I hope I'll > have the
2013 Nov 15
0
[LLVMdev] asan coverage
FYI I've seen what looked like a memory corruption in (private) Clang bootstrap process long before Kostya's changes were submitted. I hope I'll have the chance to investigate it soon. On Fri, Nov 15, 2013 at 10:20 AM, Bob Wilson <bob.wilson at apple.com> wrote: > I don’t know yet, but I will let you know as soon as I can. > > On Nov 14, 2013, at 10:18 PM, Kostya