[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12018

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2011-01-19 17:46:04 UTC ---
(In reply to comment #0)

> (gdb) set $a = malloc (10)

PR_GET_NAME requires a 16 byte buffer.

> (gdb) call prctl(16,$a)
> $1 = -1
> (gdb) print errno
> $2 = 14

This is EFAULT.
So maybe something is wrong in your call....

> 16 is PR_GET_NAME, for reference

On my machine, PR_GET_NAME is 14.
16 is PR_SET_TIMING.  When I try this, I get EINVAL, though.

When I use 14, it works for me.

-- 
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.

[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12018

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-01-11
     Ever Confirmed|0                           |1

--- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-01-11 19:23:59 UTC ---
Any response?

-- 
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.

[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[gdb at dpinol dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12018

Dani <gdb at dpinol dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gdb at dpinol dot com

--- Comment #3 from Dani <gdb at dpinol dot com> 2012-11-09 14:47:55 UTC ---
Any news about this?

-- 
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.

[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[palves at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12018

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #4 from Pedro Alves <palves at redhat dot com> 2012-11-09 14:56:22 UTC ---
Is this failing for you?  What have you done, what did you expect, and what did
you get instead?

It works for me too.

-- 
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.

[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[gdb at dpinol dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12018

--- Comment #5 from Dani <gdb at dpinol dot com> 2012-11-09 15:57:01 UTC ---
Hi,
I didn't test it myself, my actual problem is this
https://bugreports.qt-project.org/browse/QTCREATORBUG-2332 . And since both
tickets are open, I assumed that the gdb problem still persisted.

-- 
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.

[Bug threads/12018] regression: 7.2 prctl syscall inside a thread results in Bad Address

[palves at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12018

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #6 from Pedro Alves <palves at redhat dot com> 2012-11-09 16:04:00 UTC ---
I see, thanks.  Let's close this then.  Please reopen if you can still
reproduce with a current gdb.  Note that nowadays, at least on GNU/Linux, GDB
tells you the thread's name in the output of "-thread-info".  It is extracted
from 
/proc/PID/task/TID/comm.

-- 
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.