Re: Glib::ustring::assign(...)



Running your application in valgrind might give more clues.

Personally I always use "a = b" rather than "a.assign(b)", but it
shouldn't make any difference.

On Thu, 2007-08-16 at 22:39 -0700, Jamiil Abduqadir wrote:
> WinXP GNU 3.4.2
> I have this statement in 
>     if(!title.empty())
>     {
>         this->ustr->assign(title); // Segmentation Fault
>     }
> Now, dbg reports that:
> #0 0x6650d384 std::string::assign(std::string const&) (??:??)
> #1 0x664d9c69 Glib::ustring::assign(Glib::ustring const&)
> (/usr/lib/gcc/i686-pc-mingw32/3.4.4/include/c
> ++/bits/basic_string.h:427)
> #2 0x00401e83 jme::Combo::Combo(Glib::ustring const&) (??:??)
> #3 0x004027ea jme::NameFrame::Init() (??:??)
> #4 0x00402c54 jme::NameFrame::NameFrame() (??:??)
> #5 0x0040649c jme::Contacts::Contacts() (??:??)
> #6 0x00409f1d jme::Jaime::Init() (??:??)
> #7 0x004097e0 jme::Jaime::Jaime() (??:??)
> #8 0x0042068e main (??:??)
>  
> Does anyone know what this error mean and/or what I can do to get rid
> of the error?
>  
>  
> T.I.A.
> _______________________________________________
> gtk-list mailing list
> gtk-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-list
-- 
murrayc murrayc com
www.murrayc.com
www.openismus.com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]