search for: stacktraces

Hi, I'm not sure where to ask this question, you, redhat or netfilter so I'll ask you guys first, hoping you can redirect me where this post belongs. I have an issue with my CentOS 6 box with named chains in iptables. Apparently there is a builtin #define to limit chain names up to 30 chars, but the test condition fails and iptables crashes with a stacktrace. # cat /etc/redhat-release

I'm going to show the same function, first normally, and then as a coroutine, and show how gdb can see the variable when it's a normal function, but not when it's a coroutine. I'd like to understand if this can be improved. I'm trying to debug a real world problem, but the lack of debug info on variables in coroutines is making it difficult. Should I file a bug? Is this a

Would it make sense to add the possibility to print a stacktrace also on SIGFPE and not only on SIGSEGV or SIGBUS? Only noticed that LibFuzzer doesn't generate any crash report because asan is not handling the signal. Kind regards, Karl Skomski -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am updating our out-of-tree copy of LLVM to track the head (revision #272991 specifically). I have it building successfully with VC++ 2013 and CMake v3.5.2 on Windows, and with GCC v4.8.5 and CMake v3.5.2 on CentOS; but when I try building on Windows using Cygwin32 I get the following build failures: [ 4%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.o In file

On Fri, Jul 31, 2015 at 5:15 AM, Karl Skomski <karl at skomski.com> wrote: > Would it make sense to add the possibility to print a stacktrace also on > SIGFPE and not only on SIGSEGV or SIGBUS? > Yes, under a separate flag (handle_sigfpe=1). I think it's fine to have this flag on by default. Would you like to contribute a patch? > Only noticed that LibFuzzer doesn't

Hi, I must be missing something or have something misconfigured, but I get no stack-trace when there is an error in the code behind a view. If the view doesn''t compile, then I see an error & stacktrace, but all other errors I get a "lost network connection" from the browser, and nothing at all in the server output or development.log. It''s been that way with

From: Joerg Roedel <jroedel at suse.de> Make the stack unwinder aware of the IST stacks for the #VC exception handler. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- arch/x86/include/asm/cpu_entry_area.h | 1 + arch/x86/include/asm/sev-es.h | 13 ++++++++ arch/x86/include/asm/stacktrace.h | 4 +++ arch/x86/kernel/dumpstack_64.c | 47

...red in the Java code. If there's no way to do this, I'm just going to have to send every System.out/err statement in my code to a log file which is a very ugly way of doing debugging. Thanks, Adam -- View this message in context: http://r.789695.n4.nabble.com/rJava-System-out-System-err-stacktraces-tp4270712p4270712.html Sent from the R devel mailing list archive at Nabble.com.

My frontend is emitting an array (here called %error_return_trace_addresses). You can see we take the address of the first element and store it ; Function Attrs: nobuiltin noinline nounwind optnone define internal fastcc i8* @failing(%StackTrace* nonnull, %Allocator*, i16*) unnamed_addr #3 !dbg !273 { Entry: %error_return_trace_addresses = alloca [1 x i64], align 8 %error_return_trace =

I''ve installed SXDE (snv_89) and found that the web console only listens on https://localhost:6789/ now, and the module for ZFS admin doesn''t work. When I open the link, the left frame lists a stacktrace (below) and the right frame is plain empty. Any suggestions? I tried substituting different SUNWzfsgr and SUNWzfsgu packages from older Solarises (x86/sparc, snv_77/84/89,

Googling indicates that cygwin doesn't have that functionality. Or, at least, didn't in 2010, when someone asked about the same problem: https://cygwin.com/ml/cygwin/2010-01/msg00596.html "cygwin has only dlsym() not the SGI DL_info + dladdr() yet. clang just needs it to get the path for the CIndex dll. This should be possible with the code in the LLVM_ON_WIN32 section, and convert

Greetings, I implemented a proof of concept of something I'm calling "error return traces" in my frontend (screenshot and explanation at this link): https://github.com/zig-lang/zig/pull/684 Now I'm trying to minimize the runtime size. Here's some example IR that I generate: define internal fastcc i16 @baz1(%StackTrace* nonnull) unnamed_addr #2 !dbg !69 { Entry: %1 =

On Fri, 24 Aug 2018 22:06:01 +0200 Waishon <waishon009 at gmail.com> wrote: > Hi, > > thanks for your suggestions. Do you think this is causes the > stacktrace above? . I just added "REALM" as a placeholder and it > worked on a DC that was provisioned using Samba 4.7.3 and upgraded > afterwards to Samba 4.8.4 absolutely fine with this config and the > command

If I do get :index response.should_be_success I get about 20k of marshalled dumpage that starts like #<ActionController::TestResponse:0x390443c @body=\"<html><body>You are being <a href=\"http://test.host/carts/1\">redirected</a>.</body></html>\", @assigns=[], @redirected_to={:action=>\"show\", :id=>1},

On Thu, 2020-04-02 at 17:35 +0200, jesper at krogh.cc wrote: > Kernel. 5.4.26 and Ceph Luminous > > Seem to be working still but I got this after putting load on it. > > [ 785.581198] kworker/3:2: page allocation failure: order:0, > mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 (cc'ing virtualization mailing list) Basically, looks like the kernel needed

Hi, while doing work, my luks encrypted btrfs home got a nice stacktrace i run a Debian testing and a kernel 3.4 vanilla % uname -a Linux Klappe2 3.4.0 #2 SMP Thu Jun 14 03:02:37 CEST 2012 x86_64 GNU/Linux the box is a dell xps m 1330 with about 4gb ram % btrfs fi show Label: ''home'' uuid: 9c1a77c9-3767-43aa-908d-0bae1ef4e534 Total devices 1 FS bytes used 198.25GB devid

Hi! i notice a serious regression with 3.5 as Dom0 kernel (3.4 was rock stable): 1st: only the GPU PCI Passthrough works, the PCI USB Controller is not recognized within the DomU (HVM Win7 64) Dom0 cmdline is: ro root=LABEL=dom0root xen-pciback.hide=(08:00.0)(08:00.1)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) security=apparmor noirqdebug nouveau.msi=1 Only 8:00.0 and 8:00.1 get passed through

So I got tired of LLVM's PrintStackTrace() function only being able to print mangled C++ names. I went ahead and wrote a demangler (shown below), however there's one slight problem, which is that the output of backtrace_symbols appears to be different on different platforms. In order to use the cxxabi demangler, you need to provide it with the portion of each line that contains the

I'm trying to get a stacktrace, so I can't provide one. I'm trying llvm 2.7 right now. I'm hoping there's a 2.6 workaround, though. On 8/10/10 2:01 PM, "Török Edwin" <edwintorok at gmail.com> wrote: On Tue, 10 Aug 2010 13:42:05 -0600 "Bueno, Denis" <denbuen at sandia.gov> wrote: > Hello, > http://www.opendylan.org/~housel/bcdump.pl

From: Joerg Roedel <jroedel at suse.de> The get_stack_info functionality is needed in the entry code for the #VC exception handler. Provide a version of it in the .text.noinstr section which can be called safely from there. Signed-off-by: Joerg Roedel <jroedel at suse.de> Link: https://lore.kernel.org/r/20200724160336.5435-47-joro at 8bytes.org --- arch/x86/include/asm/stacktrace.h