Qt-interest Archive, July 2007
Segmentaion fault when executed through Rational Purify
Message 1 in thread
Hi All,
I am using rational Purify tool to check memory leaks,
I had build the application using "purify", when I try to open any
dialogs which are created in constructor of MainWindow , its giving
segmentation fault,
If I build and execute my application without "purify" dialogs are
opening.
Can any one tell what may be the problem
Regards
Naveen
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
Message 2 in thread
Hi,
> I had build the application using “purify”, when I try to open any
> dialogs which are created in constructor of MainWindow , its giving
> segmentation fault,
Can you provide a stack trace?
> If I build and execute my application without “purify” dialogs are opening.
>
> Can any one tell what may be the problem
Probably a Purify bug or misuse or Purify. Are you running the latest version
of Purify? On which platform does this happen?
--
[ signature omitted ]
Message 3 in thread
naveen.kmrvm@xxxxxxxxx wrote:
> I am using rational Purify tool to check memory leaks,
>
> I had build the application using âpurifyâ, when I try to open any
> dialogs which are created in constructor of MainWindow , its giving
> segmentation fault,
>
> If I build and execute my application without âpurifyâ dialogs are opening.
>
> Can any one tell what may be the problem
Memory debuggers often do things like overwrite unused/invalid memory
with specific non-zero values to highlight issues. They may also play
with memory allocations and initialization behavior in interesting ways.
If your program is doing something stupid that it normally gets away
with, the memory debugger may be exposing the issue.
Purify really should be able to tell you _where_ it crashed and give you
some idea of what happened, so you can back-track the issue.
BTW, please get rid of your giant reams of disclaimer crap.
> www.wipro.com
Who are you guys?
You're posting huge numbers of questions, often ones that could've been
answered with some thought and a little research (think Google), or by
reading the archives and Qt documentation. I expect that sort of thing
on occasion, but the queries from wipro.com are really frequent.
--
[ signature omitted ]
