Menu

#5 segmentation fault (r31)

open-accepted
None
9
2011-01-09
2011-01-08
Anonymous
No

a segmentation fault immediatly occurs

gdb session (r31 recompiled with -g) :

marry@debian:~/bouml-ng-qt4port-r31/src$ gdb ./bouml
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) run
Starting program: /home/marry/bouml-ng-qt4port-r31/src/bouml
[Thread debugging using libthread_db enabled]
[New Thread 0xb61176c0 (LWP 5177)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb61176c0 (LWP 5177)]
0xb695743b in QTextCodec::codecForName () from /usr/lib/libQtCore.so.4
(gdb) backtrace
#0 0xb695743b in QTextCodec::codecForName () from /usr/lib/libQtCore.so.4
#1 0x084d554c in EnvDialog (this=0xbfed4ecc, conv=true, noid=false) at /usr/include/qt4/QtCore/qtextcodec.h:134
#2 0x084d73fa in EnvDialog::edit (conv=12, noid=<value optimized out>) at dialog/EnvDialog.cpp:58
#3 0x08507f5d in main (argc=1, argv=0xbfed5044) at misc/main.cpp:89

Discussion

  • Leonardo Guilherme de Freitas

    I am looking into it. Thanks for your report.

     
  • Leonardo Guilherme de Freitas

    Anybody else can confirm it?

     
  • Leonardo Guilherme de Freitas

    Do you have the file .boumlrc under your home directory?

     
  • Leonardo Guilherme de Freitas

    I noticed something very strange on your application:
    [quote]
    #2 0x084d73fa in EnvDialog::edit (conv=12, noid=<value optimized out>) at dialog/EnvDialog.cpp:58
    [/quote]

    conv should be a boolean value, not "12"... just to point out. still looking into it.

     
  • Leonardo Guilherme de Freitas

    Can you please tell the encoding you are using? Seems that this is more related to text codec used for transforming one text encoding into another.
    You can try to supress the edit dialog by touching the file ~/.boumlrc. See if the bug still happens.

    Thanks.

     
  • Anonymous

    Anonymous - 2011-01-08

    there is no .boumlrc, yes 12 is strange because the call is "EnvDialog::edit(TRUE);"

    at the office bouml works very fine, I try bouml-ng because you said "Sucesfull port to Qt4 ...", how can you say that ? you aren't credible, I've already lost enough time to compile it 4 times

     
  • Anonymous

    Anonymous - 2011-01-08

    marry@debian:~/bouml-ng-qt4port-r31/src$ touch ~/.boumlrc
    marry@debian:~/bouml-ng-qt4port-r31/src$ ./bouml

    there is a popup saying "own identifier missing or invalid" then a segmentation fault, this time conv=false

    #0 0xb6a1f43b in QTextCodec::codecForName () from /usr/lib/libQtCore.so.4
    #1 0x084d554c in EnvDialog (this=0xbfe9ac0c, conv=false, noid=true) at /usr/include/qt4/QtCore/qtextcodec.h:134
    #2 0x084d73fa in EnvDialog::edit (conv=false, noid=<value optimized out>) at dialog/EnvDialog.cpp:58
    #3 0x084d87fb in read_boumlrc () at dialog/EnvDialog.cpp:662
    #4 0x08507f62 in main (argc=1, argv=0xbfe9b064) at misc/main.cpp:93

     
  • Leonardo Guilherme de Freitas

    • assigned_to: nobody --> lgfreitas
     
  • Leonardo Guilherme de Freitas

    Please understand that this code is experimental and probably it will fail. Can you confirm that BoUML by Bruno Page's works under your machine? Since you said "at the office" and the file .boumlrc is missing, I can guess that you are trying to use it under your home machine. If BoUML works you will be presented with a dialog that you must put your personal ID. Put a number between 2 and 15, close BoUML and try to run bouml-ng and tell me the results.

    Thanks.

     
  • Anonymous

    Anonymous - 2011-01-08

    lol, I confirm it fails, and being "experimental" you can't say the port to Qt4 is done in the news

    I already work with bouml at home, but on an old pc, now I have a new PC and install it. I just install bouml 4.4.2 and *of course* it works fine, I had not seen before the packages for Debian are now available on the Bouml, I installed the 4.23-p1 and didn't see problem up to now, I will do more tests this afternoon and probably will recommand it at work

     
  • Leonardo Guilherme de Freitas

    I know you can confirm, you are the bug reporter. I asked for anybody *else*. Hopefully if there are more people having this bug, we can work on it. Lets not discuss anything else, but this bug report, as it is what this place is for. Since it *of course* works fine, can you try to run bouml-ng after running bouml?

    Thanks for your help.

     
  • Anonymous

    Anonymous - 2011-01-09

    I can't test bouml-ng when .boumlrc exists because I removed it, please understand we need a bouml* working fine. The list of features added since the 4.4.2 is incredible, the 4.23 removes bugs and adds new features, why are you working on the 4.22.2 ?

     
  • Robert Allen

    Robert Allen - 2011-01-09

    Please read the project description.

    "please understand we need a bouml* working fine"

    Then please understand that the pre-alpha qt4 port is not what you are looking for!

    This is for bug testing of pre-alpha code in mid-conversion.

     
  • Leonardo Guilherme de Freitas

    I am able to compile and run it and no one else confirmed this yet. If somebody else confirm, I will reopen it.

     
  • Leonardo Guilherme de Freitas

    • status: open --> closed-works-for-me
     
  • Anonymous

    Anonymous - 2011-01-09

    Frankly I hesitate before to interfere because of the management you did with Bruno and Marry.

    Let me give you this advice : do not close a tracker because YOU can't reproduce a problem, else don't hope people will signal bug later.

    I confirm the crash signaled by Marry, it is not random but occurs each time when .boumlrc doesn't exist. With a valid .boumlrc there is no crash, but strangly the dialog "greetings" appears, I think you have to remove it or to adapt it. After there are a lot of bugs, historic doesn't work, file browser randomly reset the directory or don't enter in a directory when asking for, working on a diagram the elements or their name randomly disapear etc.

    Rather than to close the tracker take time to install a Lenny and you will see by yourself

     
  • Leonardo Guilherme de Freitas

    As I said, if someone else confirm, I will reopen this bug, As I am doing now. As for the other bugs, I am well aware of them. Now I know it is not a random bug, I will work on it.
    Many thanks for confirming it.

    As rageek said, this is not a stable release and we are working towards stabilizing the changes, as they were many.

    Thanks again.

     
  • Leonardo Guilherme de Freitas

    • status: closed-works-for-me --> open-accepted
     
MongoDB Logo MongoDB