Displaying 20 results from an estimated 4110 matches for "trapped".
2017 May 28
4
[Bug 101215] New: Graphics Crash
https://bugs.freedesktop.org/show_bug.cgi?id=101215
Bug ID: 101215
Summary: Graphics Crash
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau at
2012 Dec 17
4
(XEN) traps.c:3156: GPF messages in xen dmesg
Hi,
I''m running Xen 4.2.0 with Linux kernel 3.7.0 and I''m seeing a flood of
these messages in xen dmesg:
(XEN) traps.c:3156: GPF (0060): ffff82c480159247 -> ffff82c4802170e4
(XEN) traps.c:3156: GPF (0060): ffff82c480159247 -> ffff82c4802170e4
(XEN) traps.c:3156: GPF (0060): ffff82c480159247 -> ffff82c4802170e4
(XEN) traps.c:3156: GPF (0060): ffff82c480159247 ->
2020 Mar 05
2
[lldb-dev] Continuing from dbgtrap on different targets
On 04/03/2020 21:45, Jim Ingham via llvm-dev wrote:
> As you have seen, different machine architectures do different things after hitting a trap. On x86_64, the trap instruction is executed, and then you stop, so the PC is left after the stop. On arm64, when execution halts the pc is still pointing at the trap instruction.
>
> I don't think lldb should be in the business of telling
2011 Jun 09
2
Adapting R code for different traps
Hi all,
My code:
> temp<-outer(release.days,collection.days,'-')
> temp<-ifelse(temp>=0,NA,temp)
> release.diff<-apply(temp,2,max,na.rm=TRUE)
works for one trap and does what I want. That is, it determines the time
difference between the collection date of a trap and date of parasitoid
release immediately before it, excluding releases that occurred on the same
day
2019 Jan 25
0
[klibc:update-dash] [TRAP] Make sure evalskip is zero before running traps
Commit-ID: e6ebc6f4137090ec4ce858bdb0fe674774173e57
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e6ebc6f4137090ec4ce858bdb0fe674774173e57
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Thu, 2 Oct 2014 19:49:48 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] [TRAP] Make sure
2020 Mar 28
0
[klibc:update-dash] dash: [TRAP] Make sure evalskip is zero before running traps
Commit-ID: 9d16e7c25d87057eae0b8bbbd512dd768f409e01
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=9d16e7c25d87057eae0b8bbbd512dd768f409e01
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Thu, 2 Oct 2014 19:49:48 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:54 +0000
[klibc] dash: [TRAP] Make sure
2012 Jan 16
6
Sound not working properly on Xen Dom0, but works on native
Hi,
I''m doing some testing on Ubuntu 12.04 Alpha. All sounds comes out as
static on the Dom0 system. (I can PCI passthrough the audio card to a
DomU and that works). Native sound works fine.
Linux kronos 3.2.0-8-generic-pae #15-Ubuntu SMP Wed Jan 11 15:34:57
UTC 2012 i686 i686 i386 GNU/Linux
Here is the "ubuntu-bug audio" generated report:
2007 Apr 27
0
[PATCH] lguest simplification: don't pin guest trap handlers
We don't actually need the Guest handlers mapped to avoid double
fault, just the stack pages. Thanks to Zach for confirming.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
---
drivers/lguest/interrupts_and_traps.c | 26 +-------------------------
drivers/lguest/lg.h | 2 +-
drivers/lguest/page_tables.c | 6 +++---
3 files changed, 5
2007 Apr 27
0
[PATCH] lguest simplification: don't pin guest trap handlers
We don't actually need the Guest handlers mapped to avoid double
fault, just the stack pages. Thanks to Zach for confirming.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
---
drivers/lguest/interrupts_and_traps.c | 26 +-------------------------
drivers/lguest/lg.h | 2 +-
drivers/lguest/page_tables.c | 6 +++---
3 files changed, 5
2018 Aug 01
1
[PATCH nbdkit] tests: Cancel trap in cleanup function to avoid recursive traps.
In these test functions, when a test fails, the bash ‘trap’ command
causes the cleanup function to be called. However bash does not annul
or cancel the traps when cleanup is called, so at the end of the
cleanup function when ‘exit’ is called, cleanup is called recursively.
Avoid this by cancelling the traps at the top of the cleanup function.
Also an extra debugging message is emitted here
2019 Jan 25
0
[klibc:update-dash] [BUILTIN] Exit without arguments in a trap should use status outside traps
Commit-ID: d87680c971e35a218ca10941c6014ae9861e6a55
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d87680c971e35a218ca10941c6014ae9861e6a55
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 6 Oct 2014 10:39:47 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] [BUILTIN] Exit without
[klibc:update-dash] dash: [BUILTIN] Exit without arguments in a trap should use status outside traps
2020 Mar 28
0
[klibc:update-dash] dash: [BUILTIN] Exit without arguments in a trap should use status outside traps
Commit-ID: 85a5a4a9d96c0c680597432f1e4454718e7ad101
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=85a5a4a9d96c0c680597432f1e4454718e7ad101
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 6 Oct 2014 10:39:47 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:54 +0000
[klibc] dash: [BUILTIN] Exit
2009 Sep 06
2
[LLVMdev] loads from a null address and optimizations
On Sun, Sep 6, 2009 at 3:19 PM, Kenneth Uildriks<kennethuil at gmail.com> wrote:
> It would be unfortunate in a way if "this instruction can trap and go
> there" is taken to mean "if this instruction has no effect other than
> a possible trap, the instruction and the trapping behavior *must* be
> preserved".
What exactly would the semantics be if the
2016 Apr 18
2
Is trapping allowed when an add with nsw flag overflows?
[This mail could be an answer to the other responses as well, as they
basically are the same.]
Ah, I think I understand now what poison is for. Adds are defined to
not have side-effects, so the dependence rule is needed so the optimizer
is allowed to exploit undefined behavior. Is this correct?
I forgot to mention in my original mail that our trapping arithmetic
operations are fully
2010 Aug 09
2
[LLVMdev] Overflow trap
Several instruction set architectures include arithmetic operations that can
trap on overflow, or support this feature with a separate
trap-on-overflow-flag instruction (such as the x86 INTO instruction).
I am adding a back-end to the Open Dylan compiler to generate LLVM IR. The
original back-end, which generates x86 machine code, makes use of the INTO
instruction, and the runtime turns the
2009 Sep 06
3
[LLVMdev] loads from a null address and optimizations
On Sun, Sep 6, 2009 at 3:53 PM, Kenneth Uildriks<kennethuil at gmail.com> wrote:
> On Sun, Sep 6, 2009 at 5:32 PM, Eli Friedman<eli.friedman at gmail.com> wrote:
>> On Sun, Sep 6, 2009 at 3:19 PM, Kenneth Uildriks<kennethuil at gmail.com> wrote:
>>> It would be unfortunate in a way if "this instruction can trap and go
>>> there" is taken to
2019 Jan 25
0
[klibc:update-dash] trap: Implement POSIX.1-2008 trap reset behaviour
Commit-ID: ffba488a87578bfe0704dd906466fc64a88ff488
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ffba488a87578bfe0704dd906466fc64a88ff488
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 6 Jun 2016 19:52:43 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] trap: Implement
2020 Mar 28
0
[klibc:update-dash] dash: trap: Implement POSIX.1-2008 trap reset behaviour
Commit-ID: b9c84707e06be25579b9402f740c763ed79cbdde
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=b9c84707e06be25579b9402f740c763ed79cbdde
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 6 Jun 2016 19:52:43 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:54 +0000
[klibc] dash: trap: Implement
2010 Mar 01
0
[PATCH 2/2 V2] drm/nv50: Improve PGRAPH interrupt handling.
...}
+ for (ch = 0; ch < dev_priv->engine.fifo.channels; ch++) {
+ struct nouveau_channel *chan = dev_priv->fifos[ch];
+
+ if (!chan || !chan->ramin)
+ continue;
+
+ if (trap[1] == chan->ramin->instance >> 12)
+ break;
+ }
+ NV_INFO(dev, "%s - VM: Trapped %s at %02x%04x%04x status %08x %08x channel %d\n",
+ name, (trap[5]&0x100?"read":"write"),
+ trap[5]&0xff, trap[4]&0xffff,
+ trap[3]&0xffff, trap[0], trap[2], ch);
+ }
+ nv_wr32(dev, 0x100c90, idx | 0x80000000);
+ } else if (display) {
+ NV_IN...
2019 Jan 25
0
[klibc:update-dash] [BUILTIN] Return without arguments in a trap should use status outside traps
Commit-ID: c61b2da2ec3e5c4472c1a6c64e7025e5d19e5508
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c61b2da2ec3e5c4472c1a6c64e7025e5d19e5508
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 6 Oct 2014 21:51:26 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] [BUILTIN] Return