Bug 4449 - tlclient valgrind warning about uninitialised value in Fl_X::make_xid
Summary: tlclient valgrind warning about uninitialised value in Fl_X::make_xid
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: 3.4.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-29 15:02 CET by Peter Åstrand
Modified: 2013-08-26 09:13 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Peter Åstrand cendio 2012-10-29 15:02:52 CET
Moving this issue from bug 2723, comment #7:

==12286== Conditional jump or move depends on uninitialised value(s)
==12286==    at 0x4A9256: Fl_X::make_xid(Fl_Window*, XVisualInfo*, unsigned
long) (in /home/astrand/ctc/client/tlclient/tlclient.bin)
==12286==    by 0x417C12: MainWindow::MainWindow(std::string, std::string,
std::string) (tlclient_mainwindow.cc:388)
==12286==    by 0x41076D: TLClient::runApplication() (tlclient_tlclient.cc:433)
==12286==    by 0x40FA95: main (tlclient_main.cc:288)

Google finds a few hits for this, such as
http://starurchin.org/dillo/valgrind/18ede8e10fe2910aaab38c14ffc0842106f2aae6.html.
This warning does not happen with the previous client, but I think this is
because these problems are specific to the 64 bit client. See also:

http://www.fltk.org/str.php?L2637

According to that STR, everything should be fine since r8732. Perhaps the
problem is some of our patches?

I've tried the FLTK demo programs, but cannot see the problem there.

Note You need to log in before you can comment on or make changes to this bug.