#1 "/TOPIC" bug with "-Os -fomit-frame-pointer -march=k6"

closed-fixed
nobody
None
3
2002-12-24
2002-05-18
Anonymous
No

When _JUST_ typing "/TOPIC" in a window lostIRC 0.0.8
bugs. It will simply terminate.

From
Glenn Sommer

Discussion

    • summary: "/TOPIC" bug --> "/TOPIC" bug
    • status: open --> open-works-for-me
     
  • Logged In: YES
    user_id=277268

    Hmm - can't reproduce it here. What system are you on?

    Can you recompile the client with ./configure --enable-debug
    and run it throught GDB?

    gdb lostirc
    > run

     
  • Logged In: NO

    I tried to unset my CFLAGS/CXXFLAGS, and then recompile
    lostsIRC 0.0.8 - now it works fine!
    With the CFLAGS/CXXFLAGS like "-fomit-frame-pointer
    -march=k6" lostIRC 0.0.8 works fine, but when adding a "-Os"
    to the CFLAGS/CXXFLAGS it bugs when using: "/TOPIC"

    From
    Glenn Sommer

     
  • Logged In: YES
    user_id=277268

    Still, which system are you on? Which compiler and which
    distribition(if Linux)?

     
    • summary: "/TOPIC" bug --> "/TOPIC" bug
     
  • Logged In: NO

    Computer system:
    CPU: AMD-k6/233mhz
    Mainboard: ASUS-p5a-b
    2xquatum hdd
    and a creative sound blaster 23 card

    testing with:
    distribition 1:
    Debian [unstable]
    GCC 2.95.4-14

    distribition 2:
    LFS 3.3
    gcc-2.95.3-2

    The error is the same it both debian and LFS
    But it's properly just an error with my sucky AMD ;)

     
  • Logged In: YES
    user_id=277268

    Still can't reproduce it here.. does it only happen on your
    Debian system when you compile the package yourself? Have
    you tried the precompiled version of LostIRC which is
    installable via apt-get?

     
    • summary: "/TOPIC" bug --> "/TOPIC" bug
     
  • Logged In: NO

    the precompiled [from apt-get] version of lostirc works fine
    on my system. It only makes an error when compiling it with
    the CFLAGS/CXXFLAGS like "-Os -fomit-frame-pointer -march=k6".

    So guess lostirc just don't like those CFLAGS ;)

     
  • Logged In: YES
    user_id=277268

    Ok, I'll assume this is just a bug in gcc and leave this bug
    open for others to see it.

    Thanks.

     
    • priority: 5 --> 3
    • summary: "/TOPIC" bug --> "/TOPIC" bug with "-Os -fomit-frame-pointer -march=k6"
    • status: open-works-for-me --> open-accepted
     
  • Logged In: YES
    user_id=277268

    /TOPIC behaviour has changed.. can you see whether the
    problem still exists with 0.1.4?

     
    • summary: "/TOPIC" bug with "-Os -fomit-frame-pointer -march=k6" --> "/TOPIC" bug with "-Os -fomit-frame-pointer -march=k6"
     
  • Logged In: YES
    user_id=277268

    This bug is most likely not there anymore, since /TOPIC
    behaviour has been changed and the function has been
    reimplemented a few times.

     
    • summary: "/TOPIC" bug with "-Os -fomit-frame-pointer -march=k6" --> "/TOPIC" bug with "-Os -fomit-frame-pointer -march=k6"
    • status: open-accepted --> closed-fixed