Some analysis of starting a Gnome session under valgrind
by Daniel Veillard
I wanted to do this for a long time but only now I had the time and
a destop beefy enough to try this. Basically I replaced /usr/bin/gnome-session
by a shell script :
#!/bin/sh
/usr/bin/valgrind --trace-children=yes --log-file=/tmp/valgrind /usr/bin/gnome-session.orig $*
Then logged on in gdm , and checked what happened from an ssh connection
top the box.
The good news:
- logging went through, but it took a few minutes
- everything looked functional though extremely slow
- there wasn't many logs reported by valgrind
The bad news:
- I had to stop the session shortly after the login fully complete
the VM was full (1G of Ram + 500M of swap)
- reports from the logs are a pain to try to analyze.
- one python (rhn applet I suspect) generated a huge log, python-2.3
doesn't seems valgrindable.
I them eliminated all the empty /tmp/valgrind.pid* files, I was left with
reports from oly 25 processes.
First a word of warning, I used the normal optimized code as shipped as
part of Fedora devel (fully up-to-date box for todays version), some
of the optimizations sometimes defeat valgrind so there may be false positive.
I have tried to sort all the reports to gather together what was frequently
reported because all apps went through the same code path, for example
there is an error reported when opening gdk display which is reported like
30 times by various apps. So what I saw most:
- gdk_display_open leading to write(buf) contains uninitialised or
unaddressable byte in __write_nocancel though _X11TransWrite
hard to tell without a debugging lib if the error is a false positive
a lack of initialization gdk_display_open() or within X. Strange thing
is that valgrind report the block as being alloc'ed with calloc()
offending address is 128 bytes inside a block of size 16384
- giop_send_buffer_write in libORBit-2 leading to
Syscall param writev(vector[...]) contains uninitialised or unaddressable byte(s)
that time the uninitialized data is 10 bytes inside a block of size 2048
allocated within orbit itself.
- pango read_line raises a strange pthread mutex error:
pthread_mutex_lock/trylock: mutex has invalid owner
in pthread_mutex_lock called by pango_read_line from pango_find_map
Apparently the GStreamer code detects it's running under valgrind and
manage to shut it up :-)
Except those 3 repeated all other the place and consisting of the bulk of
the reports, I have seen errors in:
- /usr/bin/gnome-session: invalid file descriptors,
pango_attr_list_get_iterator uninitialized value.
- /usr/bin/pam-panel-icon: 2 invalid file descriptor, seems the same
as for gnome-session with value 828 too.
- /usr/lib/libwnck: uninitialized values in _wnck_read_icons
- /usr/libexec/gconfd-2: repeated g_strdup of initialized values
from gconf_set_daemon_ior, gconf_get_lock, gconf_object_to_string,
gconf_quote_string, and an fprintf
- /usr/libexec/bonobo-activation-server: uninitialized values in
CORBA_ORB_object_to_stringr,fprintf,giop_send_buffer_write
- gam_server : I got one too :-)
- metacity: uninitialized values in gdk_window_new, gdk_window_resize,
gdk_region_rectangle, gdk_region_subtract, a couple of strange
g_int_equal bugs, meta_display_begin_grab_op, meta_display_end_grab_op
- gnome-terminal: terminal_profile_update and _vte_pty_open
The best way to double check is to do the same trick as I did for
gnome-session, move the original somewhere else, replace it by a script
calling valgrind but without recursion to child on a local copy of the
program in debugging mode.
Enclosed are the data as sorted and recouped for more informations.
happy valgrinding,
Daniel
--
Daniel Veillard | Red Hat Desktop team http://redhat.com/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
18 years, 3 months
Kernel > 2.6.5 - Serial Mouse Bug
by Parameshwara Bhat
Hello list,
I think I have a bug on hand. I want confirmation to file it as a bug.
I recntly upgraded my computers at office and home to FC2 from FC1. At
office, as smooth as it could be. At home too, it was perfect except for
one major problem in FC2 not able to drive my Serial mouse. This is an old
Celeron 460 Mhz computer with which FC1 coped admirably and had detected
my serial mouse at installation. FC2 failed to detect my serial mouse and
when properly chosen in subsequent screens, it failed to drive it.
FC2 kept my old kernel 2.4.22-1.2194.nptl while installing a new 2.6.5
kernel. I have detected a pattern in mouse not working when I boot in
2.6.5 and working always when I boot in 2.4.22 series.
This pattern is further reinforced by what happens with Knoppix - 3.6 Live
CD. Whenever I chose 2.6 seies kernel, Knoppix fails to drive my mouse,
when I let be the default kernel 2.4.2x , it never fails to detect and
drive mouse.
I have also run SUSE 9.1 with kernel 2.6.4-52 with which Serial mouse is
detected and works fine.
It seems the bug is in kernel at & above 2.6.5.
Is there anubody else who has experienced something similar? I want to
confirm before filing bug.
Parameshwara Bhat
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
18 years, 5 months
RE: FC3 background
by Jozsef Mak
Hi,
I modified slightly my second FC3 wallpaper.
Check it our here:
http://jozmak.heydo.com/wallpapers/screensavers.htm
jozsef mak
>From: Diana Fong <dfong(a)redhat.com>
>Reply-To: Discussions about development for the Fedora desktop
><fedora-desktop-list(a)redhat.com>
>To: fedora-desktop-list(a)redhat.com
>Subject: FC3 background
>Date: Fri, 08 Oct 2004 18:42:44 -0400
>
>The current Fedora background includes the version number, which does
>not match the upcoming release. If you have simple, yet attractive,
>background(s) for Fedora Core now is the time to propose it.
>
>Backgrounds should be 1600*1200 and not include the version number.
>
>~Diana
>Visual Designer, Desktop Team
>
>--
>Fedora-desktop-list mailing list
>Fedora-desktop-list(a)redhat.com
>http://www.redhat.com/mailman/listinfo/fedora-desktop-list
18 years, 5 months
FC 2 no GUI, help
by Donny
Hardware: Dell Optiplex GX260 (2yr old machine),Pentium4 @2Ghz(400MhzFSB),640MB DDR (266mhz)RAM,40GB HDD (ATA80),Imbedded intel VideoChip (64MB mem) AGP4x on PCI IRQ 9-with VGA connector), Monitor IBM 14R28 (ANCIENT;from the 1st run of the Aptiva lineup days) 13"viewable (.28dot pitch CRT-SVGA 1024x768max resolution @ 60hz).
I've setup Dual Boot Grub as my Dual boot for Fedora Core 2 @ WinXP Pro SP1. file type is set to fat32 for WinXP ->I no issues using Grub to boot WinXP.
Let me tell you my issue that I'm going BALD over (had peach fuzz before).
1)the above hardware works perfectly with WinXP ->although I can only run 800x600 res max with 16-bit@60hz, nothing more (even before Fedora).
2)I tried following RedHas instructions to the letter 3x(deleted WinXP "D:\" drive partition then Automatic install-->couldn't do it. I then tried installing Fedora with Disk Druid GUI by giving the whole partion "\"(root)+swap file (last 2BG) -->didn't help. My 5th attempt allowed installation instructions to be followed yet each and everytime, all installations seemed to go without a hitch Except at the beginning with linux couldn't recognize my monitor gave the option of choosing another
3)Rescue Disc (#5) I tried "nprobe" and "skipddc" commands both, nothing work.
4)No matter what I try I still cannot get GUI.When I select Fedora Core (instead of WinXP) at the Grub Boot Loader I get loadup scripts telling me all things, one by one, everything is [ok] - in green letter; UNTIL near the very end; I get something about monitor+check Bios settings. I have the latest BIOS install for my Dell mobo. This is very fustrating, 4 guys at work know that I cannot stand Windblows, cannot afford a Mac, and tell me Linux is the way to go!
5)Ok I dropped my pride & researched and tried again to load Fedora Core2 just to see my old nemises. I logged in as root at the prompt and I typed "startx"
I get:
(EE) i810(0): No Video BIOS modes for chosen depth.
(EE) Screen(s) found,but none have a usuable configuration
Fatal Server error:
no screens found
Please consult the X.org Foundation Support at http://wikik.X.org for help
please also check the log file at "/var/log/Xorg.0.log" for additional information
XIO: fatal IO error 104 (connection reset by perr) on X server ":0.0" after 0 request (0 known processed"
with 0 events remaining
wheeew! I even typed: gedit /etc/inittab (hoping to change the id:3:initdefault to id:5:initdefault) and I get back: (gedit:2740)Gtk-WARNING **-cannot open display.
Lastly I load Knoppix3.6 to view my HD /mnt/hda3/etc/inittab file and the setting id:5:initdefault is already present.
last information Intel 82845G/GL/GE/PE/GV chip with Intel Video Bios v.2833 modes 800x600, high color 60hz.
Can you please help me out or do I need to buy a new monitor??
18 years, 5 months
Current State of Linux Input Devices
by Timo Hoenig
Hi,
I am carrying out a survey on the current state of Linux input devices.
The results will have influence on my diploma thesis and the
corresponding project which is called Input Abstraction Layer [1].
The survey is located at: http://ial.berlios.de/survey/
Anyone who uses Linux -- either on a desktop, a laptop or both -- is
more than welcome to participate.
I appreciate every single contribution to the survey.
Best Regards,
Timo
[1] Input Abstraction Layer
Web: http://developer.berlios.de/projects/ial/
SVN: http://svn.berlios.de/viewcvs/ial/
..............................................................
Timo Hönig <thoenig at nouse dot net>
..................................................:: gpg ::...
Fingerprint: 0998 0ACA A1D2 2612 4D96 DD8B E03F 084B B305 4066
18 years, 5 months
pango on by default in mozilla builds
by Chris Blizzard
I've flipped the switch on the Mozilla package so that pango is used
for display. This means that we have a lot of good support for a lot
of languages which were lacking with the current mozilla builds. No,
it's not used for printing quite yet. That's next on the list.
Yeah, it's late in the FC3 release cycle for this kind of change but
we need to get it tested some time with a wider audience, and it's
undergone some pretty good testing. If there are big problems, I can
always switch it off again.
Happy testing!
--Chris
18 years, 5 months
RE: FC3 background
by Jozsef Mak
Hi,
These are my contributions to the wallpaper project.
http://jozmak.heydo.com/wallpapers/screensavers.htm
jozsef. mak
>From: Diana Fong <dfong(a)redhat.com>
>Reply-To: Discussions about development for the Fedora desktop
><fedora-desktop-list(a)redhat.com>
>To: fedora-desktop-list(a)redhat.com
>Subject: FC3 background
>Date: Fri, 08 Oct 2004 18:42:44 -0400
>
>The current Fedora background includes the version number, which does
>not match the upcoming release. If you have simple, yet attractive,
>background(s) for Fedora Core now is the time to propose it.
>
>Backgrounds should be 1600*1200 and not include the version number.
>
>~Diana
>Visual Designer, Desktop Team
>
>--
>Fedora-desktop-list mailing list
>Fedora-desktop-list(a)redhat.com
>http://www.redhat.com/mailman/listinfo/fedora-desktop-list
18 years, 5 months
FC3 background
by Diana Fong
The current Fedora background includes the version number, which does
not match the upcoming release. If you have simple, yet attractive,
background(s) for Fedora Core now is the time to propose it.
Backgrounds should be 1600*1200 and not include the version number.
~Diana
Visual Designer, Desktop Team
18 years, 5 months
Fedora Project Mailing Lists reminder
by Elliot Lee
This is a reminder of the mailing lists for the Fedora Project, and
the purpose of each list. You can view this information at
http://fedora.redhat.com/participate/communicate/
When you're using these mailing lists, please take the time to choose
the one that is most appropriate to your post. If you don't know the
right mailing list to use for a question or discussion, please contact
me. This will help you get the best possible answer for your question,
and keep other list subscribers happy!
Mailing Lists
Mailing lists are email addresses which send email to all users
subscribed to the mailing list. Sending an email to a mailing list
reaches all users interested in discussing a specific topic and users
available to help other users with the topic.
The following mailing lists are available. To subscribe, send email to <listname>-request(a)redhat.com
(replace <listname> with the desired mailing list name such as
fedora-list) with the word subscribe in the subject.
fedora-announce-list - Announcements of changes and events. To stay
aware of news, subscribe to this list.
fedora-list - For users of releases. If you want help with a problem
installing or using , this is the list for you.
fedora-test-list - For testers of test releases. If you would like to
discuss experiences using TEST releases, this is the list for you.
fedora-devel-list - For developers, developers, developers. If you are
interested in helping create releases, this is the list for you.
fedora-docs-list - For participants of the docs project
fedora-desktop-list - For discussions about desktop issues such as user
interfaces, artwork, and usability
fedora-config-list - For discussions about the development of
configuration tools
fedora-legacy-announce - For announcements about the Fedora Legacy
Project
fedora-legacy-list - For discussions about the Fedora Legacy Project
fedora-selinux-list - For discussions about the Fedora SELinux Project
fedora-de-list - For discussions about Fedora in the German language
fedora-es-list - For discussions about Fedora in the Spanish language
fedora-ja-list - For discussions about Fedora in the Japanese language
fedora-i18n-list - For discussions about the internationalization of
Fedora Core
fedora-trans-list - For discussions about translating the software and
documentation associated with the Fedora Project
German: fedora-trans-de
French: fedora-trans-fr
Spanish: fedora-trans-es
Italian: fedora-trans-it
Brazilian Portuguese: fedora-trans-pt_br
Japanese: fedora-trans-ja
Korean: fedora-trans-ko
Simplified Chinese: fedora-trans-zh_cn
Traditional Chinese: fedora-trans-zh_tw
18 years, 5 months
