2012/9/25 Koehne Kai <Kai.Koehne@digia.com>


> -----Original Message-----
> From: ext Ruben Van Boxem [mailto:vanboxem.ruben@gmail.com]
>
> [...]
> I have now rebuilt gdb with "--disable-nls" and I believe this is the thing.
> Don't ask me why this is. The startup time reduces from ~19 seconds to 6-7
> seconds, which is the same as mingw-builds gdb.
>
> Should I report a bug for this to the gdb devs? I doubt I will be able to
> describe it well enough to be helpful, nor do I think this will have a high
> priority...

I'm not an gdb expert, but I talked to one in the office ;) He tested gdb compiled with and without Native Language Support on Linux, and couldn't measure any noticeable difference in startup time. I don't know what the priorities are for gdb these days, but sending a bug report doesn't hurt, I'd say.

Done: http://sourceware.org/bugzilla/show_bug.cgi?id=14619
 

(Speaking from a IDE developers perspective, a tool like gdb dumping output in different languages is a nightmare in the first place. But there might be people not fluent in English who want to use gdb on the command line, of course ...)

Indeed. It was an oversight on my part not to use --disable-nls in the first place. I did use it for gcc itself though, go figure :)
 

Btw, maybe the even longer delay K. Frank has noticed is because he's using a non-english system language? Just a guess ...

Regards

Kai

> Another mystery solved by your anonymous hero,

Great job! It probably has taken you quite some time to test different permutations of gdb configurations :) Thanks a lot for this...

It was actually my first guess after comparing mingw-builds scripts with mine, thankfully.


Ruben

> Ruben
>
>
>
> 2012/9/12 <andre.poenitz@nokia.com>
>
>
>       K. Frank wrote:
>       > >> Kai wrote:
>       > >>> [...] The only other
>
>       > >>> difference from the log is that rubenv's gdb also prints some
> '=cmd-param-
>       > >>> changed,param="' messages, while mingw-builds does not.
>       > >>
>       > >> What log is this?  I haven't notices gdb emitting any unexpected
> messages, but
>       > >> I'd be glad to look if this might be a hint about something.
>       > >
>       > > This is from the debugger log output of Qt Creator (Window-
> >Views->Debugger Log).
>       > > Logging the exact times a command took can be enabled in the
> context menu.
>       >
>       > Okay.  I don't use Qt Creator, so I guess I don't have this log.
>
>
>       That's also available as "normal" GDB/MI output.
>
>       You should get it when starting gdb with   -i mi  on the command
> line.
>
>       Andre'
>
>       ------------------------------------------------------------------------------
>       Live Security Virtual Conference
>       Exclusive live event will cover all the ways today's security and
>       threat landscape has changed and how IT managers can respond.
> Discussions
>       will include endpoint security, mobile security and the latest in
> malware
>       threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>       _______________________________________________
>       Mingw-w64-public mailing list
>       Mingw-w64-public@lists.sourceforge.net
>       https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public