From: "Αλέξανδρος Καρυπίδης (Alexandros Karypidis)" <karypid@yahoo.gr>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Strange gdb behavior when debugging Qt apps
Date: Mon, 04 Feb 2002 11:28:00 -0000 [thread overview]
Message-ID: <200202041927.VAA02795@uth.gr> (raw)
In-Reply-To: <1020204183937.ZM17090@localhost.localdomain>
So far noone has mentioned anything in the Qt mailing list. Moreover, I
tried running gdb against standard qt apps (like qtcups) and the fonts were
ok, so it's probably not the environment.
Furthermore, it seems that this is thread-related, because it occurs only
with applications spawning other threads. For example, I ran gdb with qtella
(a Qt gnutella client which spawns threads\b) and had the same "garbled fonts"
problem.
More specifically, when gdb's output contains somethin like:
"[New Thread XXXX (LWP YYYYY)]"
Then, the fonts are garbled...
> > I am facing a rather strange problem using gdb. I have written a simple
> > Qt application which creates a window with a few menu choices. When I
> > run the application (no debugging), everything is ok. If I try to run it
> > within gdb however, the fonts used are unreadable. They letters are very
> > small and one cannot distinguish them. Does anyone have any clue
> > regading this strange behavior?
>
> In the course of starting up the process to be debugged, gdb invokes
> the shell. Could it be that a .bashrc, .cshrc, or the like is setting
> (or unsetting) an environment variable which is influencing the font
> size?
prev parent reply other threads:[~2002-02-04 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 6:48 Αλέξανδρος Καρυπίδης (Alexandros Karypidis)
2002-02-04 10:40 ` Kevin Buettner
2002-02-04 11:28 ` Αλέξανδρος Καρυπίδης (Alexandros Karypidis) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202041927.VAA02795@uth.gr \
--to=karypid@yahoo.gr \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox