Wireshark-bugs: [Wireshark-bugs] [Bug 9152] wireshark dumps core probably in font handling

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 11 Oct 2013 17:24:41 +0000

changed bug 9152

What Removed Added
CC   [email protected]

Comment # 8 on bug 9152 from 
The original (opencsw) user's report is much cooler than the one reported here:

~~~
bash-3.00$ wireshark
15:52:49 Main Info fill_in_local_interfaces() starts
15:52:49 Capture Msg Capture Interface List ...
15:52:49 Capture Dbg sync_interface_list_open
15:52:49 Capture Dbg sync_pipe_open_command
15:52:49 Capture Dbg read 7 indicator: S empty value
15:52:49 Capture Dbg sync_pipe_wait_for_child: wait till child closed
15:52:49 Capture Dbg sync_pipe_wait_for_child: capture child closed after
0.001s
15:52:49 Main Info fill_in_local_interfaces() ends, taking 0.021s

(wireshark:14882): Pango-CRITICAL **: file fonts.c: line 1093: assertion `str
!= NULL' failed
wireshark: Warning: fontELF not found - defaulting to Monospace 9

(wireshark:14882): GLib-CRITICAL **: g_string_append: assertion `val != NULL'
failed
15:52:49 Main Info fill_in_local_interfaces() starts
15:52:49 Main Info fill_in_local_interfaces() ends, taking 0.000s
15:52:49 Capture Msg Capture Interface List ...
15:52:49 Capture Dbg sync_interface_list_open
15:52:49 Capture Dbg sync_pipe_open_command
15:52:49 Capture Dbg read 7 indicator: S empty value
15:52:49 Capture Dbg sync_pipe_wait_for_child: wait till child closed
15:52:49 Capture Dbg sync_pipe_wait_for_child: capture child closed after
0.000s
**
ERROR:main.c:3472:main_widgets_rearrange: code should not be reached
~~~

I particularly like the "fontELF not found" bit: it looks like on that system
reading memory location 0 gives you the first byte of the (or "an") ELF
program.  Neat :-).

Also interesting is the main.c assertion: that means that prefs.gui_layout_type
isn't any of the valid values (1-6).

Me thinks that someone is clobbering all or part of prefs structure someplace
between when the prefs are set when when they're used.  If you have access to a
core file can you print out the contents of that structure (you should be able
to access it from the frame that has font_init())?

Another question: when this happens do you have a ~/.wireshark/preferences
file?

You are receiving this mail because:
  • You are watching all bug changes.