demorar mais ainda,
guardei ela no meu fotolog, é so você ver ela por
AQUI
Se caso não funcionar aí, é so clicar
AQUI
Beijões e manda um abraço pro pessoal ai.
Lu (só para os intimos) A. Garcia
___
Bug-hurd mailing list
Bug-hurd@gnu.org
On Mon, Jan 18, 2021 at 4:04 PM Samuel Thibault via Libc-alpha
wrote:
>
> (leaving gcc out, it's really out of the story, it just happens to
> expose support for ifunc)
>
> Joseph Myers, le lun. 18 janv. 2021 20:05:44 +, a ecrit:
> > /scratch/jmyers/glibc-bot/install/compilers/i686-gnu/lib/gcc
On Mon, Jan 18, 2021 at 4:24 PM Samuel Thibault wrote:
>
> Samuel Thibault, le mar. 19 janv. 2021 01:21:05 +0100, a ecrit:
> > H.J. Lu, le lun. 18 janv. 2021 16:17:16 -0800, a ecrit:
> > > Why doesn't hurd ld.so build script mark strncpy as needed?
> >
> > I
On Mon, Jan 18, 2021 at 4:40 PM H.J. Lu wrote:
>
> On Mon, Jan 18, 2021 at 4:24 PM Samuel Thibault
> wrote:
> >
> > Samuel Thibault, le mar. 19 janv. 2021 01:21:05 +0100, a ecrit:
> > > H.J. Lu, le lun. 18 janv. 2021 16:17:16 -0800, a ecrit:
> > > >
On Tue, Jan 19, 2021 at 1:02 AM Samuel Thibault wrote:
>
> H.J. Lu via Libc-alpha, le lun. 18 janv. 2021 18:24:48 -0800, a ecrit:
> > On Mon, Jan 18, 2021 at 4:40 PM H.J. Lu wrote:
> > >
> > > On Mon, Jan 18, 2021 at 4:24 PM Samuel Thibault
> > > wrote:
On Tue, Jan 19, 2021 at 4:26 AM Adhemerval Zanella
wrote:
>
>
>
> On 19/01/2021 09:21, H.J. Lu via Libc-alpha wrote:
> > On Tue, Jan 19, 2021 at 1:02 AM Samuel Thibault
> > wrote:
> >>
> >> H.J. Lu via Libc-alpha, le lun. 18 janv. 2021 18:24:48 -0800, a
, but not any checkable
> preprocessor macros.
>
> Alternatively: maybe this part of cpu-features.c should be moved into
> sysdeps/unix/sysv/linux/x86_64/64/cpu-features.c and #include_next the
> common cpu-features.c?
>
Or something like this.
--
H.J.
From 24090a219d8bf902db530bfd9b
On Thu, Apr 20, 2023 at 11:43 AM Sergey Bugaev wrote:
>
> Normally, in static builds, the first code that runs is _start, in e.g.
> sysdeps/x86_64/start.S, which quickly calls __libc_start_main, passing
> it the argv etc. Among the first things __libc_start_main does is
> initializing the tunables
t;" ; then
> AC_MSG_ERROR([no mig for use])
> fi
> ;;
> esac
>
> that is, look for mig as mandatory only on Hurd, using a less-ambiguous
> variable as $host_os.
I almost agree with you, the $host_os is much better than $host.
in hurd it just says gnu0.3. we needn't to check for linux which says linux-gnu
--
Yue Lu (陆岳)
ChangeLog b/gdb/ChangeLog
index 12254b7..4fa69ac 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2013-05-04 Yue Lu
+
+ * configure.ac: Ensure MIG is available when building for GNU Hurd.
+ * configure: Regenerate.
+
2013-04-30 Samuel Thibault
* i386
targeting arm doesn't need to use MIG? As it run under GNU Hurd, it
must use the message transport facility and need to use MIG to
generate the interface file automatically or someone write it by
hands.
--
Yue Lu (陆岳)
I don't know how
to do the copyright assignment.
Could you please tell me how to do that?
thanks.
--
Yue Lu (陆岳)
entering the door of
open source world. Aha ^_^.
--
Yue Lu (陆岳)
m not correctly. I
run the kvm with this:
kvm -m 1500m -no-kvm-irqchip -drive file=hurd-7.0.qemu,cache=writeback
-vnc :1 -net nic,model=rtl8139 -net user,hostfwd=tcp::-:22 -cdrom
debian-7.0-hurd-i386-DVD-1.iso -monitor telnet::,server,nowait
--
Yue Lu (陆岳)
!
--
Yue Lu (陆岳)
I have a little fuzz about this. A few days ago I have already sent an
assignment email to the ass...@gnu.org under your advise. It seems doesn't
work because I didn't get any reply, so need I send one more email?
> Yue Lu,I'm sorry you stayed awake last Thursday and joined
Hi Justus.
On Sun, Jun 2, 2013 at 3:12 AM, Justus Winter <
4win...@informatik.uni-hamburg.de> wrote:
> Hi Yue Lu, as someone who was frustrated by gdb on the Hurd in the
> past, your project is highly appreciated. May I ask how you like to be
> addressed? I'm fuzzy about what
gt; email or postally), we should ask again.
>
Yesterday I have got a reply from FSF, they ask me to send a signed postal
mail. I think I am on the right way:) It just takes about a month to reply.
--
Yue Lu (陆岳)
) for free. Or I can provide my personal vps on
linode.com to host our code.
--
Yue Lu (陆岳)
Hi!
On Thu, Jun 20, 2013 at 6:52 PM, Thomas Schwinge wrote:
> More specifically, would Monday, 8 UTC (10 UTC+2, 16 UTC+8) work
> for everyone, typically?
>
That fine for me. And thank you for scheduling your TimeZone for me.
--
Yue Lu (陆岳)
never to continue.
I don't know how to fix this, could any of you give me a suggestion? thanks
very much.
--
Yue Lu (陆岳)
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 p
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
>>
>>>
Hi.
On Wed, Jul 17, 2013 at 8:09 PM, Richard Braun wrote:
> On Wed, Jul 17, 2013 at 02:11:58PM +0800, Yue Lu wrote:
>> When I get the exception message, I set the EIP to the next instruction
>> (for instance 0x12345678), after resume it, I call get_thread_state(), and
>> f
On Thu, Jul 18, 2013 at 12:13 AM, Richard Braun wrote:
> On Thu, Jul 18, 2013 at 12:07:20AM +0800, Yue Lu wrote:
>> when I used thread_info() to check the suspend count, they are zero.
>> But I met a strange thing.
>> this is my code snippet:
>> thr
/gdbserver.git under branch gdbserver.
Very glad for your comment.
2013-09-03 Yue Lu
* configure.tgt: Set build_gdbserver=yes for GNU/Hurd
hosts.
* configure: Regenerate.
diff --git a/gdb/configure.tgt b/gdb/configure.tgt
index b0bee47..3eb2ff7 100644
--- a/gdb/configure.tgt
this; it's probably easier that way. Moving them under gdb/nat/
> can be left for a cleanup step further down the road.
>
> Could we try that approach?
Ok, I will try to move the gdbserver/gnu-low.c back into gdb/gnu-nat.c.
> --
> Pedro Alves
>
--
Yue Lu (陆岳)
o that, etc.
Yeah, I will do that. But in my understand, I will use diff gnu-low.c
../gnu-nat.c and something like this. But I don't know how to use git
do this. Like git diff a.c b.c?
BTW, I got these patches by git diff > gdb.patch.
Then I edit the patch to two file. When I use git format-patch
I will get a patche for each commit after the
early_commit. What is the better way you generate patches?
--
Yue Lu (陆岳)
Hurd's debug APIs etc., is
> just unnecessary that way, by design, and we'll be able to focus on the
> bits that are the real new code -- the glue between the target and gdb, and
> the target and gdbserver.
I have put some soft link in directory gdbserver like *.defs which
there are a lot of place to improve in my patch, I will
submit my next patch a little later. Now I have only finished
removing the spurious blank and the soft link.
--
Yue Lu (陆岳)
te them into single one.
Or just I have got the wrong understand.
--
Yue Lu (陆岳)
*/
+#ifndef GDBSERVER
regcache_raw_supply (regcache, check_regno,
REG_ADDR (state, check_regno));
+#else
+ supply_register (regcache, check_regno,
+ REG_ADDR (state, check_regno));
+#endif
else
warning (_("... also writing this register! "
"Suspicious..."));
@@ -284,16 +337,24 @@ gnu_store_registers (struct target_ops *ops,
proc_debug (thread, "storing all registers");
for (i = 0; i < I386_NUM_GREGS; i++)
+#ifndef GDBSERVER
if (REG_VALID == regcache_register_status (regcache, i))
regcache_raw_collect (regcache, i, REG_ADDR (state, i));
+#else
+collect_register (regcache, i, REG_ADDR (state, i));
+#endif
}
else
{
+#ifndef GDBSERVER
proc_debug (thread, "storing register %s",
gdbarch_register_name (gdbarch, regno));
gdb_assert (REG_VALID == regcache_register_status (regcache, regno));
regcache_raw_collect (regcache, regno, REG_ADDR (state, regno));
+#else
+ collect_register (regcache, regno, REG_ADDR (state, regno));
+#endif
}
/* Restore the T bit. */
@@ -309,6 +370,7 @@ gnu_store_registers (struct target_ops *ops,
}
}
+#ifndef GDBSERVER
/* Provide a prototype to silence -Wmissing-prototypes. */
extern initialize_file_ftype _initialize_i386gnu_nat;
@@ -326,3 +388,4 @@ _initialize_i386gnu_nat (void)
/* Register the target. */
add_target (t);
}
+#endif
thanks.
--
Yue Lu (陆岳)
Hi,
On Wed, Sep 18, 2013 at 8:11 PM, Pedro Alves wrote:
> On 09/09/2013 10:58 AM, Thomas Schwinge wrote:
>> Hi!
>>
>> On Sun, 8 Sep 2013 21:35:05 +0800, Yue Lu wrote:
>>> On Fri, Sep 6, 2013 at 5:37 AM, Thomas Schwinge
>>> wrote:
>>>>> (c
Hi,
On Wed, Sep 18, 2013 at 8:37 PM, Pedro Alves wrote:
> On 09/12/2013 04:05 AM, Yue Lu wrote:
>
>> On Sat, Sep 7, 2013 at 2:53 AM, Pedro Alves wrote:
>>> This is what I meant:
>>> https://sourceware.org/ml/gdb-patches/2013-09/msg00253.html
>>>
>&g
Hi!
On Thu, Sep 05, 2013 at 11:37:36PM +0200, Thomas Schwinge wrote:
> Confirm that you haven't caused any regressions by running the GDB
> testsuite (natively) without and then with your change (don't forget to
> apply the testsuite patch I gave you earlier, to avoid the testsuite
> hanging (know
is developing a new operating system named the Hurd, which will be
a foundation of the whole GNU system.
>
> Thanks in advance!
>
> Regards,
> Subhashish
>
> P.S. - If you wish to ignore this, please send a short message; I'll oblige.
have fun with the big Hurd world :)
--
Yue Lu (陆岳)
C twice in Hurd project? With the experience in last summer,
I think I can implement this ideal. But I am not sure if a student can
apply a project for twice.
--
Yue Lu (陆岳)
following weeks.
>
Thank you! I have submitted my proposal.
--
Yue Lu (陆岳)
;t work either on Hurd. So as
gdbserver. You can try to attach to a exist process by GDB, you will get
that warnning. In detail, there is no distinct difference between the
implementation of GDB and gdbserver. They are the same.
--
Yue Lu (陆岳)
On Mon, Apr 2, 2018 at 7:47 AM, Samuel Thibault wrote:
> Hello,
>
> Joseph Myers, on lun. 02 avril 2018 14:22:28 +, wrote:
>> On Mon, 2 Apr 2018, Samuel Thibault wrote:
>>
>> > This means that build-glibcs i686-gnu now builds fine. Among the
>> > remaining TODOs, there are
>>
>> Thanks! I'd
On Mon, Apr 2, 2018 at 9:16 AM, Samuel Thibault wrote:
> H.J. Lu, on lun. 02 avril 2018 09:01:30 -0700, wrote:
>> On Mon, Apr 2, 2018 at 7:47 AM, Samuel Thibault
>> wrote:
>> > Hello,
>> >
>> > Joseph Myers, on lun. 02 avril 2018 14:22:28 +, wrote:
On Mon, Apr 2, 2018 at 10:15 AM, Samuel Thibault
wrote:
> H.J. Lu, on lun. 02 avril 2018 10:06:14 -0700, wrote:
>> On Mon, Apr 2, 2018 at 9:16 AM, Samuel Thibault
>> wrote:
>> > H.J. Lu, on lun. 02 avril 2018 09:01:30 -0700, wrote:
>> >> On Mon, Apr
Samuel Thibault writes:
> Applied, thanks!
This entry is also redundant:
>>* Configuration in `src/s/`: `gnu.h` uses `bsd-common.h`.
>> `gnu-kfreebsd.h`
>> uses `gnu-linux.h` -- we probably should too.
as Emacs has ceased to distribute explicit machine or system
configuration files,
On Wed, Jan 3, 2024 at 9:15 AM Sergey Bugaev wrote:
>
> Hello!
>
> This is my work on the aarch64-gnu port, aka GNU/Hurd on 64-bit ARM.
>
> To build this, you need an aarch64-gnu toolchain (binutils, GCC, MIG),
> and GNU Mach headers for AArch64. I have posted the patches for
> binutils, GCC, and
On Tue, Jul 9, 2024, 8:55 AM Samuel Thibault
wrote:
> 916730425594 ("elf: Add elf_backend_add_glibc_version_dependency")
> introduced adding an extra GLIBC_2.36 version dependency for x86_64. But
> on x86_64 GNU/Hurd, there has never been a glibc 2.36 port, and thus the
> GLIBC_2.36 version is no
Please open a binutils bug and CC me.
H.J.
On Tue, Jul 9, 2024, 9:01 AM H.J. Lu wrote:
>
> On Tue, Jul 9, 2024, 8:55 AM Samuel Thibault
> wrote:
>
>> 916730425594 ("elf: Add elf_backend_add_glibc_version_dependency")
>> introduced adding an extra GLIBC_2.36
46 matches
Mail list logo
