Jump to content

aheimberger

Members
 View Profile  See their activity

  • Posts

    2

  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    Roman Popov
    aheimberger got a reaction from Roman Popov in SystemC 2.3 Pretty-Printer   
    Hey Guys,
    I don't know if you know about GDB Pretty-Printer. GDB Pretty-Print let you print your debug output in a legible way. I tried to write the Pretty-Printers analyzing the SystemC 2.3 implementation and I was learning how the information is stored within the SystemC implementation. You will find the Pretty-Printer under following link. 
     
    https://github.com/AHeimberger/SystemC-2.3-Pretty-Printer
     
    On Github you will find instructions about installing the Pretty-Printer and a verification python file. Hope this Pretty-Printer helps you and does not cause to many problems. I were also able to use them within Eclipse.
    Cheers Andy

  2. Like
    maehne
    aheimberger got a reaction from maehne in SystemC 2.3 Pretty-Printer   
    Hey Guys,
    I don't know if you know about GDB Pretty-Printer. GDB Pretty-Print let you print your debug output in a legible way. I tried to write the Pretty-Printers analyzing the SystemC 2.3 implementation and I was learning how the information is stored within the SystemC implementation. You will find the Pretty-Printer under following link. 
     
    https://github.com/AHeimberger/SystemC-2.3-Pretty-Printer
     
    On Github you will find instructions about installing the Pretty-Printer and a verification python file. Hope this Pretty-Printer helps you and does not cause to many problems. I were also able to use them within Eclipse.
    Cheers Andy

  3. Like
    aheimberger
    aheimberger reacted to Philipp A Hartmann in sc_int<N>   
    Running your example program in a debugger prints the full expected information here:

    (gdb) print integer $1 = {<sc_dt::sc_int_base> = {<sc_dt::sc_value_base> = {_vptr.sc_value_base = 0x804a628}, m_val = 12, m_len = 30, m_ulen = 34}, <No data fields>} (gdb) print integer.m_val $2 = 12 Since some debugging information is present, I assume that the symbols in the linked library were not found.
    Read the INSTALL information that is part of the SystemC 2.3.0 package (quoting):
    ... Several options are available to the configure script to modify the compiler configuration and the selection of certain features: --disable-shared do not build shared library (libsystemc.so) --enable-debug include debugging symbols --disable-optimize disable compiler optimization --disable-async-updates disable request_async_update support --enable-pthreads use POSIX threads for SystemC processes As you can see, there are specific options supported by the configure script to build the library variant you want. You seem to want something like:

    ../configure --enable-debug --disable-optimize --prefix=/usr/local/systemc230 Some comments on your build process:
    This won't work reliably (if at all). You should never mess with (internal) configure/Automake variables via the environment. Pass them as arguments to the configure call instead. Secondly, use standardized user-customisation variables like CXXFLAGS here.
    ../configure --enable-debug --disable-optimize --prefix=/usr/local/systemc230 CXXFLAGS="-Werror" hth,
    Philipp
×
×
  • Create New...