Displaying 8 results from an estimated 8 matches for "_exiting_".
Did you mean:
_existing_
2017 Dec 15
1
cannot destroy connection (?) created by readLines in a tryCatch
...ecause it is more specific?
Would it make sense to turn that warning into an error?
Gabor
On Thu, Dec 14, 2017 at 11:46 PM, <luke-tierney at uiowa.edu> wrote:
> This has nothing to do with on.exit. It is an iteraction between where
> the warning is signaled in 'file' and your _exiting_ warning handler.
> This combination has the same issue,
>
> tryCatch(file(tempfile(), "r"), warning = identity)
> showConnections(all = TRUE)
>
> as does
>
> options(warn=2)
> file(tempfile(), "r")
> showConnections(all = TRUE)
>
> I haven'...
2017 Dec 14
0
cannot destroy connection (?) created by readLines in a tryCatch
This has nothing to do with on.exit. It is an iteraction between where
the warning is signaled in 'file' and your _exiting_ warning handler.
This combination has the same issue,
tryCatch(file(tempfile(), "r"), warning = identity)
showConnections(all = TRUE)
as does
options(warn=2)
file(tempfile(), "r")
showConnections(all = TRUE)
I haven't looked at the internals of 'file' but it look...
2017 Dec 14
4
cannot destroy connection (?) created by readLines in a tryCatch
On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote:
> Gabor,
>
> You can grab the connection and destroy it via getConnection and then a
> standard close call.
Yeah, that's often a possible workaround, but since this connection
was opened by
readLines() internally, I don't necessarily know which one it is. E.g.
I might open multiple
2009 Feb 26
4
[LLVMdev] Shrink Wrapping - RFC and initial implementation
...that execution paths that do not use CSRs do not pay the
spill/restore penalty.
- Avoiding placment of spills/restores in loops: if a CSR is used inside a
loop(nest), the spills
are placed in the loop preheader, and restores are placed in the loop
exit nodes (the
successors of the loop _exiting_ nodes).
- Covering paths without CSR uses: e.g. if a restore is placed in a join
block, a matching spill
is added to the end of all immediate predecessor blocks that are not
reached by a spill.
Similarly for saves placed in branch blocks.
Since I ran into a non-trivial issue in devel...
2004 Dec 31
1
Broken pipe...
...for now.
However, when I try to start Asterisk, it dies with the following
messages:
Junk at the beginning 49443303
Warning, flexibel rate not heavily tested!
Ouch ... error while writing audio data: : Broken pipe
I have googled for info on these errors - some have reported getting
them while _exiting_ Asterisk, but none have claimed to see them while
_starting_ Asterisk.
Any ideas?
Thanks a ton.
--sk.
2009 Mar 01
0
[LLVMdev] Shrink Wrapping - RFC and initial implementation
...s do not pay the
> spill/restore penalty.
>
> - Avoiding placment of spills/restores in loops: if a CSR is used
> inside a loop(nest), the spills
> are placed in the loop preheader, and restores are placed in
> the loop exit nodes (the
> successors of the loop _exiting_ nodes).
>
> - Covering paths without CSR uses: e.g. if a restore is placed in
> a join block, a matching spill
> is added to the end of all immediate predecessor blocks that
> are not reached by a spill.
> Similarly for saves placed in branch blocks.
Sounds great....
2009 Mar 01
2
[LLVMdev] Shrink Wrapping - RFC and initial implementation
...ill/restore penalty.
> >
> > - Avoiding placment of spills/restores in loops: if a CSR is used
> > inside a loop(nest), the spills
> > are placed in the loop preheader, and restores are placed in
> > the loop exit nodes (the
> > successors of the loop _exiting_ nodes).
> >
> > - Covering paths without CSR uses: e.g. if a restore is placed in
> > a join block, a matching spill
> > is added to the end of all immediate predecessor blocks that
> > are not reached by a spill.
> > Similarly for saves placed in bra...
2009 Mar 02
0
[LLVMdev] Shrink Wrapping - RFC and initial implementation
...ill/restore penalty.
> >
> > - Avoiding placment of spills/restores in loops: if a CSR is used
> > inside a loop(nest), the spills
> > are placed in the loop preheader, and restores are placed in
> > the loop exit nodes (the
> > successors of the loop _exiting_ nodes).
> >
> > - Covering paths without CSR uses: e.g. if a restore is placed in
> > a join block, a matching spill
> > is added to the end of all immediate predecessor blocks that
> > are not reached by a spill.
> > Similarly for saves placed in bra...