https://bugs.kde.org/show_bug.cgi?id=171275
Myriam Schweingruber changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=171275
Nicolas Lécureuil changed:
What|Removed |Added
CC||nlecure...@mandriva.com
--- Comment #9
https://bugs.kde.org/show_bug.cgi?id=171275
--- Comment #8 from Thomas McGuire 2009-04-14 10:59:14 ---
> Is it still reproducible? I can't reproduce bug on kmail 1.11.2 as mentioned
> by reporter or any other methods mentioned in comments
Yes, it is a known race condition,
--
Configure b
https://bugs.kde.org/show_bug.cgi?id=171275
Ruchir Brahmbhatt changed:
What|Removed |Added
Keywords||triaged
CC|
https://bugs.kde.org/show_bug.cgi?id=171275
Jaime Torres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://bugs.kde.org/show_bug.cgi?id=171275
Brian Foster changed:
What|Removed |Added
CC||brian.fos...@innova-card.co
|
http://bugs.kde.org/show_bug.cgi?id=171275
B Broeksema b broeksema home nl changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comm
http://bugs.kde.org/show_bug.cgi?id=171275
--- Comment #3 from John Baldwin 2008-09-27 16:00:43 ---
So I set a few breakpoints and here is where the application arguments are
parsed before KUniqueApplication::Start() is called:
(gdb) where
#0 KCmdLineArgsStatic::parseAllArgs ()
at
/usr
http://bugs.kde.org/show_bug.cgi?id=171275
--- Comment #2 from John Baldwin 2008-09-18 16:40:24 ---
I just realized that I had read the assertion backwards. The problem is that
some code is forcing a parse of the command line options before
KUniqueApplication::addCmdLineOptions() is called.
http://bugs.kde.org/show_bug.cgi?id=171275
--- Comment #1 from John Baldwin 2008-09-18 14:19:14 ---
Looking at the kcmdlineargs.h header, it seems that kmail is following the
documented procedure:
* // Initialize command line args
* KCmdLineArgs::init(argc, argv, appName, programN
10 matches
Mail list logo