Re: how to continue from a breakpoint in GNU/Hurd

Hi, Sorry for the late reply. On Wed, Jul 17, 2013 at 1:25 AM, Luis Machado wrote: > Hi, > > > On 07/16/2013 02:04 PM, Yue Lu wrote: > >> Hi, >> >> thanks for you reply. >> >> On Wed, Jul 17, 2013 at 12:44 AM, Luis Machado >> >>> Some general thoughts... >>> >>> >>> Can you make sure the breakpo

Re: [PATCH] procfs: Ignore arguments for compatibility with Linux' procfs.

Quoting Justus Winter (2013-07-09 08:22:09) > Ignore the --nodev, --noexec and --nosuid arguments. > > * procfs/main.c (argp_parser): Ignore some arguments for compatibility. > --- Ping.

Re: how to continue from a breakpoint in GNU/Hurd

Hi, On 07/16/2013 02:04 PM, Yue Lu wrote: Hi, thanks for you reply. On Wed, Jul 17, 2013 at 12:44 AM, Luis Machado Some general thoughts... Can you make sure the breakpoint has been lifted from the instruction it replaced? If the breakpoint has been lifted and it is still being hit, then it

Re: how to continue from a breakpoint in GNU/Hurd

Hi, thanks for you reply. On Wed, Jul 17, 2013 at 12:44 AM, Luis Machado wrote: > Hi, > > > On 07/16/2013 01:28 PM, Yue Lu wrote: >> >> Hi. >> >> I am writing a debugger demo under GNU/Hurd when I study the gdb source >> code. And I have met a big problem that when I set a breakpoint in the >> i

Re: how to continue from a breakpoint in GNU/Hurd

Hi, On 07/16/2013 01:28 PM, Yue Lu wrote: Hi. I am writing a debugger demo under GNU/Hurd when I study the gdb source code. And I have met a big problem that when I set a breakpoint in the inferior, my code can't resume inferior from it. I can get the exception message from the mach kernel whe

how to continue from a breakpoint in GNU/Hurd

Hi. I am writing a debugger demo under GNU/Hurd when I study the gdb source code. And I have met a big problem that when I set a breakpoint in the inferior, my code can't resume inferior from it. I can get the exception message from the mach kernel when the inferior hit the breakpoint. As soon as

[PATCH 3/4] Add the necessary infrastructure to serve passive translators

* netfs.c (netfs_get_translator): New function. * procfs.c (procfs_get_translator): Likewise. * procfs.h (struct procfs_node_ops): New field get_translator. (procfs_get_translator): New function declaration. --- netfs.c | 11 +++ procfs.c | 12 procfs.h |6 ++ 3 f

[PATCH 2/4] Fix default file ownership

Formerly all nodes were created so that they were owned by root:root by default. This causes problems if the procfs translator is running as unprivileged user and serves passive translator records, because the file ownership is being used as credentials for starting translators. This obviously fail

[PATCH 4/4] Serve mounts node with a passive translator record

Make mounts a node with a passive translator record so that the mtab translator is started on access if it is available. * rootdir.c (MTAB_TRANSLATOR): New macro. (rootdir_mounts_get_translator): New function. (mtab_translator_state): New enum. (rootdir_mounts_exists): New function. (rootdir_trans

[PATCH 1/4] Fix procfs_node_chmod

Formerly only the mode_t bits cut out by S_IFMT were preserved, but this does not include S_IPTRANS. Fix this by preserving everything but the permission bits. * procfs.c (procfs_node_chmod): Fix bitmask. --- procfs.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/procfs.c

[PATCH] libnetfs: properly respond to file_get_translator requests

Properly respond to file_get_translator requests for nodes with a passive translator record. * libnetfs/file-get-translator.c (netfs_S_file_get_translator): Handle passive translator records. --- libnetfs/file-get-translator.c | 14 ++ 1 file changed, 14 insertions(+) diff --git