search for: 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

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 ja...

...Start\ Menu/LTspice\ IV.lnk I've listed all the paths in both commands and all the files exist in the correct sub directories. I also checked the lines to make sure that all the spaces and \'s were escaped properly. I'm really at a loss as to where the missing file is. The other real puzzlement to me was the /Unix of the menu command, but I'm not familiar with the syntax of this command, I'm not a software engineer by any means. I did a : sudo find / -name \/Unix -type d and got no return. At that point I just thought that maybe the command was off into the cloud to retrieve...

...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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. I will keep you posted. On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: > Also, when are you planing to "reapply the changes or help debug&quot...

...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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. >> >> I will keep you posted. >> >> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: >> >>> Also, when are you pl...

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(...) : In...

...ng to the outside caller - 3082's call goes dead in their handset. - The outside caller goes back into the queue, hears queue MOH and gets answered by another person in the office as if they are dialing in all over again. - 3082's phone starts ringing again after they hang up in puzzlement and if they then pick up they speak to another person who is trying to make an OUTGOING call in their call center. This is for a medium sized call center which (along with 17 other centers in the same country) run the same dialplan on Asterisk 1.8.32.3 - only happens at this location. Liter...

Hello, Yesterday I "subversioned" my app using svn and now everything works fine except I don''t see any log entries in development.log? What would cause the log entries to be not produced anymore? Thanks Frank --------------------------------- Bring words and photos together (easily) with PhotoMail - it''s free and works with Yahoo! Mail.

..., 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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. >>>> >>>> I will keep you posted. >>>> >>>> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: >>>...

...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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. > > I will keep you posted. > > On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: > >> Also, when are you planing to "reapply the...

..., which doesn't prevent the problem from occurring. (Since my current understanding is that CIE and FDE are used to describe the call frame, I'm trying to simplify the problem as much as possible.) 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 parameter in a function type descriptor, but according to a code search, the name "DW_TAG_for...

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 parameter > in a function type descriptor, but according to a code search, the name &...

...g 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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. >>> >>> I will keep you posted. >>> >>> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: >>> >>>>...

...nch 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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. >>>>>> >>>>>> I will keep you posted. >>>>>> >>>>>> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at go...

...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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. >>>>> >>>>> I will keep you posted. >>>>> >>>>> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote...

...nent UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired UPS.PowerSummary.PresentStatus.NeedReplacement UPS.PowerSummary.PresentStatus.OverLoad Note that these are all events that appear through HIDGetEvents() in upsdrv_updateinfo(), and all relevant elements are updated there. Here is my puzzlement: If I run with the default poll_interval (which first applies to dstate_poll_fds(), but indirectly also controls the upsdrv_updateinfo() frequency), there are updates roughly every 2 sec, as expected, and the three forms seem to cycle like this: (1) (2) (1) (2) (1) (2) (1) (2) (1) (2) (1) (2) (1...

...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 could possibly break the >> compiler. My only hypothesis is some sort of memory corruption. >> >>>>>> >> >>>>>> I will keep you posted. >> >>>>>> >> >>>>>> On Nov 14, 2013,...

...> 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 could possibly break the > compiler. My only hypothesis is some sort of memory corruption. > >>>>>> > >>>>>> I will keep you posted. > >>>>>> > >>>>>> On Nov 14, 2013, at 9:22 PM, Kostya S...

I''m working with the agile rails book (latest rev), and have encountered more show stoppers than I woud have expected. The lastest one is rather worrying. Page 57 is somewhat notorious for breaking. There are all sorts of blogs etc about breakage and fixes since roughly Nov 05. Rails 0.14.1 and the Broken Depot Steel rails through my skull Even back then, the breakage was known and

...her 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 could possibly break the compiler. My only hypothesis is some sort of memory corruption. > >>>>>> > >>>>>> I will keep you posted. > >>>>>> > >>>>>> On Nov 14, 2013, at 9:22 PM, Kostya Serebr...