[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2017-03-04 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

Michael Mann  changed:

   What|Removed |Added

 Status|INCOMPLETE  |RESOLVED
 Resolution|--- |NOTOURBUG

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-08-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

Peter Wu  changed:

   What|Removed |Added

 Status|CONFIRMED   |INCOMPLETE
 CC||pe...@lekensteyn.nl

--- Comment #9 from Peter Wu  ---
Can you switch to a different console (Ctrl-Alt-F2) while this is the case? If
not, does SysRq + R, then Ctrl-Alt-F2 work for you?

I suspect that this is an issue with the keyboard (and mouse?) pointer being
grabbed because it is a menu. Whenever you hit a gdb breakpoint while this grab
is active, it will appear as a "lock up".

The original GDB output contains GTK stuff, are you sure you are using the Qt
UI? (Perhaps your desktop environment is interfering.)

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-03-04 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

--- Comment #8 from Kubsztal  ---
Regarding point 5: Apply a display filter (udp or tcp).

Applying the filter shall be confirmed by Enter with the list of possible
filters still visible. If filter is applied by the icon with right arrow, or by
the Enter when no list of possible filters is still visible, X is not frozen.
See attached picture.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-03-04 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

--- Comment #7 from Kubsztal  ---
Created attachment 14402
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14402=edit
applying packet filter

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-03-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

Guy Harris  changed:

   What|Removed |Added

 Status|INCOMPLETE  |CONFIRMED

--- Comment #6 from Guy Harris  ---
(In reply to Kubsztal from comment #5)
> libtool --mode=execute gdb --args wireshark -nograb
> 
> wireshark: Invalid -o flag "grab"
> [Thread 0x7fffdc7fe700 (LWP 3520) exited]
> [Thread 0x77fbd7c0 (LWP 3515) exited]
> [Inferior 1 (process 3515) exited with code 01]

If the Qt version of Wireshark can't handle Qt's command-line flags, that's a
Wireshark bug.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-03-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

--- Comment #5 from Kubsztal  ---
libtool --mode=execute gdb --args wireshark -nograb

wireshark: Invalid -o flag "grab"
[Thread 0x7fffdc7fe700 (LWP 3520) exited]
[Thread 0x77fbd7c0 (LWP 3515) exited]
[Inferior 1 (process 3515) exited with code 01]

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-02-29 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

--- Comment #4 from Guy Harris  ---
Or -nograb, as per

http://doc.qt.io/qt-4.8/debug.html

which claims that "This option is set by default when the program is running in
the gdb debugger under Linux.", but maybe that's not happening for some reason.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-02-29 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

Guy Harris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |INCOMPLETE
 Ever confirmed|0   |1

--- Comment #3 from Guy Harris  ---
What happens if you pass --nograb as one of the arguments to Wireshark when you
run it?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-02-29 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

--- Comment #2 from Kubsztal  ---
Upgrading to gdb 7.11 doesn't solve the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-02-28 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

--- Comment #1 from Kubsztal  ---
REISUB works, some issue with X then?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12199] Can't debug with gdb.

2016-02-28 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12199

Kubsztal  changed:

   What|Removed |Added

   Priority|Low |High
 CC||kubsz...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe