Please don't cross post on dev/user as it can divide discussion. On Fri, Feb 14, 2020 at 3:32 AM Daniel Gerzhoy <daniel.gerz...@gmail.com> wrote: > > Hi all, > > I've added a series of DPRINTFs into the coherence protocol (GPU_VIPER) > and its been working ok, up until this morning when I added a bunch all at > once and it started segfaulting. This only happens if I have my debug flag > enabled, otherwise the program runs to completion (this is syscall > emulation mode, apu_se.py in /examples) > > I've been trying to think of a way to figure out what the problem is using > some semblance of thought but I haven't been able to do anything so I'm > going to binary search my way through the files commenting out all of my > prints. > > In the meantime, if anyone could explain how I might use this LIBC > backtrace, either in this situation or the future, that would be amazing. >
Demangle C++ by piping trough c++filt and find exact line with addr2line: https://stackoverflow.com/questions/7648642/how-to-use-the-addr2line-command-in-linux Also try to run the program through GDB to get more visibility on state at crash. > Cheers, > > Dan Gerzhoy > > gem5 has encountered a segmentation fault > --- BEGIN LIBC BACKTRACE --- > build/GCN3_X86/gem5.opt(_Z15print_backtracev+0x28)[0x1a06bc8] > build/GCN3_X86/gem5.opt[0x1a19783] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f6d0bb39390] > build/GCN3_X86/gem5.opt(_ZlsRSoRK9MachineID+0x1c)[0x199fcac] > build/GCN3_X86/gem5.opt(_Z8ccprintfIJm9MachineID11TriggerType15Directory_StateEEvRSoPKcDpRKT_+0xebb)[0x19c2c7b] > build/GCN3_X86/gem5.opt(_ZN5Trace6Logger7dprintfIJm9MachineID11TriggerType15Directory_StateEEEvmRKNSt7__cxx1112basic_strinzgIcSt11char_traitsIcESaIcEEEPKcDpRKT_+0xcd)[0x19c316d] > build/GCN3_X86/gem5.opt(_ZN20Directory_Controller6wakeupEv+0x7a0)[0x1957130] > build/GCN3_X86/gem5.opt(_ZN10EventQueue10serviceOneEv+0xc5)[0x1a0d3b5] > build/GCN3_X86/gem5.opt(_Z9doSimLoopP10EventQueue+0x50)[0x1a25e40] > build/GCN3_X86/gem5.opt(_Z8simulatem+0xd1b)[0x1a26f2b] > build/GCN3_X86/gem5.opt[0x9bf1aa] > build/GCN3_X86/gem5.opt[0x99d167] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7852)[0x7f6d0bdf67b2] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[0x7f6d0bf2d11c] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6ffd)[0x7f6d0bdf5f5d] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[0x7f6d0bf2d11c] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f6d0bdeede9] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x613b)[0x7f6d0bdf509b] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[0x7f6d0bf2d11c] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6ffd)[0x7f6d0bdf5f5d] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[0x7f6d0bf2d11c] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f6d0bdeede9] > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[0x7f6d0be69236] > build/GCN3_X86/gem5.opt(_Z6m5MainiPPc+0x8f)[0x1a1813f] > build/GCN3_X86/gem5.opt(main+0x33)[0x8d4dd3] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f6d0a52c830] > build/GCN3_X86/gem5.opt(_start+0x29)[0x8f9dd9] > --- END LIBC BACKTRACE --- > Failed to execute default signal handler! > _______________________________________________ > gem5-dev mailing list > gem5-...@gem5.org > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
