#13404: samples/thread complains when click Menu->Thread->'Start a new thread'

2 views
Skip to first unread message

wxTrac

unread,
Aug 17, 2011, 1:00:24 AM8/17/11
to wx-...@googlegroups.com
Ticket URL: <http://trac.wxwidgets.org/ticket/13404>

#13404: samples/thread complains when click Menu->Thread->'Start a new thread'
--------------------+-------------------------------------------------------
Reporter: jchain | Owner:
Type: defect | Status: new
Priority: normal | Milestone: 2.9.3
Component: wxGTK | Version: 2.9-svn
Keywords: | Blockedby:
Patch: 0 | Blocking:
--------------------+-------------------------------------------------------
11:49:49 PM: Trace: (thread) Thread 0x7fb385457710: NEW => RUNNING.
11:49:50 PM: Trace: (thread) Thread 0x7fb385457710 started.
11:49:50 PM: Trace: (thread) Thread 0x7fb385457710 about to enter its
Entry().
../../../wx/include/wx/strvararg.h(453): assert "(argtype &
(wxFormatStringSpecifier<T>::value)) == argtype" failed in
wxArgNormalizer(): format specifier doesn't match argument type
Trace/breakpoint trap


--
Ticket URL: <http://trac.wxwidgets.org/ticket/13404>

wxTrac

unread,
Aug 17, 2011, 6:35:30 AM8/17/11
to wx-...@googlegroups.com
Ticket URL: <http://trac.wxwidgets.org/ticket/13404#comment:1>

#13404: samples/thread complains when click Menu->Thread->'Start a new thread'

---------------------+------------------------------------------------------
Reporter: jchain | Owner:
Type: defect | Status: closed

Priority: normal | Milestone: 2.9.3
Component: wxGTK | Version: 2.9-svn

Resolution: fixed | Keywords:
Blockedby: | Patch: 0
Blocking: |
---------------------+------------------------------------------------------
Changes (by VZ):

* status: new => closed
* resolution: => fixed


Comment:

(In [68757]) Use correct format specifier for thread id in the sample.

Thread id is an (unsigned) long, not just unsigned, so use "%lx" to print
it
instead of "%x" to avoid asserts in formatting code.

Closes #13404.


--
Ticket URL: <http://trac.wxwidgets.org/ticket/13404#comment:1>

Reply all
Reply to author
Forward
0 new messages