search for: traps

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

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 -> ffff82c4802170e4 (XEN) traps.c:3156: GPF...

...C 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 systems how they should report stops, especially since that is certainly something we can handle in lldb. > > For traps that lldb recognizes as ones it is using for breakpoints, it already has to handle this difference for you. But for traps we know nothing about we don't do anything special. > > I think it would be entirely reasonable that whenever lldb encounters a trap instruction that isn't one...

...'-') > temp<-ifelse(temp>=0,NA,temp) > release.diff.1<-apply(temp,2,max,na.rm=TRUE) calculates the same value for each trap, irrespective of collection day. Thanks in advance Ben -- View this message in context: http://r.789695.n4.nabble.com/Adapting-R-code-for-different-traps-tp3585215p3585215.html Sent from the R help mailing list archive at Nabble.com.

...6f4137090ec4ce858bdb0fe674774173e57 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 evalskip is zero before running traps As it is if dotrap is called with evalskip set to a nonzero value, it'll try to execute any set traps. The result is that the first command in the first set trap will be executed while the rest of the trap will be silently ignored due to evalskip. This is highly counterintuitive, even though...

...7057eae0b8bbbd512dd768f409e01 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 evalskip is zero before running traps [ dash commit d28c13e7119a605ef152a4310e9415dc7ae9b8f3 ] As it is if dotrap is called with evalskip set to a nonzero value, it'll try to execute any set traps. The result is that the first command in the first set trap will be executed while the rest of the trap will be silently ignored due...

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:

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 insertions(+), 29 deletions(-) =================================================================== --- a/drivers/lguest/interrupts_and_traps...

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 insertions(+), 29 deletions(-) =================================================================== --- a/drivers/lguest/interrupts_and_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 giving the value of $status which can be useful. --- tests/tes...

...6014ae9861e6a55 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 arguments in a trap should use status outside traps POSIX now requires that exit without arguments in a trap should return the last command status prior to executing traps. This patch implements this behaviour. Signed-off-by: Herbert Xu <herbert at gondor.apana.org.au> Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/da...

...18e7ad101 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 without arguments in a trap should use status outside traps [ dash commit da30b4b787695fbf77e5d941ff350a66ca572bcb ] POSIX now requires that exit without arguments in a trap should return the last command status prior to executing traps. This patch implements this behaviour. Signed-off-by: Herbert Xu <herbert at gondor.apana.org.au> Signed-off-by:...

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

...No, trapping is not allowed, since an overflowing add nsw is defined > to produce a poison value, which sort of explodes into undefined > behavior if it reaches a side-effect. This is to support speculative > execution. > > If you emit trapping adds for nsw, you'll see spurious traps every now > and then. > > There's a stronger form of undefined behavior, exhibited by things > like divide by zero, that permits traps. > > John > > > > On 4/15/16 7:28 PM, Manuel Jacob via llvm-dev wrote: >> Hi, >> >> In our backend, we cu...

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

...gt; >> What exactly would the semantics be if the instruction *might* trap? >> I somehow can't imagine it being useful. >> >> -Eli >> > I'm not sure I understand the question.  Instructions that are > guaranteed to trap can be optimized into unconditional traps.  So > we're talking about instructions that *might* trap in any case. > > I was saying that if the only possible effect of an instruction is a > trap, do we really want optimizers to preserve it in every case? Right... the question is, is there any language that actually has such...

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

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

...tus = nv_rd32(dev, 0x400108); + uint32_t ustatus; + int display = nouveau_ratelimit(); + + + if (!status && display) { + nouveau_graph_trap_info(dev, &trap); + nouveau_graph_dump_trap_info(dev, "PGRAPH_TRAP", &trap); + NV_INFO(dev, "PGRAPH_TRAP - no units reporting traps?\n"); + } + + /* DISPATCH: Relays commands to other units and handles NOTIFY, + * COND, QUERY. If you get a trap from it, the command is still stuck + * in DISPATCH and you need to do something about it. */ + if (status & 0x001) { + ustatus = nv_rd32(dev, 0x400804) & 0x7fffffff; +...

...025e5d19e5508 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 without arguments in a trap should use status outside traps POSIX now requires that return without arguments in a trap should return the last command status prior to executing traps. This patch implements this behaviour. Incidentally this also changes the behaviour of return without arguments in a loop conditional to use the last exit status in the body...