public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
@ 2011-09-09 9:16 ` blue.dragan+sourceware at gmail dot com
2011-09-09 15:37 ` pedro at codesourcery dot com
` (8 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: blue.dragan+sourceware at gmail dot com @ 2011-09-09 9:16 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
ChrisD <blue.dragan+sourceware at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |blue.dragan+sourceware at
| |gmail dot com
--- Comment #7 from ChrisD <blue.dragan+sourceware at gmail dot com> 2011-09-08 20:52:06 UTC ---
I am hitting the same bug on quad core ARM. gdb is crashing with SIGILL in
ldlinux-3.so or in libpthread.so apparently in the debugged process.
I'm using gdb-7.2 and I tried various glibc (including 2.13) but all other
programs work fine, only gdb hits this problem.
gdb is almost unusable, because it's crashing on every run very quickly.
I am glad to have found this bug - setting scheduler affinity indeed makes the
crashes go away.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
2011-09-09 9:16 ` [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system blue.dragan+sourceware at gmail dot com
@ 2011-09-09 15:37 ` pedro at codesourcery dot com
2011-09-10 17:29 ` blue.dragan+sourceware at gmail dot com
` (7 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: pedro at codesourcery dot com @ 2011-09-09 15:37 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
Pedro Alves <pedro at codesourcery dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |pedro at codesourcery dot
| |com
--- Comment #8 from Pedro Alves <pedro at codesourcery dot com> 2011-09-09 10:56:36 UTC ---
Please try with gdb 7.3, and paste the session so we can see the problem for
ourselves. From the older posts, it's not gdb that is crashing with SIGILL,
but
the program:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 1083503760 (LWP 351)]
0x4002639c in __nptl_death_event () from /lib/libpthread.so.0
Continuing from this resulted in a gdb internal error. I believe the latter
to be fixed nowadays.
The SIGILL could be explained by completely different problems, several not
really gdb's fault, but looks like something going wrong around the thread
death event breakpoint. Please show a session with both "set debug infrun 1"
and "set debug lin-lwp 1" issued before issuing "run". That will activate
gdb's run control debug messages and may help identify the problem.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
2011-09-09 9:16 ` [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system blue.dragan+sourceware at gmail dot com
2011-09-09 15:37 ` pedro at codesourcery dot com
@ 2011-09-10 17:29 ` blue.dragan+sourceware at gmail dot com
2011-09-10 17:43 ` blue.dragan+sourceware at gmail dot com
` (6 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: blue.dragan+sourceware at gmail dot com @ 2011-09-10 17:29 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
--- Comment #9 from ChrisD <blue.dragan+sourceware at gmail dot com> 2011-09-10 17:25:57 UTC ---
Hi Pedro, please find the requested output below. This was on a trivial C++
program. This is the most typical outcome. I agree this does not necessarily
have to be a gdb bug, since the crash *appears* to be in glibc. This run was
with glibc-2.11.3, but I've tried 2.13 before and it had the same outcome. No
other app I've tried crashes with SIGILL, therefore I suspect gdb must be doing
something that causes this crash, maybe it's just revealing a glibc bug? Again,
the crash disappears if I limit gdb to only one CPU.
$ gdb --args ./a
GNU gdb (Gentoo 7.3.1 p1) 7.3.1
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "armv7a-unknown-linux-gnueabi".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /home/chris/test/a...done.
(gdb) set debug infrun 1
(gdb) set debug lin-lwp 1
(gdb) b main
Breakpoint 1 at 0xf25c: file a.cpp, line 6.
(gdb) r
Starting program: /home/chris/test/a
linux_nat_wait: [process 827]
LLW: waitpid 827 received Trace/breakpoint trap (stopped)
LLW: Candidate event Trace/breakpoint trap (stopped) in process 827.
LLW: trap ptid is process 827.
LLR: Preparing to resume process 827, 0, inferior_ptid process 827
RC: Not resuming sibling process 827 (not stopped)
LLR: PTRACE_CONT process 827, 0 (resume event thread)
linux_nat_wait: [process 827]
LLW: waitpid 827 received Trace/breakpoint trap (stopped)
LLW: Candidate event Trace/breakpoint trap (stopped) in process 827.
LLW: trap ptid is process 827.
infrun: proceed (addr=0x4004b8b0, signal=0, step=0)
infrun: resume (step=0, signal=0), trap_expected=0
LLR: Preparing to resume process 827, 0, inferior_ptid process 827
RC: Not resuming sibling process 827 (not stopped)
LLR: PTRACE_CONT process 827, 0 (resume event thread)
infrun: wait_for_inferior (treat_exec_as_sigtrap=0)
linux_nat_wait: [process -1]
LLW: waitpid 827 received Trace/breakpoint trap (stopped)
LLW: Candidate event Trace/breakpoint trap (stopped) in process 827.
LLW: trap ptid is process 827.
infrun: target_wait (-1, status) =
infrun: 827 [process 827],
infrun: status->kind = stopped, signal = SIGTRAP
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x40059d64
bpstat_what: bp_shlib_event
infrun: BPSTAT_WHAT_SINGLE
infrun: no stepping, continue
infrun: resume (step=1, signal=0), trap_expected=1
LLR: Preparing to resume process 827, 0, inferior_ptid process 827
LLR: PTRACE_CONT process 827, 0 (resume event thread)
infrun: prepare_to_wait
linux_nat_wait: [process -1]
LLW: waitpid 827 received Trace/breakpoint trap (stopped)
LLW: Candidate event Trace/breakpoint trap (stopped) in process 827.
LLW: trap ptid is process 827.
infrun: target_wait (-1, status) =
infrun: 827 [process 827],
infrun: status->kind = stopped, signal = SIGTRAP
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4004e11c
infrun: software single step trap for process 827
infrun: no stepping, continue
infrun: resume (step=0, signal=0), trap_expected=0
LLR: Preparing to resume process 827, 0, inferior_ptid process 827
RC: Not resuming sibling process 827 (not stopped)
LLR: PTRACE_CONT process 827, 0 (resume event thread)
infrun: prepare_to_wait
linux_nat_wait: [process -1]
LLW: waitpid 827 received Illegal instruction (stopped)
LLW: Candidate event Illegal instruction (stopped) in process 827.
infrun: target_wait (-1, status) =
infrun: 827 [process 827],
infrun: status->kind = stopped, signal = SIGILL
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4004e11c
infrun: random signal 4
Program received signal SIGILL, Illegal instruction.
infrun: stop_stepping
0x4004e11c in ?? () from /lib/ld-linux.so.3
(gdb) bt
#0 0x4004e11c in ?? () from /lib/ld-linux.so.3
#1 0x4004e11c in ?? () from /lib/ld-linux.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (2 preceding siblings ...)
2011-09-10 17:29 ` blue.dragan+sourceware at gmail dot com
@ 2011-09-10 17:43 ` blue.dragan+sourceware at gmail dot com
2011-09-10 18:09 ` pedro at codesourcery dot com
` (5 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: blue.dragan+sourceware at gmail dot com @ 2011-09-10 17:43 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
--- Comment #10 from ChrisD <blue.dragan+sourceware at gmail dot com> 2011-09-10 17:29:00 UTC ---
One more thought. Since the log I posted comes from running gdb on a single
threaded program, maybe the problem is some interaction between the two
processes. Maybe the debugged program runs on a different CPU? Maybe a cache
flush or something similar is missing in gdb when it writes the code segment
when setting up breakpoints? The failure is intermittent, so this looks like
some sort of a race condition.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (3 preceding siblings ...)
2011-09-10 17:43 ` blue.dragan+sourceware at gmail dot com
@ 2011-09-10 18:09 ` pedro at codesourcery dot com
2011-09-11 8:29 ` blue.dragan+sourceware at gmail dot com
` (4 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: pedro at codesourcery dot com @ 2011-09-10 18:09 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
--- Comment #11 from Pedro Alves <pedro at codesourcery dot com> 2011-09-10 17:42:55 UTC ---
Yes, I'd suspect something like that. If there's a flush missing, it'll be a
bug on the kernel side --- ptrace does that for us. (It's a common-ish kernel
bug on new ports.)
In this particular case, the crash happens while stepping over a magic
breakpoint gdb sets in libc, to be able to track DSO loads/unloads. We call
this the shlib event breakpoint.
> infrun: stop_pc = 0x40059d64
> bpstat_what: bp_shlib_event
Here it is being hit.
> infrun: BPSTAT_WHAT_SINGLE
GDB decides it should single-step past this breakpoint. (remove the
breakpoint, single-step, reinsert, resume)
At this point, the breakpoint is removed.
> infrun: no stepping, continue
> infrun: resume (step=1, signal=0), trap_expected=1
Single-step. But arm-linux doesn't support single-steps, actually.
So instead, GDB computed the possible destinations the instruction could take,
places magic breakpoints there, and lets the thread run until one of the
possible destinations is hit.
> LLR: Preparing to resume process 827, 0, inferior_ptid process 827
> LLR: PTRACE_CONT process 827, 0 (resume event thread)
Here's the resume.
> infrun: prepare_to_wait
> linux_nat_wait: [process -1]
> LLW: waitpid 827 received Trace/breakpoint trap (stopped)
> LLW: Candidate event Trace/breakpoint trap (stopped) in process 827.
> LLW: trap ptid is process 827.
> infrun: target_wait (-1, status) =
> infrun: 827 [process 827],
> infrun: status->kind = stopped, signal = SIGTRAP
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4004e11c
> infrun: software single step trap for process 827
Alright, "software single-step" complete. The program moved like:
0x40059d64 -> 0x4004e11c
> infrun: no stepping, continue
> infrun: resume (step=0, signal=0), trap_expected=0
And here we let the program run free again, since we've successfully
moved past the breakpoint we wanted to step over.
> LLR: Preparing to resume process 827, 0, inferior_ptid process 827
> RC: Not resuming sibling process 827 (not stopped)
> LLR: PTRACE_CONT process 827, 0 (resume event thread)
> infrun: prepare_to_wait
> linux_nat_wait: [process -1]
> LLW: waitpid 827 received Illegal instruction (stopped)
> LLW: Candidate event Illegal instruction (stopped) in process 827.
> infrun: target_wait (-1, status) =
> infrun: 827 [process 827],
> infrun: status->kind = stopped, signal = SIGILL
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4004e11c
> infrun: random signal 4
Yet, the instruction at 0x4004e11c doesn't execution -- the kernel claims it's
an illegal instruction.
I suggest disassembling 0x40059d64 and making sure it looks like the next
instruction to execute would really be 0x4004e11c. And then, disassembling
0x4004e11c, trying to understand if it really should be a valid instruction, or
if we're pointing somewhere in the middle of garbage.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (4 preceding siblings ...)
2011-09-10 18:09 ` pedro at codesourcery dot com
@ 2011-09-11 8:29 ` blue.dragan+sourceware at gmail dot com
2011-09-12 18:29 ` blue.dragan+sourceware at gmail dot com
` (3 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: blue.dragan+sourceware at gmail dot com @ 2011-09-11 8:29 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
--- Comment #12 from ChrisD <blue.dragan+sourceware at gmail dot com> 2011-09-10 18:08:10 UTC ---
This is from another run (different addresses):
This is the first instruction (from bpstat_what: bp_shlib_event):
(gdb) x/i 0x40013d64
0x40013d64: bx lr
This instruction is used to return from a function.
This is the instruction at which it hit a SIGILL:
Program received signal SIGILL, Illegal instruction.
infrun: stop_stepping
0x400087d4 in ?? () from /lib/ld-linux.so.3
(gdb) x/i 0x400087d4
=> 0x400087d4: bl 0x4000d7f0
Here's the target of this jump:
(gdb) x/i 0x4000d7f0
0x4000d7f0: push {r4, r5, r6, lr}
All this looks good.
Can you point me in the right direction about ptrace? I'm running kernel 2.6.36
(Android K36) and I can't upgrade it. If there is a bug in ptrace indeed, maybe
I can find out whether there was a bug filed for this and check whether it was
fixed in newer kernels, then apply that fix to my kernel.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (5 preceding siblings ...)
2011-09-11 8:29 ` blue.dragan+sourceware at gmail dot com
@ 2011-09-12 18:29 ` blue.dragan+sourceware at gmail dot com
2014-07-19 14:31 ` will.newton at gmail dot com
` (2 subsequent siblings)
9 siblings, 0 replies; 17+ messages in thread
From: blue.dragan+sourceware at gmail dot com @ 2011-09-12 18:29 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
--- Comment #13 from ChrisD <blue.dragan+sourceware at gmail dot com> 2011-09-12 15:51:19 UTC ---
Looking at ptrace.c for ARM in the Linux kernel, it looks like the file has
significant changes in kernel 2.6.39 compared to 2.6.36, the most apparent
change being support for hardware breakpoints. There doesn't seem to be any
straightforward fixes though. We will likely be moving to 2.6.39 soon, I will
try gdb on it and update this bug.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (6 preceding siblings ...)
2011-09-12 18:29 ` blue.dragan+sourceware at gmail dot com
@ 2014-07-19 14:31 ` will.newton at gmail dot com
2014-07-19 17:51 ` blue.dragan+sourceware at gmail dot com
2014-07-20 8:09 ` will.newton at gmail dot com
9 siblings, 0 replies; 17+ messages in thread
From: will.newton at gmail dot com @ 2014-07-19 14:31 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=10833
Will Newton <will.newton at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |will.newton at gmail dot com
--- Comment #14 from Will Newton <will.newton at gmail dot com> ---
Any update on this issue? Are you still seeing the problem?
Thanks,
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (7 preceding siblings ...)
2014-07-19 14:31 ` will.newton at gmail dot com
@ 2014-07-19 17:51 ` blue.dragan+sourceware at gmail dot com
2014-07-20 8:09 ` will.newton at gmail dot com
9 siblings, 0 replies; 17+ messages in thread
From: blue.dragan+sourceware at gmail dot com @ 2014-07-19 17:51 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=10833
--- Comment #15 from ChrisD <blue.dragan+sourceware at gmail dot com> ---
Sorry, I forgot to update this bug. This turned out to be a bug in the Linux
kernel. It's been fixed since at least kernel 2.6.39. The problem never
appeared again with any newer kernel. Gdb works fine on any multi-core ARM CPU.
Comment 11 probably diagnosed this problem correctly. Please close the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
` (8 preceding siblings ...)
2014-07-19 17:51 ` blue.dragan+sourceware at gmail dot com
@ 2014-07-20 8:09 ` will.newton at gmail dot com
9 siblings, 0 replies; 17+ messages in thread
From: will.newton at gmail dot com @ 2014-07-20 8:09 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=10833
Will Newton <will.newton at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Will Newton <will.newton at gmail dot com> ---
Thanks for the update, closing as fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
` (5 preceding siblings ...)
2009-10-28 5:50 ` melwyn dot lobo at gmail dot com
@ 2009-10-28 5:51 ` melwyn dot lobo at gmail dot com
6 siblings, 0 replies; 17+ messages in thread
From: melwyn dot lobo at gmail dot com @ 2009-10-28 5:51 UTC (permalink / raw)
To: gdb-prs
------- Additional Comments From melwyn dot lobo at gmail dot com 2009-10-28 05:51 -------
> I am able to reproduce the exact same behaviour on GDB 7.0. The remaining
bug
> environment is the same.
Also if I disable one of the cores, OR if I set scheduler affinity to a
particular processor this error (SIGILL) does not come.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
` (4 preceding siblings ...)
2009-10-23 14:15 ` ppluzhnikov at google dot com
@ 2009-10-28 5:50 ` melwyn dot lobo at gmail dot com
2009-10-28 5:51 ` melwyn dot lobo at gmail dot com
6 siblings, 0 replies; 17+ messages in thread
From: melwyn dot lobo at gmail dot com @ 2009-10-28 5:50 UTC (permalink / raw)
To: gdb-prs
------- Additional Comments From melwyn dot lobo at gmail dot com 2009-10-28 05:50 -------
(In reply to comment #4)
> (In reply to comment #3)
> > I have also experienced the same behaviour on GDB 6.8.
> There have been fixes to linux-thread-db and linux-nat since 6.8, so yes I
> believe it would help to know if the problem is still present in current CVS
> version.
I am able to reproduce the exact same behaviour on GDB 7.0. The remaining bug
environment is the same.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
` (3 preceding siblings ...)
2009-10-23 9:17 ` melwyn dot lobo at gmail dot com
@ 2009-10-23 14:15 ` ppluzhnikov at google dot com
2009-10-28 5:50 ` melwyn dot lobo at gmail dot com
2009-10-28 5:51 ` melwyn dot lobo at gmail dot com
6 siblings, 0 replies; 17+ messages in thread
From: ppluzhnikov at google dot com @ 2009-10-23 14:15 UTC (permalink / raw)
To: gdb-prs
------- Additional Comments From ppluzhnikov at google dot com 2009-10-23 14:15 -------
(In reply to comment #3)
> I have also experienced the same behaviour on GDB 6.8.
There have been fixes to linux-thread-db and linux-nat since 6.8, so yes I
believe it would help to know if the problem is still present in current CVS
version.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
` (2 preceding siblings ...)
2009-10-23 5:17 ` ppluzhnikov at google dot com
@ 2009-10-23 9:17 ` melwyn dot lobo at gmail dot com
2009-10-23 14:15 ` ppluzhnikov at google dot com
` (2 subsequent siblings)
6 siblings, 0 replies; 17+ messages in thread
From: melwyn dot lobo at gmail dot com @ 2009-10-23 9:17 UTC (permalink / raw)
To: gdb-prs
------- Additional Comments From melwyn dot lobo at gmail dot com 2009-10-23 09:17 -------
(In reply to comment #2)
> GDB 6.6 is 3 years old.
> Could you try to reproduce this using (just released) 7.0 or (better yet) GDB
> built from CVS?
I have also experienced the same behaviour on GDB 6.8. Do you think this could
be of use to you? It will take some time for me to setup ARM cortex build on
GDB 7.0.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
2009-10-23 4:41 ` [Bug gdb/10833] " melwyn dot lobo at gmail dot com
2009-10-23 4:42 ` melwyn dot lobo at gmail dot com
@ 2009-10-23 5:17 ` ppluzhnikov at google dot com
2009-10-23 9:17 ` melwyn dot lobo at gmail dot com
` (3 subsequent siblings)
6 siblings, 0 replies; 17+ messages in thread
From: ppluzhnikov at google dot com @ 2009-10-23 5:17 UTC (permalink / raw)
To: gdb-prs
------- Additional Comments From ppluzhnikov at google dot com 2009-10-23 05:17 -------
GDB 6.6 is 3 years old.
Could you try to reproduce this using (just released) 7.0 or (better yet) GDB
built from CVS?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
2009-10-23 4:41 ` [Bug gdb/10833] " melwyn dot lobo at gmail dot com
@ 2009-10-23 4:42 ` melwyn dot lobo at gmail dot com
2009-10-23 5:17 ` ppluzhnikov at google dot com
` (4 subsequent siblings)
6 siblings, 0 replies; 17+ messages in thread
From: melwyn dot lobo at gmail dot com @ 2009-10-23 4:42 UTC (permalink / raw)
To: gdb-prs
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
@ 2009-10-23 4:41 ` melwyn dot lobo at gmail dot com
2009-10-23 4:42 ` melwyn dot lobo at gmail dot com
` (5 subsequent siblings)
6 siblings, 0 replies; 17+ messages in thread
From: melwyn dot lobo at gmail dot com @ 2009-10-23 4:41 UTC (permalink / raw)
To: gdb-prs
------- Additional Comments From melwyn dot lobo at gmail dot com 2009-10-23 04:41 -------
Created an attachment (id=4312)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4312&action=view)
Plain multithreaded program to illustrate crash issue
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2014-07-20 8:09 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-10833-4717@http.sourceware.org/bugzilla/>
2011-09-09 9:16 ` [Bug gdb/10833] GDB crashes on debugging multithreaded program on ARM SMP dual core system blue.dragan+sourceware at gmail dot com
2011-09-09 15:37 ` pedro at codesourcery dot com
2011-09-10 17:29 ` blue.dragan+sourceware at gmail dot com
2011-09-10 17:43 ` blue.dragan+sourceware at gmail dot com
2011-09-10 18:09 ` pedro at codesourcery dot com
2011-09-11 8:29 ` blue.dragan+sourceware at gmail dot com
2011-09-12 18:29 ` blue.dragan+sourceware at gmail dot com
2014-07-19 14:31 ` will.newton at gmail dot com
2014-07-19 17:51 ` blue.dragan+sourceware at gmail dot com
2014-07-20 8:09 ` will.newton at gmail dot com
2009-10-23 4:40 [Bug gdb/10833] New: " melwyn dot lobo at gmail dot com
2009-10-23 4:41 ` [Bug gdb/10833] " melwyn dot lobo at gmail dot com
2009-10-23 4:42 ` melwyn dot lobo at gmail dot com
2009-10-23 5:17 ` ppluzhnikov at google dot com
2009-10-23 9:17 ` melwyn dot lobo at gmail dot com
2009-10-23 14:15 ` ppluzhnikov at google dot com
2009-10-28 5:50 ` melwyn dot lobo at gmail dot com
2009-10-28 5:51 ` melwyn dot lobo at gmail dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).