http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2174
Summary: Wireshark fails to restart after setting the preferences
for SCCP
Product: Wireshark
Version: 0.99.7
Platform: PC
OS/Version: All
Status: NEW
Severity: Critical
Priority: High
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: arun2.b@xxxxxxxxxxx
BugsThisDependsOn: 2170
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
+++ This bug was initially created as a clone of Bug #2170 +++
Build Information:
--
The following steps can be used to reproduce the problem.
1. open wireshark
2. Edit ---> preferences ---> Protocols ----> SCCP
3. Edit "User Table"
4. Enter 140 in called_ssn and RANAP in user and leave other fields empty.
5. Click Ok and then Apply.
6. Again apply and then OK
7. Now close wireshark and restart it
8. The splash screen appears and while loading the configrations it
crashes.
The following is the back trace which we got while debuggin
with GDB.
[rncpet67: /projects/rncpet/workarea/mudayal/Wireshark/install0_99_7/bin]>
gdb wireshark
GNU gdb Red Hat Linux (6.1post-1.20040607.62rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) r
Starting program:
/export/rncpet/workarea/mudayal/Wireshark/install0_99_7/bin/wireshark
[Thread debugging using libthread_db enabled]
[New Thread -1207990592 (LWP 9832)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1207990592 (LWP 9832)]
0x0085d1d7 in ep_strndup (src=0x0, len=0) at emem.c:514
514 for (i = 0; src[i] && i < len; i++)
(gdb) bt
#0 0x0085d1d7 in ep_strndup (src=0x0, len=0) at emem.c:514
#1 0x0089242f in uat_fld_chk_range (u1=0x8f141f8, strptr=0x0, len=0,
v=0xffff, u3=0x0, err=0xbff46644) at uat.c:396
#2 0x0089d799 in uat_load_lex () at uat_load.l:177
#3 0x0089e1a2 in uat_load (uat_in=0x3, err=0xbff46698) at uat_load.l:270
#4 0x0089211a in uat_load_all () at uat.c:315
#5 0x00869815 in init_prefs () at prefs.c:1086
#6 0x00869f49 in read_prefs (gpf_errno_return=0xbff467f8,
gpf_read_errno_return=0xbff467fc, gpf_path_return=0xbff46800,
pf_errno_return=0xbff46804, pf_read_errno_return=0xbff46808,
pf_path_return=0xbff4680c) at prefs.c:1249
#7 0x08086540 in main (argc=1, argv=0xbff468e4) at main.c:2478
(gdb) q
The program is running. Exit anyway? (y or n) y
I would like to know where the configrations are stored for wireshark and what
are those files.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.